Pre-launch checks

Before you ship a vibe-coded site, have Opus 5.5 send out 5 subagents to check these 20 things, then fix them all in one pass:
Consistent design
- Write a DESIGN.md first, and make every color, font size, spacing and corner radius follow it
- Keep the palette restrained and the type hierarchy clear

/goal Check [COMPONENT NAME OR PATH] and make sure it survives the content and states it will encounter in real use.
INSPECT ONLY THIS COMPONENT.
Do not modify it yet. Read its actual props, slots, states, data sources, and where it is used. Based on what it really accepts, select the stress cases that apply.
TEST THESE WHEN RELEVANT:

Before you ship a vibe-coded site, have Opus 5.5 send out 5 subagents to check these 25 things behind the pages, then fix them all in one pass:
Keys and access
- Keep secret keys like your OpenAI key and Stripe secret key on the server only. Search your frontend files and git history, and replace any that show up
- Check login and permissions on the server for every endpoint,…

Before you ship, have Opus 5.5 send out 4 subagents whose only job is to break your app, and split these 16 questions between them:
Security
- Do your bundled frontend JS or git history contain private keys like sk_ or service_role?
- Skip the UI and call your APIs directly, logged out or with someone else's ID. Does the server stop you?