Menu
Validate model correctness using MCP tools. Checks element references, relationships, view definitions, and syntax.
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
Design 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.
| name | test-model |
| description | Validate model correctness using MCP tools. Checks element references, relationships, view definitions, and syntax. |
Use this skill when validating LikeC4 model correctness and integrity.
Use LikeC4 MCP read-project-summary to validate:
Use LikeC4 MCP search-element to verify:
Use LikeC4 MCP find-relationships to check:
Use LikeC4 MCP open-view to preview:
Use Context7 MCP query-docs to verify:
# Use LikeC4 MCP search-element to find elements
# Verify all referenced elements exist in model
# Use LikeC4 MCP read-project-summary
# Check that all element kinds are in spec-*.c4 files
❌ api -[calls]-> service // Missing label
✅ api -[calls]-> service 'Fetches data'
❌ include ** // Too broad
✅ include mySystem.* // Scoped
read-project-summary - verify all element kinds existsearch-element to validatefind-relationships for key connectionsopen-view for each defined viewlikec4 start locally to ensure diagrams renderCritical requirement: Every view MUST explicitly include its parent/surrounding element.
For detailed context requirements, see PARENT_CONTEXT_REFERENCE.md
Common mistakes:
Comprehensive validation report identifying: