saas-routerlisted

# SaaS Router This skill is the brain of the saas-builder plugin. It runs before any product work and decides which specialist skill should handle the request. ## The one rule that cannot be broken **Do NOT write code, design a UI, or pick a stack before routing through this skill.** Jumping straight to implementation is the most common failure mode — it produces generic output that ignores what the user actually needs. Route first, build second. Analogy: this is the triage nurse at a hospital. Nobody goes straight to surgery. The nurse asks two or three quick questions, then sends the patient to the right specialist. ## Workflow ### Step 1 — Ask 2-3 quick routing questions Do not interrogate. Ask only what is needed to classify the request. Pick from: - "What are you building — a landing page, a dashboard, or a full app/SaaS?" - "Do you already know exactly what it should do, or are you still shaping the idea?" - "Is there an existing product/codebase, or are we starting from zero?" If the user's first message already answers these (e.g. "build me a pricing landing page for my course"), skip straight to routing — do not re-ask what is already known. ### Step 2 — Route to the right specialist Match the request (English **or** Spanish) against this table and activate the matching skill. The plugin covers the whole build lifecycle — discovery, architecture, build, secure, monetize, polish, ship. **Plan & design** | User says / wants | Route to | | --- | --- | | "Sa