Skills Router

A meta-skill directory — maps any task to the right specialist skill before you write a single line of code.

Agent Protocol

1. Check for project context first. Before routing, look for a project memory file in the project root and read it for stack-specific rules that override generic skill guidance. Check for any of these (whichever exists):
   • GEMINI.md — Gemini / Antigravity
   • CLAUDE.md — Claude Code
   • AGENTS.md — OpenAI Codex
   • .cursorrules — Cursor
   • .github/copilot-instructions.md — GitHub Copilot
   • CONVENTIONS.md — Aider and others
2. Match your task to the domain table below.
3. Find the skill's SKILL.md file. Skills may be installed locally or globally. Before concluding a skill is missing, you must check the following locations using proper absolute paths (resolve the user's home directory programmatically before using file-reading tools; do NOT pass literal ~/ or %USERPROFILE% strings to tools like view_file):
   • Central Global: <USER_HOME_DIR>/.agents/skills/<skill-name>/SKILL.md (Check here first, this is the source of truth)
   • Agent-Specific Global: <USER_HOME_DIR>/<YOUR_AGENT_DIR>/skills/<skill-name>/SKILL.md (e.g. .cursor/skills, .gemini/antigravity/skills, .cline/skills)
   • Local Workspace: ./.agents/skills/<skill-name>/SKILL.md or ./.cursor/skills/<skill-name>/SKILL.md
4. If not found in any of these paths, run the install command from the table (if one exists), appending -g to ensure it installs to the central .agents directory. Let the installation finish.
   • Self-Healing Protocol: If the install command explicitly fails (e.g., repository not found), immediately run npx skills find <skill-name> to get the updated, verified command. Use it to install, and then update the table in this SKILL.md file with the corrected link permanently.
5. Load the skill using the view_file tool on the exact absolute path to SKILL.md. Once loaded, you MUST output "Loaded specialist skill: [name]" in your chat response so the user sees the routing succeeded.
6. Follow that skill's instructions for the task.
7. Before claiming done, load the verification-before-completion skill (find it in the tables below and follow steps 3-5 to load it).
8. If you used a skill not listed here, add it to the Pending Review section at the bottom — never to the live tables.

If no skill matches, you MUST append a proposed skill name and task description as a bullet point to the Still Needed section of this document, then proceed with built-in knowledge.

Pre-Baked Critical Rules (Always Active)

These rules apply regardless of which skill you load:

• Supabase RLS: Always wrap auth.uid() in (SELECT auth.uid()) — prevents per-row re-evaluation
• One RLS policy per table/role/action — never create duplicate permissive policies
• Supabase browser client: Singleton cached on globalThis only — prevents "Multiple GoTrueClient instances"
• Server Components by default — 'use client' only when strictly required (event handlers, hooks, browser APIs)
• Stripe webhooks: Always verify signature with stripe.webhooks.constructEvent() before processing

Domain → Skill Routing Table

⚛️ React / Next.js / Frontend

🗄️ Database / Supabase / Postgres

💳 Payments / Billing

⛓️ Blockchain / Web3 / Solana

🧪 Testing / QA

🚀 Deployment / DevOps / Infra

🤖 AI / LLM / Agents

📱 Mobile

🎨 Design / UX

📊 Backend / TypeScript / Architecture

📧 Communications / Email

🖼️ Documents / Media

✍️ Content / Writing / Marketing

🏷️ Product / Growth / CRO

📚 Docs / README

🔧 Agent Productivity / Skills Management

✅ Verification

Still Needed (run npx skills find <name> to resolve)

• superdesign
• typescript-expert
• nestjs-expert
• solana-vulnerability-scanner
• paywall-upgrade-cro
• signup-flow-cro
• pricing-strategy
• launch-strategy
• game-changing-features

⏳ Pending Review

Agents: Append newly discovered skills HERE only. Never edit the live routing tables above. Humans: Review entries below, verify the install command on skills.sh, then promote to the correct table.

🔒 Security Note

Before promoting any pending entry:

1. Verify the GitHub repo exists and is from a trusted owner
2. Check the skill's page on skills.sh for security badges (Socket, Snyk, Gen Agent Trust Hub)
3. Review the SKILL.md content in the repo before installing
4. Never install skills from repos you don't recognise

Install Note

• Verified npx skills add https://github.com/... commands were confirmed on skills.sh
• npx skills find <name> searches skills.sh live and returns the confirmed install command
• IMPORTANT: Always append -g to the npx skills add commands listed in the tables above when executing them to ensure central installation.