name	troubleshoot-errors
description	Diagnose common LikeC4 errors (element not found, unknown kinds, invalid relationships). Provides causes and solutions.

Troubleshoot LikeC4 Errors

Use this skill when resolving common LikeC4 syntax or reference errors.

Common Issues

"Element not found"

Cause: Using short name instead of FQN
Solution: Use mySystem.api not api for nested elements

"Unknown element kind"

Cause: Invalid or generic element kind
Solution: Check projects/shared/spec-*.c4 for valid kinds; use specific kinds like Container_Api not Container

"Invalid relationship kind"

Cause: Undefined relationship type
Solution: Use defined kinds: calls, async, reads, writes, uses (model) or http, https, tcp (deployment)

Diagram shows unexpected elements

Cause: Over-broad wildcard includes like include **
Solution: Use scoped wildcards: include mySystem.* or include mySystem.* ->

"instanceOf target not found"

Cause: Referencing non-existent or wrong element type
Solution: Ensure target is a Container from model, use FQN: instanceOf mySystem.api

Más de este repositorio

mismo repositorio

design-view

a-scolan/c4-hands-on-demo

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.

2026-01-232

model-deployment

a-scolan/c4-hands-on-demo

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.

2026-01-232

write-rich-descriptions

a-scolan/c4-hands-on-demo

Use metadata for system models (business/technical context) and markdown tables for deployment models (infrastructure specs). Makes models queryable and self-documenting.

2026-01-232

c4-modeling-process

a-scolan/c4-hands-on-demo

C4 modeling methodology - design system hierarchy top-to-bottom from Context to Components. Ensures consistent, stakeholder-focused architecture documentation.

2026-01-202

configure-project-includes

a-scolan/c4-hands-on-demo

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).

2026-01-202

create-element

a-scolan/c4-hands-on-demo

Create elements with proper naming (PascalCase kinds, camelCase vars), required metadata (technology, description), and correct hierarchy.

2026-01-202

name	troubleshoot-errors
description	Diagnose common LikeC4 errors (element not found, unknown kinds, invalid relationships). Provides causes and solutions.

Troubleshoot LikeC4 Errors

Use this skill when resolving common LikeC4 syntax or reference errors.

Common Issues

"Element not found"

Cause: Using short name instead of FQN
Solution: Use mySystem.api not api for nested elements

"Unknown element kind"

Cause: Invalid or generic element kind
Solution: Check projects/shared/spec-*.c4 for valid kinds; use specific kinds like Container_Api not Container

"Invalid relationship kind"

Cause: Undefined relationship type
Solution: Use defined kinds: calls, async, reads, writes, uses (model) or http, https, tcp (deployment)

Diagram shows unexpected elements

Cause: Over-broad wildcard includes like include **
Solution: Use scoped wildcards: include mySystem.* or include mySystem.* ->

"instanceOf target not found"

Cause: Referencing non-existent or wrong element type
Solution: Ensure target is a Container from model, use FQN: instanceOf mySystem.api