菜单
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.
用 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.
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.
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 | registry-pick |
| description | 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. |
Read docs/registry/INDEX.md and docs/registry/packs/*.md, match the project's signals against pack tags and fit-signals, and produce a short, opinionated recommendation.
This skill does NOT install anything. It shortlists what is worth installing for THIS project.
Before recommending, gather these from the project:
| Signal | Source | Example |
|---|---|---|
| Stack | package.json, Anchor.toml, requirements.txt, Gemfile, Cargo.toml | @solana/web3.js → web3/Solana |
| Domain | docs/business/BUSINESS-PLAN.md, docs/product/PRODUCT-BRIEF.md | "PHI" → healthcare, "pagamentos" → fintech |
| Compliance | docs/technical/TECHNICAL-PLAN.md security/privacy section | LGPD, GDPR, HIPAA, PCI |
| UI surface | Product Brief, prototype-lab presence | mobile, dashboard, B2C web |
| Public/private | repo metadata, deploy intent | public GitHub → enables gitleaks |
| Team familiarity | user statement | "primeira vez com Claude Code" → start with #foundations only |
If signals are missing, ask 2–3 targeted questions BEFORE recommending. Never invent stack details.
docs/registry/INDEX.md to enumerate available packs.When NOT to install matches the project shape.Conflicts and overlaps section in each one-pager (pick one of overlapping packs based on context).must-install → recommended → optional → skip-for-now.git clone / npm install itself).## Registry recommendation for <project name>
Project signals detected:
- Stack: <e.g. Next.js + Supabase>
- Domain: <e.g. SaaS B2B compliance>
- Compliance: <e.g. LGPD>
- UI: <e.g. dashboard + landing>
- Public repo: <yes/no>
### Must install
| Pack | Why for this project | How |
|------|----------------------|-----|
| `<slug>` | <one sentence> | `<install command>` |
### Recommended
| Pack | Why | How |
|------|-----|-----|
| ... | ... | ... |
### Optional
| Pack | Why | How |
|------|-----|-----|
| ... | ... | ... |
### Skipped (and why)
- `<slug>` — <reason from `When NOT to install`>
### Open questions before installing
- ...
docs/registry/INDEX.md.docs/registry/packs/<slug>.md.archived packs.License: check upstream, surface that as an open question.When the user says "encontrei um repo novo, adiciona aí":
docs/registry/packs/<slug>.md from the template in docs/registry/README.md.docs/registry/INDEX.md.docs/registry/tags/<tag>.md files.UPSTREAM-SOURCES.md.docs/registry/README.mddocs/registry/INDEX.mddocs/registry/tags/UPSTREAM-SOURCES.md