Optimizer Router

The repo has 64+ focused skills. Do not guess from memory and do not read the whole tree. Use the catalog, pick the smallest set, then follow the target skill.

1. Find the signals

From the request and the repo, detect:

• Framework/runtime: React, Next.js, Vue, Nuxt, Angular, Svelte, Solid, Astro, Remix, TanStack Start, Node, or a backend language.
• Library/style: component kit (MUI, Mantine, shadcn, ...), styling system (Tailwind, CSS, Sass, CSS-in-JS), motion/3D.
• Infra: Docker, Kubernetes, Terraform.
• System shape: monolith/modular/microservices/serverless, shared DB, coupling.
• Symptom: slow load, slow interaction, memory, bundle size, database, reliability, cost, migration.

If the user named a specific technology, skip the router and use that skill. The router is only for ambiguity.

2. Search the catalog

python tools/catalog.py search "slow nextjs mui table"
python tools/catalog.py search "postgres connection pool" --limit 5
python tools/catalog.py list --domain backend

If the catalog is missing:

python tools/catalog.py

Read skills/CATALOG.md for the full grouped list.

3. Route by domain

Focused libraries live under: skills/web/_components/skills/ (Aceternity, Base UI, Bulma, coss, Create UI, DaisyUI, Float UI, Flowbite, Franken UI, Headless UI, HeroUI, Mantine, MUI, Park UI, Preline, Radix, ReUI, shadcn, TailGrids, tweakcn, Untitled UI).

Styling systems: bootstrap, pandacss, sass-scss, stylex, tailwindcss, twind, unocss, vanilla-extract.

4. Pick at most 3

• Primary: the framework/runtime/language.
• Secondary: the component library, styling system, motion/3D or infra that is actually involved.
• Architecture: only if the problem is boundaries/data/distribution, not a local performance bug.

Examples:

• “Slow Next.js product page with MUI tables” → skills/web/nextjs + skills/web/_components/skills/mui.
• “Vue app with Tailwind feels sluggish” → skills/web/vue + skills/styles/tailwindcss.
• “Rails endpoint N+1” → skills/backend/ruby.
• “Docker image is 2 GB” → skills/devops/docker.
• “Should we split this monolith?” → skills/architecture (+ framework skill only if implementation detail matters).
• “Billing service shares the orders DB” → skills/architecture + skills/backend/node or the relevant language.

Do not run three audits blindly. Pick the primary constraint; add a second skill only when its layer is part of the problem.

5. Ask one question only if needed

If the main stack is still ambiguous, ask exactly one question:

What is the main app stack: React/Next.js, Vue/Nuxt, Angular, Svelte, Solid, Astro, Remix, TanStack Start, a backend language, or infrastructure?

Do not ask about every library; inspect package.json, manifests, lockfiles and the tree first.

6. Hand off

Read the chosen skill's SKILL.md and follow its workflow. Tell the user:

1. which skill(s) you chose,
2. why (one line),
3. what you will run first (the skill's audit command).

Do not summarize a skill's advice from memory; open the file.