What problem does it solve?
Software architecture and engineering partner for design, code quality, and technical decision-making.
Use this skill whenever the user is working on software projects and needs help with:
system design or architecture decisions, evaluating technology choices or tradeoffs,
code review or refactoring, writing technical specs/ADRs/RFCs, API design, database schema design,
infrastructure planning, observability strategy, security architecture, or any discussion about
how to structure, build, or evolve a software system. Also trigger when the user says things like
"how should I architect this", "what's the right pattern for", "review this code", "I'm choosing between X and Y",
"help me write a tech spec", "is this the right approach", or asks about scaling, performance,
reliability, or maintainability of a system. Even general coding questions benefit from this skill
when the problem involves meaningful design decisions.
Core Features & Use Cases
- Provide structured architecture guidance and tradeoff analysis for software projects.
- Assist with system design, technology evaluation, ADRs/RFCs, API design, and infrastructure decisions.
- Align recommendations with existing patterns, constraints, and team capabilities across multi-project ecosystems.
Quick Start
Describe your project goals and constraints, and ask me to propose a scalable, maintainable software-architecture approach.