architecture-advisor
Architecture Advisor
This skill routes to the architecture-advisor agent — a principal software architect (Opus, plan mode) that provides strategic guidance on system design, technology evaluation, and architectural decisions.
When to Use
- Designing new system components or services
- Evaluating technology choices (build vs. buy, library selection)
- Planning large-scale migrations or refactors
- Assessing technical debt and prioritizing remediation
- Creating Architecture Decision Records (ADRs) for
docs/adr/ - Reviewing system design for quality attributes (scalability, maintainability, security)
What the Agent Does
The architecture-advisor agent operates in plan mode — it researches the codebase, analyzes the current architecture, and presents a recommended approach for your approval before any changes are made.
- Understands current architecture — reads config files, maps dependencies, reviews existing ADRs
- Identifies the concern — new design, migration, scaling, tech debt
More from kaakati/sdh-claude-skills
refactor
Safely refactor code using Fowler's patterns with test-first methodology and incremental steps. Use this skill whenever someone asks to refactor code, reduce technical debt, extract patterns, restructure modules, or says things like "refactor this", "clean up this code", "extract this into a service", "this code smells", "reduce duplication", "decompose this function", or "restructure this module". Also trigger for code smell identification, large-scale codebase transformations, or safe migration of legacy code.
2ui-ux-patterns
|
2web-design-guidelines
|
2react-best-practices
|
2clean-architecture
Validate and implement Clean Architecture patterns including entity/use-case/adapter/framework layer separation, dependency direction enforcement, and architectural conformance checking. Use this skill whenever someone asks about architecture validation, layer boundaries, dependency direction, or says things like "check architecture", "validate clean architecture", "are my layers correct", "dependency direction", "refactor to clean architecture", "layer violation", or "architectural conformance". Also trigger for discussions about service object patterns, controller responsibilities, or domain model isolation.
2api-designer
Design and review REST APIs for consistency, standards compliance, and developer experience. Use this skill whenever someone asks to design an API, create endpoints, review API contracts, generate OpenAPI specs, or says things like "design the API for X", "review this endpoint", "what should the API look like", "create a REST interface", "write the OpenAPI spec", or "check my API design". Also trigger when someone mentions pagination strategy, error response format, API versioning, or rate limiting design.
1