Validates file and variable naming conventions against project standards. Scans for files that violate kebab-case naming, variables that aren't camelCase, constants that aren't UPPER_SNAKE_CASE, and types/classes that aren't PascalCase. Outputs a table of findings with severity levels and suggested fixes. Use this skill whenever the user asks to "check naming", "lint names", "validate conventions", "find naming violations", "enforce naming standards", or says things like "are my file names consistent?", "check my code style", or "find convention violations". Also use it when the user mentions naming conventions, casing rules, or asks about camelCase vs kebab-case in their project — even if they don't explicitly say "naming checker".
Break down feature requests, user stories, and epics into structured, implementable sub-tasks with T-shirt size estimates (XS–XL), dependencies, and acceptance criteria. Includes a risk assessment step for tasks that touch shared code paths, require database migrations, or affect cross-cutting concerns. Use this skill whenever the user asks to "break down", "decompose", "split up", "plan implementation of", "task out", "scope", "estimate the work for", "turn into tickets", "plan sprint work for", or "create sub-tasks for" a feature, story, or epic — even if they phrase it casually like "what work do we need to do for X" or "how would I implement Y". Also use it when someone pastes a user story or feature description and asks for next steps or an implementation plan. Use this skill when the user wants executable sub-tasks with estimates — not for high-level architecture discussions or pure design brainstorming.