show-skill-catalog

List this pack and route you to the right skill

QuickFull

Show Skill Catalog

List the skills from this pack and, if the user says what they are trying to do, point them at the matching skill. Do not search skills.sh.

Catalog

SkillWhat it does
/show-skill-catalogLists this pack and routes you to the right skill
/find-skillsSearch and install skills from the open ecosystem (skills.sh)
/grill-meRelentless interview to sharpen a plan or design
/fix-tech-debtFind README/TODO/FIX debt markers, group by domain, pick items, grill a plan
/request-refactor-planInterview, then file a GitHub issue with a tiny-commit refactor plan
/apply-solid-principlesApply SRP, OCP, LSP, ISP, and DIP to named or changed modules
/create-commitSplit work into logical conventional commits (uses agent session history when available)
/apply-best-practicesReact and Next.js performance rules from Vercel
/apply-prettierFormat files with the project's Prettier
/fix-lintFix Biome or ESLint issues
/apply-style-guideApply a repo style guide, or Google's if none
/write-e2e-testsWrite e2e tests for user-provided files
/write-unit-testsWrite unit tests for named units
/write-storybookWrite Storybook stories for named components
/write-handoffCompact this conversation so the next agent can continue
/review-codeTwo-axis review (standards + spec) since a fixed point
/develop-with-tddTests first, watch them fail, then write the code
/feature-sliced-designFeature-Sliced Design (FSD) v2.1 frontend architecture
/use-hybrid-folder-structureHybrid frontend layout: responsibility first, feature second

Present this as a readable list for a human (the table is the source of truth). One line per skill is enough unless they ask for more.

Which should I use?

If the user describes a current task, recommend from this pack only:

  • What can I do / what did I install? → /show-skill-catalog (this skill)
  • Sharpen a plan, design, or idea before building → /grill-me
  • Triage TODO/FIX/README tech debt and plan fixes → /fix-tech-debt
  • Plan a refactor as an RFC / GitHub issue with tiny commits → /request-refactor-plan
  • Implement, refactor, migrate, or "review and replace/improve …" → /grill-me first (skip only for pure Q&A or read-only review with no follow-up work); if /develop-with-tdd is installed, use it next for the implementation
  • Apply SOLID (SRP/OCP/LSP/ISP/DIP) to existing modules → /apply-solid-principles
  • Writing or refactoring React / Next.js for performance → /apply-best-practices
  • Format with Prettier → /apply-prettier
  • Fix Biome or ESLint → /fix-lint
  • Apply a style guide → /apply-style-guide
  • Write e2e tests (paths required) → /write-e2e-tests
  • Write unit tests → /write-unit-tests
  • Write Storybook stories → /write-storybook
  • Review a branch, PR, or work since a commit → /review-code
  • Commit the current work → /create-commit
  • Organize a frontend with FSD layers and slices → /feature-sliced-design
  • Reorganize src/ by file kind and feature → /use-hybrid-folder-structure
  • Hand this session to another agent → /write-handoff
  • Need a skill that is not in this pack → /find-skills

/feature-sliced-design and /use-hybrid-folder-structure are different frontend layouts. If the user names FSD, layers, or slices, use FSD. If they name hybrid, responsibility-first, or file-kind folders, use hybrid. If they only say "reorganize src/", ask which layout they want.

If more than one fits, list them in the order the human should run them (for example grill, then TDD, then commit).

If nothing in this pack fits, say so and suggest /find-skills.