The Seedskill — Design skill for Claude Code

the-seedskill

A [Claude Code](https://claude.com/claude-code) skill (formerly `multitenant-saas-playbook`): an engineering playbook for building and evolving a real, paying-customer-facing multi-tenant SaaS. The reference stack is Next.js + Supabase/Postgres + Tailwind + Vercel, but the lifecycle and diagnostic habits generalize to other stacks.

It captures the operating discipline that came out of actually shipping a multi-tenant SaaS solo, over many rounds of: build → a real user tries it → something's subtly wrong → find the actual mechanism → fix it → check whether the same mechanism is lurking elsewhere. On top of that domain-specific residue — gotchas that cost real debugging time, design calls that turned out right, and calls that had to be reversed after real usage — it now carries a self-contained core of general engineering discipline adapted from [obra/superpowers](https://github.com/obra/superpowers): systematic debugging, evidence-before-claims verification, test-first development, a design → plan → execute workflow with approval gates, and code review / parallel-agent practices. You don't need superpowers installed to use it; if you have it, the two compose.

What's inside

• `SKILL.md` — the main playbook: the rules that don't bend, push/merge authorization discipline, "verify by seeing it, not by inferring it," how to diagnose a "this is broken" report, auditing for the same bug shape after a fix.
• `references/debugging-and-verification.md` — four-phase root-cause debugging, the three-fix rule, defense in depth, and the verification gate before any "done" claim.
• `references/testing-discipline.md` — red→green→refactor, tests that name the break they catch, and multi-tenant tests worth writing every time.
• `references/design-plan-execute.md` — classifying a request (spike / bounded / architectural), approval gates,