Agnostic Architect
A technology-agnostic engineering framework: analyze the problem first, select the optimal stack per task, enforce Clean Architecture + SOLID + OWASP Top 10, and require a testing strategy on every implementation.
This folder now works with either GitHub Copilot or Claude, from the same source of truth.
agnostic-architect/
├── SKILL.md ← Claude Skill (Claude Code / claude.ai)
├── copilot-instructions.md ← GitHub Copilot custom instructions
├── references/
│ ├── owasp-checklist.md ← full OWASP enforcement table
│ └── output-format.md ← mandatory response structure
└── README.md ← this file
Using it with Claude (Claude Code)
Claude Code auto-discovers skills. Drop this whole folder into one of:
~/.claude/skills/agnostic-architect/ — available in every project on your machine<project>/.claude/skills/agnostic-architect/ — scoped to one project only
No config file, no "type Hi to activate" step needed. Claude's skill system triggers on task relevance, not on a magic word: it reads the description in SKILL.md's frontmatter and pulls the skill in automatically whenever a request matches (new project, stack choice, security review, refactor, test generation, etc.).
If you want the old-style banner anyway, typing Hi or Initialize still works — the skill supports it as an optional entry point, it's just not the only way in.
Using it with claude.ai (no Claude Code)
Claude.ai supports uploading a skill directly: package this folder (zip it, or just the bare SKILL.md if you don't need the reference files) and use the "Save skill" option when Claude presents it, or upload it in your account's skill settings.
Using it with GitHub Copilot
VS Code / Copilot will auto-detect it. Type Hi in a Copilot Chat session in that workspace to activate — Copilot doesn't do relevance-based triggering, so the literal keyword is still required there.
Copilot's version still references MCP servers (filesystem, github, mssql, figma, etc.) for real-time context — configure those the same way as before via .vscode/mcp.json if you want that. See the table below.
Common MCP servers (Copilot path only)
| Server |
Purpose |
Package |
| Filesystem |
Read/write local files |
@modelcontextprotocol/server-filesystem |
| Fetch |
Retrieve web pages & APIs |
@modelcontextprotocol/server-fetch |
| PostgreSQL |
Query PostgreSQL databases |
@modelcontextprotocol/server-postgres |
| SQLite |
Query SQLite databases |
@modelcontextprotocol/server-sqlite |
| GitHub |
Repo, PR, issue access |
@modelcontextprotocol/server-github |
| Memory |
Persistent knowledge graph |
@modelcontextprotocol/server-memory |
Browse more servers at https://github.com/modelcontextprotocol/servers
Claude Code doesn't need this table — the equivalent capabilities (reading files, running gh, hitting a DB CLI, fetching docs) are already native tools, listed in SKILL.md.
| Section |
Content |
| 1. Proposed Stack |
Language, Framework, Database, Infrastructure |
| 2. Justification |
Why this stack is optimal vs. an alternative |
| 3. Implementation |
Clean Architecture code with inline security |
| 4. Testing Strategy |
Unit, integration, and security test plans |
| ⚠️ Security Notes |
Trade-offs and mitigations (when applicable) |
Full template: references/output-format.md.
Enforced standards
- Architecture: Clean Architecture, strict layer separation
- Design: SOLID (SRP, OCP, LSP, ISP, DIP)
- Security: OWASP Top 10 (
references/owasp-checklist.md), zero-trust, no hardcoded secrets
- Testing: Unit + Integration + Security tests required for every implementation
Troubleshooting
| Issue |
Solution |
| Claude doesn't use the skill |
Check it's in ~/.claude/skills/ or <project>/.claude/skills/, and that the task is substantive — trivial one-line asks may bypass skills entirely by design. |
| Copilot doesn't activate on "Hi" |
Confirm copilot-instructions.md is at .github/copilot-instructions.md in the workspace root. |
| Copilot MCP tools not listed |
Check .vscode/mcp.json syntax, confirm Node.js is installed, restart VS Code. |
| Copilot ignores the instructions |
Some IDEs need the file at a different path — check that IDE's docs for custom instruction locations. |
License
Provided as a workspace configuration template. Use and modify freely.
