design_patterns-snob_naming

Standardize compound identifiers with hyphen-delimited and underscore-joined naming schemes.

2|Updated Jun 26, 2025

Search Tags:#snob_n naming #naming_convention #hyphen_underscore #package_name #directory_name #type_string #coding_standards

Ready to run

npx skills add https://github.com/amarbel-llc/dodder --skill design-patterns-snob-naming

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: design_patterns-snob_naming
Source: https://github.com/amarbel-llc/dodder/tree/main/.claude/skills/design_patterns-snob_naming
Command: npx skills add https://github.com/amarbel-llc/dodder --skill design-patterns-snob-naming

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Snob naming provides a clear two-level naming scheme that prevents ambiguous or inconsistent identifiers by splitting semantic parts with hyphens and joining words within parts with underscores.

Core Features & Use Cases

Enforces a two-level hierarchy for names (hyphen-separated components and underscore-separated words)
Helps review and standardize names for packages, directories, types, and skills
Use Case: When naming a new package, apply the Snob rule to yield a stable, consistent name like design_patterns-snob_naming

Quick Start

Apply snob naming to a sample identifier such as 'design_patterns-snob_naming' to illustrate the rule.

Frequently Asked Questions about design_patterns-snob_naming

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

FAQPage Schema

What is the best way to standardize compound identifiers for packages and directories?▼

The best way to standardize compound identifiers is using a two-level naming scheme that separates distinct semantic parts with hyphens and joins words within each part using underscores. This prevents ambiguous directory names during refactoring.

How do I apply a consistent naming convention to type strings and skills?▼

You apply a consistent naming convention by enforcing a hyphen-delimited and underscore-joined structure across type strings and skills. This splits semantic components clearly, yielding stable identifiers like design_patterns-snob_naming for projects.

When do I need a hyphen and underscore naming scheme for coding standards?▼

You need a hyphen and underscore naming scheme when reviewing or refactoring code to prevent inconsistent identifiers. It enforces a two-level hierarchy that splits semantic parts with hyphens and joins words within parts with underscores.

Does this naming convention handle edge cases like multiple words in a single package name component?▼

Yes, this naming convention handles edge cases by enforcing underscores to join multiple words within a single semantic part. It provides clear examples and edge-case handling to ensure package names remain structured and unambiguous.

Why use a two-level hierarchy for directory names instead of camelCase?▼

A two-level hierarchy for directory names prevents ambiguous or inconsistent identifiers by separating distinct semantic parts with hyphens and joining words within parts with underscores, providing clearer structural boundaries than camelCase.

Can I use this naming convention to review and standardize names across existing projects?▼

Yes, you can use this naming convention to review and standardize names for packages, directories, types, and skills across existing projects. It applies the hyphen-delimited and underscore-joined rule during refactoring tasks to yield consistent identifiers.