naming

Enforce naming conventions for enums and external contract values in code.

3|Updated Dec 31, 2025
One-click install
npx skills add https://github.com/andredezzy/maccing --skill naming-andredezzy
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: naming
Source: https://github.com/andredezzy/maccing/tree/main/skills/engineering/naming
Command: npx skills add https://github.com/andredezzy/maccing --skill naming-andredezzy

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill helps developers adhere to precise naming conventions, improving code readability and maintainability.

Core Features & Use Cases

  • Closed Set Enums: Ensures that internal states are represented as enums, enhancing code clarity and preventing errors.
  • External Contract Compliance: Guides naming of values that cross boundaries, ensuring consistency with external systems.
  • Avoiding Common Mistakes: Provides rules to avoid common naming pitfalls, such as vague names or unnecessary complexity.

Quick Start

Use the naming skill to rename a function to a more precise name.

Frequently Asked Questions about naming

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

FAQPage Schema
How do I enforce naming conventions to improve code readability?

Apply precise naming rules to variables and functions to prevent vague names and unnecessary complexity, directly improving code readability and long-term maintainability.

What is the best way to name closed set enums for internal states?

The best way to name closed set enums is to ensure internal states are explicitly represented as enums. This enhances code clarity and prevents invalid state errors in your application logic.

How do I maintain external contract compliance when naming boundary values?

Maintain external contract compliance by following guided naming rules for values that cross system boundaries. This ensures naming consistency with external systems and prevents integration mismatches.

What are common naming pitfalls and how can I avoid them?

Common naming pitfalls include using vague names or introducing unnecessary complexity. Avoid them by adhering to enforced rules that require precise, clear naming across all coding environments.

Do I need a specific framework to apply these naming conventions?

No specific framework is needed. These naming conventions apply to all coding environments where consistent naming practices are beneficial, requiring only a general understanding of enum usage and contract naming.