skills.rest
a-scolan
a-scolanCOMMUNITY
Explore all skills by this author →
GitHub

name-deployment-nodes

Standardize deployment node naming across VMs, zones, environments, and external providers.

5|1|Updated Jan 15, 2026
Search Tags:#deployment#infrastructure#VM#naming#C4#zones#VLAN
One-click install
npx skills add https://github.com/a-scolan/c4-template --skill name-deployment-nodes
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: name-deployment-nodes
Source: https://github.com/a-scolan/c4-template/tree/main/.github/skills/name-deployment-nodes
Command: npx skills add https://github.com/a-scolan/c4-template --skill name-deployment-nodes

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

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.

Core Features & Use Cases

  • Naming formulas
  • Virtual Machines: {Environment}{ServiceName}Vm (PascalCase) with FQN in kebab-case like prod-apigw-vm
  • Zones: {Tier}Tier or {Function}Zone (PascalCase)
  • Environments: {Environment} (Prod, Staging, Dev, Test)
  • External Nodes: {Provider}{Service} (PascalCase)
  • Zones descriptions should include VLAN details and CIDR blocks

Quick Start

Review the naming formulas and apply them to a new deployment. Start by renaming existing VMs to the proper pattern, and update zone and environment names to align with the conventions.

Frequently Asked Questions about name-deployment-nodes

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

FAQPage Schema
How do I standardize VM naming conventions across deployment environments?▼

Standardize VM naming by applying the {Environment}{ServiceName}Vm pattern in PascalCase, then converting it to a kebab-case FQN like prod-apigw-vm. This ensures consistent infrastructure documentation across all deployment environments.

What naming formula should I use for infrastructure zones and tiers?▼

For infrastructure zones, use the {Tier}Tier or {Function}Zone naming formulas in PascalCase. Zone descriptions should also include specific VLAN details and CIDR blocks to maintain clear network documentation.

How do I name external provider nodes in my deployment infrastructure?▼

Name external provider nodes using the {Provider}{Service} formula in PascalCase. This convention keeps external infrastructure nodes consistently documented alongside your internal VMs, zones, and environments.

Do I need external tooling to enforce infrastructure naming conventions?▼

No external tooling is required to enforce these infrastructure naming conventions. You only need to apply the documented patterns for VMs, zones, environments, and external nodes to standardize your deployment documentation.

What is the best way to rename existing VMs to match infrastructure documentation standards?▼

The best way to rename existing VMs is to apply the {Environment}{ServiceName}Vm pattern and update their FQN to kebab-case. You should also align zone and environment names with these conventions during the update.

Related Skills

Explore More Software Engineering Skills→
jrjsmrtnjrjsmrtn

c4-deployment

Model deployment environments with C4 diagrams using Structurizr DSL.

Community
Advanced
torosenttorosent
3

smart-docs

Generate Markdown documentation with C4 architecture and workflow diagrams from codebases.

Community
Advanced
newnolnewnol
2

terraform-ansible-proxmox

Automate Proxmox VM and container provisioning with Terraform and Ansible.

Community
Advanced
matlockxmatlockx

coding-standards

Enforce universal coding standards across Go, Rust, Swift, TypeScript, JavaScript, React, and Node.js.

Community
Advanced