Module Design Skill
evgeniiakruglova/claude-skill-module-design
Metodologia de design de engenharia em 9 passos como skill para Claude Code
Ver no GitHubSkill para Claude que transforma tarefas de desenvolvimento em blueprints estruturados usando metodologia de engenharia em 9 passos. Define módulos, estágios e operações com TEP (Target End Product) em cada nível, incluindo análise de falhas por inversão e padrão Config/Client/Storage para arquitetura modular robusta.
Instalação
npx convez-ai evgeniiakruglova/claude-skill-module-design1 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
- Decompor arquiteturas de sistemas complexos em módulos coesos
- Planejar pipelines de IA, ETL e processamento de conteúdo
- Executar pré-mortems e mapear modos de falha em projetos
Veredito

Skill robusto e bem estruturado para arquitetos de software que buscam rigor metodológico. Excelente para decomposição de sistemas complexos e prevenção de erros em estágio de design, mas requer curva de aprendizado significativa.
README
A tradução para o português deste README ainda está na fila.
module-design
Engineering design methodology as a Claude Code skill. Landing page: https://module-design-skill.vercel.app
Turns any development task into a blueprint: Module, Stage, Operation, with a TEP (Target End Product) at every level, inversion from failure, the Config/Client/Storage infrastructure triad, and a file-structure template.
No "let's think how to break this down." A hard 9-step process that lands on a finished design blueprint.
Installation
git clone https://github.com/evgeniiakruglova/claude-skill-module-design ~/.claude/skills/module-design
Launch Claude Code. The skill activates automatically on triggers.
What's inside
| File | What |
|---|---|
SKILL.md | 9-step workflow, rules, common mistakes |
references/principles.md | Architectural principles (SRP / Unix / Isolation / Composability / Fractality / DRY) and definitions |
references/inversion.md | Inversion navigation (necessary conditions, subtraction, constraint, kill criteria) |
references/conventions.md | Config / Client / Storage infrastructure triad |
references/template.md | Module template: collapsed and expanded form |
references/checklists.md | Module / stage / operation checklists with examples |
assets/blueprint.md | Final design document template |
Workflow
- System TEP (Target End Product), one sentence, a specific product
- Inversion first, premortem, necessary conditions, kill criteria
- Decomposition into modules, one customer, one contract
- Decomposition into stages, noun test plus extension for edge cases
- Decomposition into operations, atomic step, indivisible
- Placement of the Config/Client/Storage triad, at the correct level
- Expand or collapse the stage, by 4 load criteria
- Validation with checklists, module/stage/operation
- Inversion report, every failure mode mapped to a concrete measure
Triggers
The skill activates on mentions of:
- "design module X", "break task Y into stages"
- "is this a module or a stage", "should I expand this stage"
- "where does Config/Client/Storage live"
- "run a premortem", "find the bottleneck", "define kill criteria"
- key terms: TEP, module/stage/operation, SRP, inversion, module template, triad
Applies to
- AI agents and pipelines
- Parsers, ETL, content pipelines
- Backend systems with modular architecture
- Any task that requires decomposition and a contract
License
MIT
Originally created by Vlad Yasko. English translation by Jenya Kruglova.