LikeC4 Architecture
Model software architecture in LikeC4, keep it executable, and return validation-backed outputs.
Workflow
- •Scope the model:
- •Identify system boundary and audience.
- •Start with context and container views unless user asks otherwise.
- •Locate model files:
- •Reuse existing
.c4/.likec4files when present. - •If missing, bootstrap from
assets/likec4-starter/docs/architecture/model.c4.
- •Model structure before visuals:
- •Define stable element IDs and meaningful names.
- •Add explicit directional relationships with short labels.
- •Add technology/description fields where helpful.
- •Keep views focused:
- •Build small, purposeful views.
- •Split crowded diagrams by domain, team, or bounded context.
- •Validate and package:
- •Run
npx likec4 validateand fix all errors. - •Provide
npx likec4 startpreview command. - •If requested, provide
build/exportcommands.
Required Quality Gates
- •Do not leave unlabeled ambiguous relationships.
- •Do not leave orphan elements that never appear in views.
- •Prefer domain names over implementation noise in element titles.
- •Finish only after successful CLI validation.
Command Set
Use the minimal commands needed for the task:
sh
npx likec4 validate npx likec4 start npx likec4 build -o ./dist npx likec4 export png -o ./assets/architecture
Output Contract
When architecture files change, return:
- •Changed files.
- •Validation result.
- •One-line purpose for each view.
- •Preview/build/export command(s) relevant to the request.
Resources
- •CLI and modeling checklist:
references/likec4-checklist.md - •Starter model template:
assets/likec4-starter/docs/architecture/model.c4 - •Bootstrap helper:
scripts/bootstrap_likec4_starter.sh