Your agent can do more. Find the skill that makes it happen.
Find your next superpower If you are an agent, refer to our llms.txt for full access.Sketch types, signatures, and module structure before code, then stay in the loop while implementation fills in. Use for $architect, 'architect this', 'design this', or non-trivial work where jumping to code would lock in the wrong shape.
Анализ требований и контекста задачи (architect). Use when нужно разобрать требования ДО проектирования — акторы, ограничения, риски, открытые вопросы; ещё не проектируем и не ревьюим.
Проектирование архитектуры решения (architect). Use when нужно спроектировать, КАК строить систему/фичу — компоненты, данные, контракты, выбор технологий; требования уже понятны или их даст /architect:analyze.
Ревью существующей архитектуры (architect). Use when нужно оценить УЖЕ написанную систему — узкие места, нарушения границ, антипаттерны с доказательствами file:line; ничего не проектируем и не правим.
Master software architect specializing in modern architecture patterns, clean architecture, microservices, event-driven systems, and DDD. Reviews system designs and code changes for architectural integrity, scalability, and maintainability. Use PROACTIVELY for architectural decisions.
Цель роли architect: session-first план, реализация в разрешённом scope и независимая проверка; Task Master только по явному выбору.
Capture the "why" behind technical choices to prevent architectural drift. Load when the user makes a major technical decision, chooses a library/framework, defines a system boundary, or changes a core architectural pattern. Also triggers on "record a decision", "write an ADR", "why did we do this", "document this architectural choice", or "architectural decision record". Supports SYNTHESIS=true…
Provides a framework for architectural decision-making and system design analysis. Covers requirements analysis, trade-off evaluation, and architecture decision record documentation.
Create layered system architecture diagrams using HTML/CSS templates with color-coded tiers and grid layouts. Best for technology stacks, microservices topology, and multi-tier application design.
Create or evaluate an architecture decision record (ADR). Use when choosing between technologies (e.g., Kafka vs SQS), documenting a design decision with trade-offs and consequences, reviewing a system design proposal, or designing a new component from requirements and constraints.
Write and maintain Architecture Decision Records (ADRs) following best practices for technical decision documentation. Use when documenting significant technical decisions, reviewing past architectural choices, or establishing decision processes.
Implement proven backend architecture patterns including Clean Architecture, Hexagonal Architecture, and Domain-Driven Design. Use when architecting complex backend systems or refactoring existing applications for better maintainability.
Skills give your agent reusable instructions for a specific job. Pick one, read what it does, and bring it into your workflow.
A name only tells half the story. Search the full description and instructions to find the right fit.
Read the skill, visit its source, and see exactly what you’re adding to your agent.
Copy the install command from a skill page and run it in your project.
npx skillycli add owner/repo --skill name