agentsclimarketplace

Saas router

Skill MartinOlivero/saas-builder/skills/saas-router

This skill should be used FIRST whenever the user wants to create, build, design, ship, or prototype any digital product — a SaaS, web app, platform, MVP, landing page, sales page, dashboard, admin panel, backoffice, internal tool, API, database, auth, payments, or any user interface. Trigger phrases (English) include "build me a", "I want to create", "design a", "let's make a", "I have an idea for", "help me ship". Trigger phrases (Spanish) include "quiero construir", "armar una", "diseñar una", "hagamos un", "tengo una idea para", "necesito una app/SaaS/landing", "agregá login/pagos/base de datos", "subir a producción". It routes the request to the correct specialist skill instead of writing code or designing blindly.From its SKILL.md

Install
npx -y skills add MartinOlivero/saas-builder --skill saas-router

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

6.9 KB, ~1.6k tokens by cl100k_base, as published. Nobody here has run it

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 / wantsRoute to
"SaaS", "platform", "app", "MVP", "product" / "idea para", idea not fully definedproduct-discovery → architecture-primer → build skills → ui-design
"architecture", "how do I structure this", "scale", "what stack" / "cómo lo estructuro", "qué stack"architecture-primer
"landing", "sales page", "lead capture" / "página de ventas", "captar leads"landing-page (structure + copy) + design-taste-frontend (visual execution)
"portfolio", "marketing site", "agency site", "editorial/blog", "make a website that doesn't look AI-generated", website redesign / "portfolio", "sitio de marketing", "que no parezca hecho por IA", "rediseñar mi web"design-taste-frontend
"dashboard", "admin", "backoffice", "internal tool", "data table", product/app UI / "panel", "tablero", "interfaz de la app"ui-design (dashboard mode)
Component, colors, design system for an app, dark mode for product UI / "componente", "design system de la app"ui-design
"copy this design", "make it look like this screenshot/site", reference image of a web they like / "cloná esta web", "hacelo como esta captura"image-to-code

Web vs. app boundary (important): design-taste-frontend owns public-facing sites — landings, portfolios, marketing, editorial, redesigns — and explicitly does NOT do dashboards, data tables, or multi-step product UI. The moment the work is logged-in product UI (dashboards, admin, settings, data-heavy screens), route to ui-design instead. For a landing page, run both: landing-page sets the section order and copy, then design-taste-frontend executes the visual so it doesn't look templated.

Build the backend

User says / wantsRoute to
"design the API", "endpoint", "REST or GraphQL" / "diseñar la API", "un endpoint"api-design
"database", "schema", "model this data", "multi-tenant" / "base de datos", "modelar los datos"data-modeling
"login", "auth", "roles", "permissions", "SSO" / "agregar login", "roles", "permisos"auth

Secure & monetize

User says / wantsRoute to
Writing any endpoint / input / data write, "is this secure", "rate limit", "secrets" / "esto es seguro", "manejar datos de usuarios"secure-coding (runs alongside backend work)
"payments", "Stripe", "subscriptions", "pricing", "billing" / "cobrar", "suscripciones", "precios"payments

Polish & ship

User says / wantsRoute to
"slow", "performance", "Core Web Vitals", "bundle size" / "está lento", "optimizar"frontend-performance
"accessible", "a11y", "WCAG", "screen reader", "keyboard" / "accesibilidad"accessibility
"SEO", "meta tags", "social preview", "sitemap" / "que Google lo encuentre", "preview en WhatsApp"technical-seo
"PWA", "installable", "offline", "push notifications" / "que funcione offline", "instalable"pwa
"is this safe to ship", "pre-launch security check", "did I miss anything", before deploying / "antes de subir, ¿está seguro?"pre-ship-security
"deploy", "CI/CD", "GitHub Actions", "Sentry", "rollback", "staging" / "subir a producción", "monitoreo"deployment

Step 3 — Hand off with context

When routing, pass along everything already learned so the specialist does not re-ask. State the handoff explicitly, e.g. "This is a full SaaS with a fuzzy idea, so I'll start with product-discovery to lock the MVP, then architecture, then build."

The full-SaaS lifecycle

A from-scratch SaaS runs through these phases. Each feeds the next — don't skip, but don't force every phase if the user only asked for one slice.

  1. product-discovery — define the problem, the user, and the MVP scope.
  2. architecture-primer — decide the high-level system design and stack.
  3. Build — data-modeling (the schema) → api-design (the endpoints) → auth (who can do what) → ui-design (the interface). secure-coding runs throughout, not as a final step.
  4. Monetize — payments when it's time to charge.
  5. Polish — frontend-performance, accessibility, technical-seo, pwa as the product matures.
  6. Ship — pre-ship-security for a final security review of the finished code, then deployment for CI/CD, monitoring, and rollback.

Building UI before the MVP is defined, or picking a stack before knowing the scale, produces rework. But secure-coding is never deferred — preventing a vulnerability is always cheaper than auditing one out later.

When NOT to route

If the user explicitly asks for one specific thing ("just give me a Tailwind navbar"), honor it and go straight to ui-design. Routing serves the user — it is not a toll booth. Use judgment: ambiguity means ask; clarity means act.

What ships with it

Read from the repository

Just SKILL.md. No reference files, no scripts.

Gives 0 of the 12 instructions most design frontend skills give in ~1.6k tokens

Counted across 1,179 of the 2,086 authors here whose files we hold, read 2026-09-06

  • Commit to a bold aesthetic directionin 31 of 1179, across 24 files
  • Prefer component composition over inheritancein 28 of 1179, across 14 files
  • Animate only transform and opacity propertiesin 27 of 1179, across 22 files
  • Memoize expensive computations with useMemoin 26 of 1179, across 13 files
  • Use semantic HTML elementsin 24 of 1179, across 23 files
  • Virtualize long lists for performancein 21 of 1179, across 10 files
  • Use CSS variables for design tokensin 20 of 1179, across 14 files
  • Implement loading, empty, and error statesin 20 of 1179
  • Lazy load heavy components with Suspensein 19 of 1179, across 8 files
  • Respect prefers-reduced-motion media queriesin 18 of 1179, across 10 files
  • Prioritize CSS-only animations for HTMLin 18 of 1179, across 16 files
  • Use compound components for related UI elementsin 18 of 1179, across 7 files

Said here and by no other author read

  • ask two or three quick routing questions
  • skip routing questions if the request is already clear
  • match the request to the correct specialist skill
  • pass all learned context to the specialist
  • route to product-discovery for undefined SaaS ideas
  • route to ui-design for logged-in product interfaces

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.

Keep looking

Skills are one crate of 611,884. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.