Zuno

You can rename components and files to kebab-case conventions, validate that new contributions follow project rules and architecture before acceptance, and remove files together with their related tests, styles, stories, mocks, and references such as imports, routes, and nav links.

Frontend and full-stack engineers maintaining component-based codebases benefit most, especially teams enforcing naming conventions, reviewing contributions against project architecture rules, and performing dead code or refactor cleanup in modules like launch-pad or marketplace.

Invoke it when a file is unused or when explicitly removing a feature or route. It deletes the target file plus related tests, styles, stories, and mocks, and when removing by request it also cleans up all references including imports, routes, and navigation links.

Use it when renaming files or components, when conventional or 'suitable' names are requested, or when adding new files to modules such as launch-pad or marketplace. It produces kebab-case (xxx-yyy) names that fit the feature or project context.

No external dependencies are specified in the manifest. The skills operate on an existing project codebase with established conventions, requiring only access to the project's files, components, routes, and contribution patterns to validate or modify them.