system-design
Installation
SKILL.md
System Design
Three-route bundle. Elicit a design or recover the implemented architecture, then turn the shared markdown contract into concrete .c4 source.
Routing
| Situation | Load |
|---|---|
| Need to clarify a system: identify actors, decide containers, pick components, write it down with ASCII diagrams | c4-modeling/SKILL.md |
| Need to understand existing implementation and create evidence-backed architecture views | code-to-c4/SKILL.md |
Have a structured C4 description (markdown + element/relationship tables) and need .c4 / .likec4 source plus views |
likec4/SKILL.md |
Default flow
- Enter at
c4-modelingfor greenfield design prompts. Enter atcode-to-c4when existing source code is the architecture evidence. - Elicit or recover Context → Container → Component. Produce a single
c4-model.md. - Hand off to
likec4. Generate.c4source from the markdown using the handoff mapping inlikec4/SKILL.md.
This is one continuous workflow. Continue from modeling through validated .c4 output without asking the user to invoke the next skill. Pause only for a material unresolved design choice or when the user explicitly requests a markdown-only checkpoint.