菜单
Smoke-test that the project still builds, the dev server starts, and the main user flow loads after a change. Run after every non-trivial edit, after a rollback, before a commit, and before pushing to remote.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Plan post-first-100-users growth without burning out the founder, the budget, or the user base. Pairs with `first-100-users` (which gets you to 100); this skill takes you from 100 to ~1000 sustainably. Activated when the user says "já tenho 100 usuários, e agora?", "como cresço sem queimar dinheiro?", "o WhatsApp 1-a-1 não escala mais".
Get a second (and third) AI opinion on hard-to-reverse decisions. Runs the same prompt through different agent roles or model families in parallel, then reconciles disagreements. Inspired by gstack's `/codex` cross-review pattern. Activated for architecture decisions, security-sensitive code, pricing/packaging changes, deploy gates, legal-adjacent text, or any decision the user flags as "não dá pra desfazer fácil".
Turn a manually-validated workflow into a documented, repeatable, and partially-automatable process. Use AFTER a task has been done at least 3 times by hand and is showing signs of repetition. Inspired by Sahil Lavingia's principle "do it manually until it works, then processize." Activated when the user says "tô fazendo isso toda semana", "vamos automatizar?", "isso já cansou", or after `daily-standup` flags repeated manual work.
Recommend external repo packs from docs/registry/ that fit a project's stack, domain, and constraints. Use during /project-start (after the Technical Plan), when the user asks "que repos eu deveria usar?", or whenever a new need (security review, design system, deploy guidance) appears mid-build.
Flag potentially expensive technical choices BEFORE they are committed. Watch for AI model selection, hosting tier upgrades, third-party services with metered pricing, and DB patterns that explode with scale.
At the start of a session (or on user request "o que a gente fez", "onde paramos"), produce a 4-bullet briefing — what's done, what's in progress, what's next, what's blocked. Replaces the dev habit of standup for solo vibe coders.
| name | verify-build-works |
| description | Smoke-test that the project still builds, the dev server starts, and the main user flow loads after a change. Run after every non-trivial edit, after a rollback, before a commit, and before pushing to remote. |
bug-triage-agent.rollback-safe operation.npm run typecheck
npm run lint
Stop and report at first failure. Don't continue if static layer is broken.
npm run build
If build fails, hand off to bug-triage-agent.
npm run dev
Confirm: process alive after 15s, HTTP 200 on http://localhost:<port>/, no fatal stderr.
For UI: load homepage + most critical authenticated page.
For API: hit GET /health (or main endpoint) → 2xx.
npm run test:smoke # if exists
🧪 verify-build-works
Step 1 — Static checks: ✅ typecheck OK, lint OK
Step 2 — Build: ✅ build succeeded in 14s
Step 3 — Dev server: ✅ ready on :3000, GET / → 200
Step 4 — Smoke tests: ⚠️ no test:smoke script — skipped
Step 5 — Visual sanity: ✅ home renders, login renders
Verdict: SAFE TO COMMIT.
If any step fails:
🧪 verify-build-works — ❌ FAIL at Step 2 (build)
Erro principal: src/features/auth/sign-in.ts(23,7): TS2322 ...
Próximo passo: invoco o bug-triage-agent.
Antes de avisar que terminou, eu sempre testo. Se algo está quebrado, eu falo agora — não na frente do primeiro usuário.
|| true.