model-deployment

Define and validate physical deployment hierarchies in C4 models.

5|1|Updated Jan 15, 2026
One-click install
npx skills add https://github.com/a-scolan/c4-template --skill model-deployment-a-scolan
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: model-deployment
Source: https://github.com/a-scolan/c4-template/tree/main/.github/skills/model-deployment
Command: npx skills add https://github.com/a-scolan/c4-template --skill model-deployment-a-scolan

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps teams define and enforce a clear physical deployment structure for C4 models, ensuring environments, zones, VMs, and apps are consistently organized with correct containment and instanceOf relationships.

Core Features & Use Cases

  • Hierarchical deployment modeling: Represent Environment -> Zone -> VM -> App with proper containment and instanceOf links.
  • Shared spec compliance: Reuse node kinds and tags from shared/spec-deployment.c4 to maintain consistency across projects.
  • Network and infrastructure details: Include VLANs, network segments, and protocol/port descriptions in zone and VM definitions.
  • Validation guidance: Enforce port formats and mirrored relationships between system and deployment models.

Quick Start

Create a deployment model by defining a Production Environment, add Zones (DMZ, App, Data), introduce VMs and Apps with instanceOf links, and reference shared specs; ensure port descriptions exist in relationships.

Frequently Asked Questions about model-deployment

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I model physical deployment hierarchies in C4 models?

Model physical deployment hierarchies in C4 models by defining containment relationships from Environment to Zone to VM to App, using instanceOf links to map system components to their physical counterparts.

How do I structure network segments and ports in a C4 deployment model?

Structure network segments and ports in a C4 deployment model by defining VLANs within zones and specifying protocol and port descriptions on relationships connecting VMs and apps.

What is the best way to enforce consistent deployment topology across multiple projects?

Enforce consistent deployment topology across multiple projects by referencing shared deployment specs for node kinds and tags, ensuring all environments and zones follow identical structural rules.

How do I validate instanceOf links between system and deployment C4 models?

Validate instanceOf links between system and deployment C4 models by enforcing mirrored relationships, checking that every physical node correctly maps to its logical system component counterpart.

Can I use shared spec compliance to standardize VM and environment definitions in C4?

Yes, you can use shared spec compliance to standardize VM and environment definitions in C4 by reusing node kinds and tags from shared deployment specification files across projects.

Why does my C4 deployment model require port descriptions on relationships?

C4 deployment models require port descriptions on relationships to validate network infrastructure details, ensuring proper protocol formats and consistent communication mapping across zones and VMs.