القائمة
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.
التثبيت باستخدام 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.
Walk a vibe-coder through deploying a Next.js + Supabase project to Vercel + Supabase production for the first time. Activated when the user says "vamos publicar", "como coloca no ar", "deploy", or after Sprint 1 ships and the app needs a public URL.
| name | daily-standup |
| description | 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. |
session-log/.git log --oneline -10).docs/SPRINTS.md or current sprint doc.CHANGELOG.md recent entries.☀️ Bom dia. Onde a gente parou:
✅ Feito ontem (ou na última sessão):
• [1-3 itens concretos]
🚧 Em andamento agora:
• [1-2 itens com % aproximada]
🎯 Próximo passo (o que faria sentido fazer agora):
• [1 item, prazo curto]
🚨 Bloqueios / decisões esperando você:
• [se houver — caso contrário "nada bloqueando"]
feat:, merge, branch aqui — isso é pra leitura rápida.☀️ Bom dia. Onde a gente parou:
✅ Feito ontem:
• Configuração inicial do banco (Supabase) feita
• Tela de login funcionando com magic link
• Email de boas-vindas testado
🚧 Em andamento:
• Tela de dashboard (~40% — falta a parte dos cards de métricas)
🎯 Próximo passo:
• Terminar os 3 cards do dashboard. Estimativa: 1-2h.
🚨 Bloqueios:
• Você precisa decidir se a primeira métrica é "clientes novos" ou "receita do mês". Te mando uma comparação rápida quando começar.