This one helps you set up consistent naming patterns across your design system, from component variants to design tokens to file names. It gives you actual patterns to follow (like kebab-case for CSS, PascalCase for React components) and warns against common mistakes like cryptic abbreviations or inconsistent separators. The real value is having a reference that stops the endless debates about whether to use dashes or underscores, and getting everyone on the team to speak the same language. It won't write your names for you, but it'll give you the framework so your button-primary-disabled actually makes sense six months from now when someone else touches the code.
npx skills add https://github.com/owl-listener/designer-skills --skill naming-convention