菜单
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.
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/a-scolan/c4-hands-on-demo --skill name-deployment-nodes命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
正在显示 SKILL.md
基于 SOC 职业分类
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.
| name | name-deployment-nodes |
| description | 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. |
Use this skill when creating VMs, zones, or deployment nodes in deployment.c4 or operations.c4.
Prerequisite: Read model-deployment skill for basic structure and hierarchy.
Pattern: {Environment}{ServiceName}Vm (PascalCase)
// Examples following pattern
ProdApigwVm // prod + apigw + vm = production API gateway VM
ProdUploadVm // prod + upload + vm = production upload service VM
ProdWorkerVm // prod + worker + vm = production processing worker VM
StagingApiVm // staging + api + vm = staging API VM
DevDatabaseVm // dev + database + vm = development database VM
Rules:
Prod, Staging, Dev, TestVm for consistencyprod-apigw-vm, prod-upload-vmPattern: {Tier}Tier or {Function}Zone (PascalCase)
// Tier-based naming (for layered architectures)
Dmz // Demilitarized Zone (edge security)
AppTier // Application tier (microservices)
ProcTier // Processing tier (async workers)
DataTier // Data tier (databases, storage)
// Function-based naming (for specialized infrastructure)
SecZone // Security & monitoring
InfraZone // Backup & disaster recovery
NetworkZone // Load balancing & CDN
Rules:
Tier suffix for layered architecture (App, Proc, Data, Dmz)Zone suffix for functional groupings (Sec, Infra, Network)AppT or ProcZone)Pattern: {Environment} (PascalCase)
Prod // Production (customer-facing)
Staging // Staging (pre-production testing)
Dev // Development (local testing)
Test // Test (automated testing)
Pattern: {Provider}{Service} (PascalCase)
VirusTotalService // SaaS antivirus provider
AwsS3Bucket // AWS cloud storage
GoogleAnalyticsApi // Google SaaS analytics
DatadogMonitoring // SaaS monitoring platform
Always include network and infrastructure specifications in zone descriptions:
AppTier = Zone "Application Tier (VLAN 101: 10.1.0.0/24)" {
description """
Microservices deployment zone
| Property | Value |
|:---------|:------|
| VLAN | 101 |
| Network | 10.1.0.0/24 |
| Gateway | 10.1.0.1 |
| Firewall | DMZ → AppTier (ingress 443) |
| Firewall | AppTier → DataTier (egress 27017, 9000) |
| Purpose | Production microservices |
"""
// VMs in this zone
ProdUploadVm = Node_Vm "prod-upload-vm" { ... }
ProdRetrievalVm = Node_Vm "prod-retrieval-vm" { ... }
}
Zone SomeTier "Human Readable Zone Name (VLAN N: CIDR)" {
description """
Brief purpose of this zone
| Property | Value |
|:---------|:------|
| VLAN | 101 |
| Network | 10.1.0.0/24 |
| Gateway | 10.1.0.1 |
| Firewall Rules | List relevant rules |
| Purpose | What runs here |
| Tags | #Production #Networking |
"""
}
Use Markdown tables to make deployment specs scannable and self-documenting:
ProdUploadVm = Node_Vm "prod-upload-vm" {
#Deployment
technology "Node.js + Docker"
description """
File upload handler and validation service (fail-fast validation)
| Property | Value |
|:---------|:------|
| Hostname | prod-upload-vm |
| IP Address | 10.1.0.12/24 |
| OS | Ubuntu 22.04 LTS |
| CPU | 2 vCPU |
| RAM | 4 GB |
| Disk | 100 GB SSD |
| Port | 3001 |
| Protocol | HTTP/2 |
| Container | Docker |
| Monitoring | Prometheus metrics on 9090 |
| Backup | Daily snapshots |
"""
uploadApp = Node_App "Upload Service" {
instanceOf vault.uploadService
}
}
Node_Vm "vm-name" {
technology "Runtime + Tools"
description """
Human-readable purpose and role
| Property | Value |
|:---------|:------|
| Hostname | prod-service-vm |
| IP | 10.x.x.y/24 |
| OS | Ubuntu 22.04 LTS |
| CPU | 2 vCPU |
| RAM | 4 GB |
| Port | 3001 |
| Container | Docker |
| Monitoring | Port 9090 |
"""
}
deployment {
Prod = Node_Environment 'Production Datacenter - EU' {
#Production
// Edge security zone
Zone Dmz "Network DMZ (VLAN 100: 10.0.0.0/24)" {
description """
Perimeter security zone with TLS termination
| Property | Value |
|:---------|:------|
| VLAN | 100 |
| Network | 10.0.0.0/24 |
| Gateway | 10.0.0.1 |
| Purpose | Edge services |
"""
ProdApigwVm = Node_Vm "prod-apigw-vm" {
technology "Kong / API Gateway"
description """
Edge API gateway terminates TLS and routes
| Property | Value |
|:---------|:------|
| IP | 10.0.0.10/24 |
| OS | Ubuntu 22.04 LTS |
| CPU | 4 vCPU |
| RAM | 8 GB |
| Port | 443 |
"""
apiApp = Node_App "API Gateway" {
instanceOf vault.api
}
}
}
// Application services tier
AppTier = Zone "Application Tier (VLAN 101: 10.1.0.0/24)" {
description """
Microservices deployment zone
| Property | Value |
|:---------|:------|
| VLAN | 101 |
| Network | 10.1.0.0/24 |
| Gateway | 10.1.0.1 |
"""
ProdUploadVm = Node_Vm "prod-upload-vm" {
description """
| IP | 10.1.0.12/24 |
| Port | 3001 |
"""
uploadApp = Node_App "Upload Service" {
instanceOf vault.uploadService
}
}
ProdRetrievalVm = Node_Vm "prod-retrieval-vm" {
description """
| IP | 10.1.0.13/24 |
| Port | 3002 |
"""
retrievalApp = Node_App "Retrieval Service" {
instanceOf vault.retrievalService
}
}
}
// Processing tier
ProcTier = Zone "Processing Tier (VLAN 102: 10.2.0.0/24)" {
ProdQueueVm = Node_Vm "prod-queue-vm" {
description "| IP | 10.2.0.14/24 | | Port | 5672 |"
queueApp = Node_App "Message Broker" {
instanceOf vault.jobs
}
}
ProdWorkerVm = Node_Vm "prod-worker-vm" {
description "| IP | 10.2.0.15/24 |"
workerApp = Node_App "Processing Worker" {
instanceOf vault.worker
}
}
}
// Data tier
DataTier = Zone "Data Tier (VLAN 103: 10.3.0.0/24)" {
ProdDatabaseVm = Node_Vm "prod-database-vm" {
description "| IP | 10.3.0.16/24 | | Port | 27017 |"
dbApp = Node_App "Database" {
instanceOf vault.docDB
}
}
ProdStorageVm = Node_Vm "prod-storage-vm" {
description "| IP | 10.3.0.17/24 | | Port | 9000 |"
storageApp = Node_App "Object Storage" {
instanceOf vault.minio
}
}
}
}
}
{Environment}{Service}Vm pattern (e.g., ProdUploadVm)prod-upload-vm){Tier} or {Function}Zone naming{Provider}{Service} (e.g., VirusTotalService)Node_App with instanceOf linking to model container| ❌ Don't | ✅ Do | Why |
|---|---|---|
ProdApiVM | ProdApigwVm | Inconsistent casing (VM vs Vm) |
prod_upload_vm variable | ProdUploadVm | Variable names should be PascalCase |
AppServers zone | AppTier zone | Zone names should be singular, use Tier/Zone suffix |
| No VLAN in description | VLAN 101: 10.1.0.0/24 in description | Networks require VLAN/CIDR for ops |
dev-upload-vm for production | prod-upload-vm | Environment prefix must match node |
Generic name Vm1, Server1 | ProdUploadVm | Names should indicate purpose |
model-deployment - Deployment structure and hierarchywrite-rich-descriptions - Detailed markdown tables in element descriptionsstructure-deployment-tiers - Organizing zones into logical tiers