skills.rest
dpalfery
dpalferyCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

azure-naming

Automates Azure resource naming using the slug-env-region-app pattern with length constraints.

1|Updated Jul 21, 2025
Search Tags:#azure#standardization#resources#governance#environment#naming
One-click install
npx skills add https://github.com/dpalfery/motorcycle-rag-system --skill azure-naming
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: azure-naming
Source: https://github.com/dpalfery/motorcycle-rag-system/tree/main/.claude/skills/azure-naming
Command: npx skills add https://github.com/dpalfery/motorcycle-rag-system --skill azure-naming

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Inconsistent Azure resource naming across teams leads to governance gaps, auditing difficulties, and confusion when managing inventories.

Core Features & Use Cases

  • Enforces the canonical {slug}-{environment}-{region}-{app} naming pattern for all Azure resources.
  • Provides a reference table mapping common resource types to their slugs and examples to standardize naming across environments.
  • Assists in governance and lifecycle management by giving clear, repeatable naming rules and examples for onboarding new resources.

Quick Start

Apply the azure-naming rule by constructing resource names in the form {slug}-{env}-{region}-{app} using the correct slug for each resource type.

Frequently Asked Questions about azure-naming

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

FAQPage Schema
How do I enforce Azure resource naming consistency across teams?▼

Azure resource naming consistency is enforced by applying a strict slug-env-region-app pattern to all resources, which improves governance, auditing, and cross-team collaboration.

What is the canonical naming pattern for Azure resources?▼

The canonical Azure naming pattern is constructed as {slug}-{environment}-{region}-{app}, using a reference table to map common resource types to their correct slugs.

How do I handle Azure resource name length constraints during standardization?▼

Azure naming length constraints are handled through automated truncation and explicit mappings, ensuring the standardized slug-env-region-app pattern remains valid for each specific resource type.

Can I use this naming standardization for Azure governance and lifecycle management?▼

Yes, Azure naming standardization supports governance and lifecycle management by providing repeatable rules and examples for onboarding new resources across different environments.

What are the limitations of using a strict naming pattern for Azure resources?▼

The strict naming pattern requires valid slug, environment, region, and app values, meaning non-standard identifiers will be rejected or truncated to fit specific Azure resource length constraints.

Related Skills

Explore More Software Engineering Skills→
henkisdabrohenkisdabro
77

gtm-best-practices

Audit Google Tag Manager containers and apply standardized naming conventions.

Community
Intermediate
jguadagnojguadagno
18

azure-deployment-preflight

Validate Azure Bicep templates and configurations before deployment.

Community
Intermediate
masermediagroup-stackmasermediagroup-stack
1

resource-tagging

Audit and enforce cloud resource tagging across AWS, Azure, and GCP.

Community
Advanced
oscardlfroscardlfr
1

lint-resources

Validate Android string resource naming conventions in strings.xml files.

Community
Intermediate