Profile My skills Saved Collections Edit profile Submit a skill

← all publishers

lglucas

@lglucas source repo

28 published skills

  1. ▌
    Pitch · lglucas
    Derive a 10-section pitch from BP v0.0.2 into docs/business/PITCH.md, then ask the founder whether the BP and Pitch should live online inside the product (/pitch, /investors) — running a redaction gate over what must never go public. Runs at WIZARD stage 2.9. Use when the user says "preciso de um pitch", "vou apresentar pra investidor", "quero pôr o BP no site", "dá pra deixar isso público?", "como resumo tudo isso em 10 slides?".
    0
    installs
  2. ▌
    Codemap · lglucas
    Mantém o CODEMAP.md — o índice de todo arquivo de código do projeto com uma linha sobre o núcleo de cada um, para achar arquivo sem ler o repositório inteiro. Regenere sempre que a lista, a descrição ou a contagem de linhas mudar — na prática, junto com qualquer edição de código —, ao fechar sprint e antes de release. Use quando o usuário disser "onde fica o arquivo de X?", "que arquivos mexem com Y?", "atualiza o mapa", "cadê o código que faz isso?" — ou quando você mesmo estiver prestes a varrer o repo procurando alguma coisa.
    0
    installs
  3. ▌
    Processize · lglucas
    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.
    0
    installs
  4. ▌
    Decision Log · lglucas
    Record WHY a decision was made — including the alternatives rejected — as a session-log entry or an ADR. Use after any decision touching architecture, product scope, pricing, compliance, security, or release strategy, when `multi-ai-review` reconciles a disagreement, and when the user says "anota isso", "registra essa decisão", "por que a gente escolheu isso mesmo?", "não lembro por que fizemos assim".
    0
    installs
  5. ▌
    Os Self Test · lglucas
    Verify the AI Dev Operating System is in a coherent state inside a project. Detects missing canonical files, broken cross-references, skills/agents/commands without frontmatter, registry drift, unindexed session logs, unwired hooks and gitignore gaps. Run after major edits to the OS, after renaming or moving canonical files, before opening a new sprint, before a release, and when the user says "tá tudo certo aqui?", "quebrou alguma coisa na estrutura?", "faz um check geral", "os links estão funcionando?".
    0
    installs
  6. ▌
    Secrets Scan · lglucas
    Scan project changes for leaked secrets, credentials, unsafe env handling, and accidental private data. This is the DETECTION pass over what is already in the tree; `secrets-discipline` is the preventive workflow that stops it happening. Run before every commit, before every release (invoked by `release-check`), and when the user says "vazou alguma chave aí?", "isso tá seguro pra subir?", "esqueci alguma senha no código?".
    0
    installs
  7. ▌
    Cost Watchdog · lglucas
    Flag potentially expensive technical choices BEFORE they are committed — AI model selection, hosting tier upgrades, third-party services with metered pricing, and DB patterns that explode with scale. Preventive counterpart to `usage-monitor`, which tracks real spend after launch. Triggers when the user says "posso usar o Opus pra isso?", "qual plano eu contrato?", "isso vai ficar caro?", "quanto custa rodar isso?", or whenever a paid tier or metered API is about to enter the stack.
    0
    installs
  8. ▌
    Daily Standup · lglucas
    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.
    0
    installs
  9. ▌
    Privacy Audit · lglucas
    Review any feature that collects, stores, processes, exports, or displays personal data — answering the nine questions in `.claude/rules/privacy-audit.md` (what data, why, where, who can access, how controlled, retention, logs, deletion/export, policy impact). Mandatory before merging personal-data changes. Triggers on auth, user profiles, exports, analytics, logging, and when the user says "vou guardar o CPF", "preciso pedir o e-mail", "e a LGPD?", "posso salvar isso do usuário?".
    0
    installs
  10. ▌
    Product Brief · lglucas
    Write docs/product/PRODUCT-BRIEF.md by reverse-engineering the approved prototype — every screen, the flow as actually clicked, and the gaps the prototype implied but never showed (empty states, errors, permissions, offline). Runs at WIZARD stage 4.1, after BP v0.0.2 and after a prototype direction is approved in Phase 3. Use when the user asks "o que exatamente a gente vai construir?", "quais telas o MVP tem?", "o que fica de fora?".
    0
    installs
  11. ▌
    Prototype Lab · lglucas
    Build three genuinely distinct HTML/CSS/JS prototype directions — brand, color, typography, UI, UX — from BP v0.0.2 and the research, then extract the approved one into docs/product/DESIGN-DIRECTION.md. Runs at WIZARD Phase 3, BEFORE the Product Brief and Technical Plan. Use when the user says "quero ver como vai ficar", "me mostra umas ideias de layout", "qual vai ser a cara do produto?", "que cores a gente usa?", or runs /prototype-lab.
    0
    installs
  12. ▌
    Registry Pick · lglucas
    Recommend external repo packs from docs/registry/ that fit a project's stack, domain, and constraints. Runs twice in the WIZARD — a design-scoped pass at stage 3.1 (before the Prototype Lab) and a full stack pass at stage 4.3 (after the Technical Plan). Also use when the user asks "que repos eu deveria usar?", or whenever a new need (security review, design system, deploy guidance) appears mid-build.
    0
    installs
  13. ▌
    Release Check · lglucas
    Pre-release gate covering tests, build, docs, changelog, privacy, security, and sprint closure. Delegates to `verify-build-works`, `secrets-scan`, and `privacy-audit` rather than re-checking by hand. Run before tagging a release, before closing a sprint, before a first deploy, and when the user says "tá pronto pra lançar?", "posso subir isso?", "fecha a versão", "dá pra publicar?".
    0
    installs
  14. ▌
    Rollback Safe · lglucas
    Undo the last AI change without losing user work. Use when the latest AI-applied change broke something, the user says "desfaz", "volta", "undo", "estraga tudo", or after `bug-triage-agent` selects a revert as the safest fix. Designed for vibe coders who don't yet trust git.
    0
    installs
  15. ▌
    Usage Monitor · lglucas
    Track real-world usage and cost across LLM providers, hosting, DB, and email after a feature ships or a launch happens. Complements `cost-watchdog` (preventive). Triggers when the user says "tô gastando muito", "quanto custa", "quanto deu de fatura", or after launch.
    0
    installs
  16. ▌
    Research Waves · lglucas
    Run the 3-wave research and validation process — Wave 1 competitor and market research, Wave 2 red team (devil's advocate, business/finance, technical/security), Wave 3 coordinator consolidation and BP writing. Runs at WIZARD stages 2.4–2.6, only after the user approves the plan. Use when the user asks "quem são meus concorrentes?", "esse mercado existe mesmo?", "isso tem furo?", "alguém já faz isso?", or runs /research-waves. Never fabricates market data.
    0
    installs
  17. ▌
    Sprint Roadmap · lglucas
    Create a 14–20 sprint roadmap in docs/SPRINTS.md plus individual sprint files, starting with Sprint -1 (consolidating the approved prototype into a design system). Runs at WIZARD stage 4.4, after BP v0.0.2, the approved prototype direction, the Product Brief, and the Technical Plan all exist. Use when the user asks "qual a ordem das coisas?", "quanto tempo isso leva?", "o que eu faço primeiro?", or runs /sprint-plan.
    0
    installs
  18. ▌
    First 100 Users · lglucas
    Get the first 100 real users for a vibe-coder SaaS without spending on ads. Hand-curated outreach, founder communities, niche-specific channels, retention check-ins. Activated after launch when the user asks "como pego os primeiros usuários", "ninguém tá usando", "como divulgo isso?", or after `launch-agent` Track A. Hand off to `grow-sustainably` once the project passes ~100 active users — this skill is conversation-driven and does not scale past that.
    0
    installs
  19. ▌
    Multi AI Review · lglucas
    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".
    0
    installs
  20. ▌
    Project Genesis · lglucas
    Drive the full 5-phase Project Genesis Wizard, from raw idea to first coding sprint. Use when starting a new project from the AI Dev Operating System, when the user runs /project-start, or when they say "vamos começar um projeto novo", "tenho uma ideia de SaaS", "quero criar um app", "por onde eu começo?". Enforces the prototype-before-spec ordering (Phase 3 before Phase 4) and refuses to write code before Phase 5.
    0
    installs
  21. ▌
    Feature Scaffold · lglucas
    Create a feature-based folder structure (components, actions, api, db, hooks, schemas, tests) plus an initial implementation plan, following `.claude/rules/feature-based-architecture.md`. Use when starting a new product feature during a coding sprint, and when the user says "vamos criar a tela de X", "quero adicionar tal funcionalidade", "onde eu coloco esse arquivo?", "como organizo isso?".
    0
    installs
  22. ▌
    Grow Sustainably · lglucas
    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".
    0
    installs
  23. ▌
    Sprint Management · lglucas bundle
    Manage the sprint lifecycle — open a sprint, maintain the sprint branch and docs, close it, update the changelog, and prepare tags. Powers /sprint-start, /sprint-plan and /sprint-close. Use when the user says "vamos começar a sprint", "fecha a sprint", "o que tá nessa sprint?", "terminei essa etapa", "qual o próximo ciclo?".
    0
    installs
  24. ▌
    Secrets Discipline · lglucas
    Enforce safe handling of API keys, tokens, passwords, and credentials — env files, `.gitignore` coverage, `.env.example` upkeep, rotation after exposure. This is the PREVENTIVE workflow; `secrets-scan` is the detection pass that finds what already leaked. Run when adding an integration, before commits, before a first deploy, and when the user pastes something that looks like a credential or says "essa é minha chave da OpenAI", "onde eu coloco esse token?", "posso commitar o .env?".
    0
    installs
  25. ▌
    Verify Build Works · lglucas
    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 (`rollback-safe`), after a fix from `bug-triage-agent`, before a commit, before pushing, and as part of `release-check`. Also when the user says "ainda tá funcionando?", "roda aí pra ver", "testa se não quebrou", "tá de pé?".
    0
    installs
  26. ▌
    Deploy Vercel Supabase · lglucas
    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.
    0
    installs
  27. ▌
    Plain Portuguese Explainer · lglucas
    Translate technical decisions, architecture, errors, or AI-generated jargon into plain Portuguese a vibe coder (non-dev) can act on. Use whenever the user signals confusion ("não entendi", "o que isso quer dizer", "explica de novo") or after producing technical artifacts.
    0
    installs
  28. ▌
    Business Plan Impact Review · lglucas
    Check every Business Plan change for downstream impact before accepting it — price moves projections, ARPU, LTV and positioning; persona moves GTM, UX and MVP scope; stack moves costs, roadmap and risks. Runs at WIZARD stage 2.8 when turning BP v0.0.1 into v0.0.2, and any time the BP is edited after approval. Use when the user says "mudei o preço", "troquei a persona", "cortei o escopo", "e se eu cobrar por assento?", or when `grow-sustainably` / `multi-ai-review` flag a pricing or packaging change.
    0
    installs