From ludus-toolkit
Create, edit, and validate Ludus range configuration YAML including VM definitions, domains, networking, router settings, testing behavior, and role configuration. Use when users need help authoring or reviewing `ludus` range config files.
How this skill is triggered — by the user, by Claude, or both
Slash command
/ludus-toolkit:ludus-range-configThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Use this skill to build safe, valid Ludus YAML configurations and explain tradeoffs in topology, networking, and role design.
Use this skill to build safe, valid Ludus YAML configurations and explain tradeoffs in topology, networking, and role design.
Always suggest the YAML schema validation header at the top of configs:
# yaml-language-server: $schema=https://docs.ludus.cloud/schemas/range-config.json
Use {{ range_id }} template strings in vm_name and hostname fields. This resolves to the user's range ID (e.g., "JS").
Windows hostnames are limited to 15 characters due to NETBIOS.
VLANs must be 2-255 and become the third octet of the VM's IP (e.g., vlan 10 = 10.X.10.Y).
ip_last_octet must be unique within a VLAN.
Set linux: true for Linux VMs, windows: key for Windows VMs, macOS: true for macOS VMs.
Domain roles are: primary-dc, alt-dc, or member.
role_vars must be a dictionary - do not use hyphens to prefix variables.
Roles must exist on the server before deploy — verify installed roles and add any that are missing.
references/schema.md for full schema details, valid values, defaults, and complete examples.https://docs.ludus.cloud/docs/configuration for official configuration guidance.https://docs.ludus.cloud/schemas/range-config.json for schema-backed validation.npx claudepluginhub dotknewt/toolkits --plugin ludus-toolkitEnforces cross-project coding conventions for naming, readability, immutability, and code-quality review. Activates on new projects, refactoring, or code review.