skill-architect

The Skill Architect acts as a senior consultant for developers and technical leads aiming to extend the capabilities of AI coding agents like Claude Code, Cursor, Aider, and Roo Code. Instead of providing generic templates, this skill employs a rigorous, multi-phase methodology to ensure that every skill built is fit for purpose, performant, and reliable. It is designed for those who need to automate repetitive workflows, enforce consistency across team processes, or teach agents to handle specific, deterministic tasks. By moving from Discovery to Architecture and finally to Craft, it prevents the common pitfalls of bloated, vague, or incorrectly triggered instructions that degrade agent performance. Whether you are creating a standalone skill, an MCP-enhanced workflow, or a complex system, the architect ensures that your SKILL.md file is optimized for LLM consumption, utilizing progressive disclosure to maintain token efficiency and clarity.

• Performs deep-dive Discovery to define success criteria, identify necessary tools, and map concrete use cases before any code is generated.

• Implements a structured Architectural phase to select optimal patterns such as Sequential Workflows, Multi-MCP Coordination, or Iterative Refinement.

• Enforces strict quality standards, prioritizing code over prose for deterministic checks and minimizing technical debt by keeping documentation concise.

• Guides the creation of optimized directory structures, effectively balancing logic in scripts/, reference material in references/, and static templates in assets/.

• Educates users on negative triggers and specific prompt engineering to ensure skills only activate when contextually relevant, preventing interference with other agent operations.

• Use this when you say: 'turn this into a skill', 'I want to automate this workflow', or 'how do I teach my Agent to do X'.

• Ideal for building internal methodology skills, domain-specific intelligence modules, or automated asset generation tools.

• Not intended for creating subagents (use subagent-creator) or drafting technical design documents (use create-technical-design-doc).

• Always follow the sequential workflow: Discovery, Architecture, Craft, Validate, and Deliver.

• Remember to design with composability in mind; skills must coexist safely with other loaded capabilities in the environment.