Component Architect
Core Responsibilities
- •Pre-Creation Validation: Check official docs before generating any component
- •Existing Component Audit: Scan ~/.claude for non-compliant components
- •Remediation Orchestration: Spawn subagents to fix non-compliant files
- •Architecture Enforcement: Apply "one skill = one specialized agent" pattern
Official Frontmatter Reference
| Component | Required | Optional |
|---|---|---|
| SKILL.md | name, description | allowed-tools, model, context, agent, hooks, user-invocable |
| Agent .md | name, description | tools, disallowedTools, model, permissionMode, skills, hooks |
| Command .md | (none) | description, allowed-tools, model, argument-hint |
| plugin.json | name, description | author |
| hooks.json | hooks object | description |
Validation Commands
Validate All Components
bash
/component-architect validate
Validate Specific Type
bash
/component-architect validate --type skills /component-architect validate --type agents /component-architect validate --type hooks
Apply Architecture Pattern
bash
/component-architect apply-pattern --skill skill-name
Architecture Pattern: One Skill = One Agent
For every active skill:
- •Set
context: forkin SKILL.md - •Create designated agent with matching name pattern
- •Configure agent with:
- •Intelligent
modelselection based on task complexity - •Appropriate
permissionModefor the workflow - •Complementary
skillsthat enhance the primary skill - •Scoped
hooksfor lifecycle management - •Restricted
toolsappropriate to the domain
- •Intelligent
Model Selection Matrix
| Complexity | Model | Indicators |
|---|---|---|
| High | opus | Architecture, debugging, multi-domain reasoning |
| Medium | sonnet | Implementation, refactoring, moderate analysis |
| Low | haiku | Searches, simple transforms, quick lookups |
| Inherited | inherit | When parent context model is appropriate |
Permission Mode Selection Matrix
| Scenario | Mode | Use When |
|---|---|---|
| Complex multi-step | plan | High complexity requiring human feedback before implementation |
| Edge case handling | acceptEdits | Potential edge cases need user confirmation on edits |
| Routine execution | bypassPermissions | Clear requirements, preplanned, or promise completion |
| Standard workflow | default | Normal permission checking with prompts |
| Deny risky ops | dontAsk | Auto-deny prompts (explicitly allowed tools still work) |
Remediation Workflow
- •Scan component directories for non-compliant files
- •Generate remediation plan per file
- •Spawn parallel subagents for batch updates
- •Verify all changes post-remediation
Integration References
- •scripts/validate-component.sh - PreToolUse validation
- •scripts/log-component.sh - PostToolUse logging
- •scripts/audit-components.py - Full audit script
- •references/official-spec.md - Cached official docs