What problem does it solve?
Changes to LikeC4 CLI code generation can silently break output contracts, letting generated dot, d2, mermaid, or plantuml files escape the requested --outdir when views come from external include paths, absolute paths, or Windows drive paths.
Core Features & Use Cases
- Output containment invariants: Defines the contract that every multi-file generator (dot, d2, mermaid/mmd, plantuml) writes all emitted views under the requested --outdir.
- Regression test matrix: Provides a minimal test matrix covering nested project views, external include paths, parent-relative paths, absolute paths, and Windows drive-style paths.
- Temp workspace fixture pattern: Describes a workspace/project-a/shared/out fixture layout with assertions that no file lands outside the output root.
- Use Case: When fixing a bug where
likec4 gen dot --outdir out writes a file next to an externally included source, use this Skill to add a failing regression test first, then verify all four formats against the containment contract.
Quick Start
Ask the AI to add a regression test proving that likec4 gen dot, d2, mermaid, and plantuml keep every generated file inside the --outdir folder, including views from external include paths.