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.

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.

Create typed relationships with FQN, proper kinds (calls/async/reads/writes), descriptive labels, and no return relationships.

Create sequence views showing temporal flows and user interactions. Uses plain arrows with descriptive labels (no relationship kinds).

Advanced view features: styling (colors, shapes, style predicates), layout control (autoLayout, rank hints), and navigation (navigateTo, links).

Systematic naming for deployment nodes (VMs, zones, environments) enables consistent infrastructure documentation. Use {Environment}{Service}Vm for VMs, {Tier} for zones, and include VLAN/network details.

Organize deployment infrastructure into logical tiers (DMZ → AppTier → ProcTier → DataTier) with clear responsibility separation and firewall rules between zones.

Validate model correctness using MCP tools. Checks element references, relationships, view definitions, and syntax.

Load project context before making changes. Use when starting work to check available element kinds, relationship types, and tags.

Create Architecture Decision Records (ADRs) documenting WHY decisions were made. Uses standard ADR format (Status/Context/Decision/Consequences).

Apply common patterns (external integration, async processing, multi-tier, caching). Provides tested templates.

Quick reference for available element kinds and relationship types from shared specifications.

Structure multi-project workspaces with shared specifications. Use template project for new projects, organize by domain/team/layer.

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