claude-code-architect-designer

## Current inventory Skills: !`ls .claude/skills` Agents: !`ls .claude/agents` Rules: !`ls .claude/rules` Decision records (the latest is the most recent): !`ls .claude/decisions` ## Scenario $ARGUMENTS --- # Claude Code Architect Designer Decides **which of the six forms** of extension resolves the scenario, and writes it. The six: | # | Form | File | |---|---|---| | 1 | Auto-invocable skill | `.claude/skills/<name>/SKILL.md` | | 2 | Manually-invoked skill (`/name`) | same, with `disable-model-invocation: true` | | 3 | Subagent | `.claude/agents/<name>.md` | | 4 | Rule | `.claude/rules/<name>.md` | | 5 | `CLAUDE.md` section | root `CLAUDE.md` | | 6a | MCP server, shared | `.mcp.json` | | 6b | MCP server, one agent only | `mcpServers:` in that agent's frontmatter | 6b isn't a fourth reason to write an agent — it's reason 2 of § 5 of the decision matrix (restrict tools) applied to an external connection instead of a built-in one. An agent only exists in the first place per the three reasons already in `references/decision-matrix.md` § 5; 6b just answers which tools it gets once that's settled. A legitimate seventh answer, and the cheapest one: **create nothing**. A piece that already covers the scenario exists, a CLI already solves it (§ 2.1 of the decision matrix), or the problem is a compliance issue and belongs in a hook/`permissions.deny` — which this skill does not write, see § Out of scope. **Entry rule: no proposal without an interview.** Classifying from o...