Business agent: strict QA requirements — product still broken, must fix before Phase 2

skills/business/SKILL.md

@@ -133,19 +133,31 @@ You have a Hetzner API token with full read+write access. You can:
 - Message tool for contacting the user
 - Cron for scheduling (if needed)
 
-## Quality First — MANDATORY
+## Quality First — MANDATORY (NON-NEGOTIABLE)
 
-**NEVER move to customer acquisition until the product actually works end-to-end.**
+**NEVER move to customer acquisition until the product is POLISHED and PROFESSIONAL.**
 
-Before Phase 2 (Launch), you MUST verify:
-- Every button on the landing page works (not mailto: links, not broken JS)
-- Free tier signup works completely — user gets an API key without human intervention
-- Pro tier checkout works completely — Stripe payment → API key provisioned
-- Every API endpoint works with a real API key
-- Error handling works (bad input, rate limits, expired keys)
-- Test it yourself. If you can't click through the entire flow and get a working PDF, it's not ready.
+The human has repeatedly found broken buttons, console errors, and half-assed flows. This is unacceptable. You are the CEO, the developer, AND the QA team. The human should NEVER find bugs — that's YOUR job.
 
-**You are the QA team.** The human should never find broken buttons. Test everything before declaring it done.
+### QA Checklist — MUST PASS before Phase 2:
+1. **Zero console errors** — open the browser tools, check for JS errors, fix ALL of them
+2. **Every button works** — click every single button on every page. If it doesn't do something useful, remove it or fix it.
+3. **Full free signup flow** — landing page → enter email → get API key → copy key → use key to generate a PDF → PDF downloads correctly
+4. **Full pro signup flow** — click Pro → Stripe checkout loads → payment works → API key provisioned with pro limits
+5. **API documentation** — if there's a "Docs" button, it must link to REAL documentation with request/response examples, auth instructions, error codes. Not a list of endpoint names.
+6. **Landing page is professional** — no broken layouts, no placeholder text, no dead links
+7. **Error handling** — bad API key → clear error, missing params → clear error, rate limited → clear error with retry-after
+8. **Mobile responsive** — landing page looks good on mobile too
+
+### How to QA properly:
+- Use `curl` to test every API endpoint with valid AND invalid inputs
+- Use the browser tool to load the landing page and check for console errors
+- Click through EVERY user flow as if you're a new customer who's never seen the product
+- If something is broken, FIX IT before logging the session as "done"
+- **Do NOT say "tested end-to-end ✅" unless you actually tested EVERY flow INCLUDING the browser UI**
+
+### Definition of Done:
+A stranger should be able to land on docfast.dev, sign up, get an API key, and generate their first PDF within 2 minutes, with ZERO confusion and ZERO errors. If that's not the case, you're not done.
 
 ## Anti-Patterns (Don't Do These)