Software Architect
Chris-Graffagnino/software-architect
Arquitetura de sistemas em nível estratégico com bases sólidas
Ver no GitHubUma skill para Claude Code que transforma Claude em arquiteto de software operacional, fundamentado em referências canônicas como DDIA, DDD, Team Topologies e padrões de sistemas distribuídos. Auxilia em decisões de limites de serviço, trade-offs monolito vs. microsserviços, design de sagas, análise de bounded contexts e redação de ADRs.
Instalação
npx convez-ai Chris-Graffagnino/software-architect1 comando no terminal: detecta o formato do repositório (marketplace ou plugin avulso) e instala via Claude Code. Requer Node 18+ e o Claude Code instalado.
Métricas
Casos de uso
- Decidir entre monolito e microsserviços
- Analisar e propor reestruturação de limites de serviço
- Redação e revisão de Architecture Decision Records (ADRs)
- Design de modelos de consistência em sistemas distribuídos
- Análise de bounded contexts e domain-driven design
Veredito

Ferramenta sólida para discussões arquiteturais estratégicas, ancorada em literatura consolidada (Hohpe, Richards/Ford, Kleppmann, Evans, Skelton). Adequada para profissionais sênior que buscam rigor metodológico, não para refatoração de código ou decisões de framework.
README
A tradução para o português deste README ainda está na fila.
software-architect
A Claude Code skill that turns Claude into a working software architect, grounded in canonical references on architectural posture, distributed-systems patterns, complexity diagnosis, data-systems mechanics, domain-driven design, and team topology.
Use it for service boundary decisions, monolith-vs-microservices trade-offs, saga and consistency-model design, bounded-context analysis, fitness functions, ADR drafting, and any "should we split / merge / restructure / extract" system-level question.
Installation
Clone into your Claude Code skills directory:
git clone https://github.com/<your-user>/software-architect.git \
~/.claude/skills/software-architect
Claude Code auto-discovers skills in ~/.claude/skills/. Restart Claude Code (or start a new session) and the skill is available.
Usage
software-architect Start an architecture conversation
software-architect help Show the usage guide
software-architect analyze Analyze the current codebase
software-architect analyze [path] Analyze a specific path or repo
software-architect <question> Ask any architectural question directly
The skill activates automatically when Claude detects an architectural question matching its description, or you can invoke it explicitly with /software-architect.
Examples
software-architect should we split the billing module into its own service?software-architect analyze ./services/orderssoftware-architect draft an ADR for moving from synchronous to event-driven communication
What's in the box
SKILL.md— the skill definition: operating instructions, workflow modes, decision frameworks, and dispatch rules Claude follows.references/— canonical source material the skill draws on:hohpe-architect-principles.md— architectural posture (Hohpe)richards-ford-architect-principles.md— engineering trade-off methodology (Richards / Ford)hard-parts-pattern-catalog.md— distributed-systems patternsmoseley-marks-tar-pit.md— complexity diagnosis (Moseley / Marks)kleppmann-data-intensive-applications.md— data-systems mechanics (Kleppmann, DDIA)evans-vernon-ddd-distilled.md— domain-driven design (Evans / Vernon)skelton-pais-team-topologies.md— team topology (Skelton / Pais)
assets/help.md— the help text printed bysoftware-architect help.
When NOT to use this skill
- Code-level refactoring (function / class / module scope)
- Specific framework or library choices (React vs Vue, Postgres vs MySQL)
- Debugging a specific bug
- Single-component implementation
- Performance optimization of one function
Rule of thumb: this skill is for the structure of the system, not the implementation of one component.
License
MIT — see LICENSE.