validate-naming

Validate extension names against reserved names, duplicates, and kebab-case conventions.

1|Updated Apr 20, 2026
One-click install
npx skills add https://github.com/Largo2z9/phantomos --skill validate-naming
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: validate-naming
Source: https://github.com/Largo2z9/phantomos/tree/main/.skills/skills/validate-naming
Command: npx skills add https://github.com/Largo2z9/phantomos --skill validate-naming

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents invalid extension names by detecting reserved names, duplicates, formatting violations, and semantic overlaps before new entities are created.

Core Features & Use Cases

  • Reserved Name Validation: Checks proposed extension names against protected core entity names to avoid collisions.
  • Duplicate and Convention Checks: Reviews existing extensions for duplicates and enforces kebab-case naming with MECE principles.
  • Use Case: When creating a new PhantomOS extension, use this Skill to confirm the name is unique, compliant, and ready for the next scaffold-extension phase.

Quick Start

Ask the Skill to validate the proposed extension name before creating a new extension.

Frequently Asked Questions about validate-naming

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

FAQPage Schema
How do I prevent extension naming conflicts before creating a new extension?

You prevent extension naming conflicts by validating proposed names against reserved core entities and existing extensions. This process detects duplicates and semantic overlaps to confirm the name is unique before creation.

What is kebab-case naming convention validation for extensions?

Kebab-case naming validation enforces lowercase letters separated by hyphens for extension names. It applies MECE principles to ensure names are mutually exclusive and collectively exhaustive without formatting violations.

How do I check if an extension name is a reserved name?

You check if an extension name is reserved by validating it against protected core entity names using brand and index data structures. This identifies collisions with protected names before entity creation.

Does extension name validation modify my workspace files?

No, extension name validation does not modify workspace files. It requires access to brand and index data structures to perform read-only validation checks for naming collisions and convention enforcement.

What's the best way to enforce MECE principles when naming extensions?

To enforce MECE principles when naming extensions, validate proposed names for semantic overlaps and duplicates. This ensures names are mutually exclusive and collectively exhaustive within the extension index.

Why does extension creation fail due to naming collisions?

Extension creation fails due to naming collisions when proposed names match reserved core entities or existing extensions. Validation detects these semantic overlaps and formatting violations before the creation phase begins.