naming-convention

Files (1)

• SKILL.md

SKILL.md (first lines)

# Naming Convention

Use this skill to turn vague naming requests into convention-compliant names.

## When to use

Use this skill when the user:

- asks for a name for a server, host, DNS entry, or similar infrastructure resource
- asks whether an existing name follows the convention
- asks to rename something to match the standard
- asks what an environment code, purpose code, or pattern segment should be
- needs multiple candidate names that all stay consistent with the same convention

If the task is clearly about naming consistency, apply this skill even if the user does not explicitly say "naming convention".

## Source of truth

If the user's target resource is outside the documented scope, say so clearly and ask the user for their team's convention rather than guessing.

## Inputs to gather

Ask only for the missing inputs.

For the global naming pattern, gather:

- `project`
- `datacenter`
- `purpose`
- `number`

For the DNS naming pattern, gather:

- `project`
- `datacenter`
- `dns_domain`

Ask concise follow-up questions when required.

### Required clarifications for the global pattern

Ask the user for:

1. **Project**
   Short project identifier.

2. **Datacenter**
   The datacenter code to use.

3. **Purpose**
   Must map to one approved purpose code.

4. **Number**
   A unique number for this resource.

### Required clarifications for the DNS pattern

Ask the user for:

1. **Project**
2. **Datacenter**
3. **DNS domain**

## Patterns

Use these canonical patterns exactly.

### Global naming pattern

```text
[project]-[datacenter]-[purpose]-[number]
```

### DNS naming pattern

```text
[project].[datacenter].[dns_domain]
```

Approved purpose codes

Use only these approved purpose codes unless the user explicitly tells you their team has extended the list:

- app — application server
- bkt — storage bucket
- cfg — configuration management server
- dns — name server
- fwl — firewall
- ftp — SFTP server
- lb — load balancer server
- mon — monitoring server
- pdu — power distribution unit
- prx — proxy server
- rtr — router
- sql — database server
- ssh — SSH jump or bastion host
- sto — storage server
- swt — switch
- ups — uninterruptible power supply
- vcs — version control software server
- vpn — VPN server
- web — web server

If the user's purpose does not clearly map to one of these codes, ask before inventing a new code.

## Output format

When you have enough information, present the answer in this format.

### For a proposed name

Proposed name

```text
<final-name>
```

┌──────────────────────────┬─────────┬───────────┐
│ Segment │ Value │ Meaning │

From woernfl/ai-lab, MIT.

More from woernfl/ai-lab