Menu
Diagnose common LikeC4 errors (element not found, unknown kinds, invalid relationships). Provides causes and solutions.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
| name | troubleshoot-errors |
| description | Diagnose common LikeC4 errors (element not found, unknown kinds, invalid relationships). Provides causes and solutions. |
Use this skill when resolving common LikeC4 syntax or reference errors.
mySystem.api not api for nested elementsprojects/shared/spec-*.c4 for valid kinds; use specific kinds like Container_Api not Containercalls, async, reads, writes, uses (model) or http, https, tcp (deployment)include **include mySystem.* or include mySystem.* ->instanceOf mySystem.apiDesign views with proper includes/excludes and basic layout. Use for include patterns, tag filtering, and simple rank hints. For advanced styling/navigation, use customize-view.
Model deployment infrastructure (environments, zones, VMs, apps) with proper hierarchy and instanceOf links. Organize zones into tiers (DMZ, App, Data, Processing) with rich descriptions including VLAN/network specifications.
Use metadata for system models (business/technical context) and markdown tables for deployment models (infrastructure specs). Makes models queryable and self-documenting.
C4 modeling methodology - design system hierarchy top-to-bottom from Context to Components. Ensures consistent, stakeholder-focused architecture documentation.
Manage likec4.config.json includes and image aliases. Ensures relative paths and preserves existing configuration. Support multi-file organization (system-model + system-views + deployment + operations).
Create elements with proper naming (PascalCase kinds, camelCase vars), required metadata (technology, description), and correct hierarchy.