What problem does it solve? When multiple screens manage tab names independently, inconsistent validation rules cause duplicate names, empty labels, and divergent behavior between add and edit flows. This Skill centralizes the naming rules so every tab-management screen behaves identically. ## Core Features & Use Cases - Unified Normalization Logic: Enforces trim-based canonicalization, empty-string rejection, and duplicate rejection through one shared function used by both add and edit paths. - Layered Architecture Guidance: Keeps validation decisions in the logic layer while the UI layer handles only error display and control flow. - Minimal Test Coverage: Defines a focused test set covering initial names, add-time duplicates, edit-time duplicates, and empty-string edit preservation. - Use Case: When renaming tabs across /work, /values, and /skills screens, apply this Skill to guarantee that a name rejected on one screen is rejected everywhere, then verify with the direct tests and a production build. ## Quick Start Ask the AI to apply the tab name normalization rules when adding or renaming a tab so trimming, empty-string rejection, and duplicate checks stay consistent across all screens.
