Loading...
Loading...
Found 2,219 Skills
Analyze Java project architecture at macro level - package structure, module boundaries, dependency direction, and layering. Use when user asks "review architecture", "check structure", "package organization", or when evaluating if a codebase follows clean architecture principles.
Design-driven development methodology. The design/ directory is the single source of architectural truth — read it before coding, stay within its boundaries, and when the system's shape needs to change, update the design first. Use this skill whenever starting any development work on this project. Also use when the user asks to: create or update architecture docs, add a new module or feature that might cross existing boundaries, refactor system structure, or understand the codebase architecture. Trigger on phrases like "design first", "update the design", "does this change the architecture", "write a design for", "what's the current design", or when onboarding to understand a codebase's shape. Supports arguments: `/design-driven init` to configure a project for design-driven development, `/design-driven bootstrap` to generate design from an existing codebase.
Explain how something works in this codebase by exploring code and producing a clear architectural explanation. Optionally critique the architecture for issues.
[Hyper] Use when working on Vite + TanStack Router projects - enforces architecture rules (layers, routes, hooks, services, conventions) with mandatory validation before any code change. Triggers on file creation, route work, hook patterns, or any structural change in a Vite + TanStack Router codebase.
/cs:cto-review <plan> — Architecture and scaling interrogation. Tech debt, scaling cliffs, team scaling, build-vs-buy.
Crear o actualizar Architecture Decision Records (ADRs) en docs/adr/. Activar siempre que el usuario quiera documentar, registrar, actualizar o cambiar el estado de una decisión arquitectónica — incluso si no usa la palabra "ADR". Frases que activan este skill: "registrar decisión", "documentar por qué usamos X", "dejar constancia de esta elección técnica", "decision record", "cambiar ADR a Accepted", "marcar como Superseded", "crear ADR", "actualizar ADR", "nuevo ADR", "ADR-XXX". Usar también cuando el usuario describa una tensión arquitectónica que deba quedar documentada.
Generate self-contained HTML visualizations with Plannotator theming. Use for implementation plans, PR explainers, architecture diagrams, data tables, slide decks, and any visual explanation of technical concepts. Plans and PR explainers follow Plannotator's prescriptive approach; all other visual content delegates to nicobailon/visual-explainer.
Write comprehensive technical documentation including user guides, how-to articles, system architecture docs, onboarding materials, and knowledge base articles. Creates clear, structured documentation for technical and non-technical audiences. Use when users need technical writing, documentation, tutorials, or knowledge base content.
arc42 architecture documentation template and guidance
Generate implementable architecture solutions based on business requirements and tech stacks, providing structured suggestions and tech stack selection optimization through a four-step process (information collection, requirement sorting, iterative improvement, solution output)
Create and validate solution design documents (SDD). Use when designing architecture, defining interfaces, documenting technical decisions, analyzing system components, or working on solution-design.md files in docs/specs/. Includes validation checklist, consistency verification, and overlap detection.
Perform systematic self-review of code changes before commits using structured checklist. Validates architecture boundaries, code quality, test coverage, documentation, and project-specific anti-patterns. Use before committing, creating PRs, or when user says "review my changes", "self-review", "check my code". Adapts to Python, JavaScript, TypeScript, Go, Rust projects.