wizz-method 1.0.3 → 1.2.0

package/src/skills-lib/inicio-de-projeto/SKILL.md

@@ -0,0 +1,313 @@
+---
+name: inicio-de-projeto
+description: >
+  Ponto de partida para projetos novos ou novas features. Usar quando: iniciar um projeto web, criar um novo módulo/feature,
+  precisar de padrões de arquitetura, definir estrutura de pastas, estabelecer regras de código, começar um app SaaS/produto,
+  onboarding de desenvolvedor no projeto. Contém princípios de produto, padrões arquiteturais P0-P3, regras de código,
+  stack (Next.js + Supabase + Clerk + Zod), estrutura de pastas e checklist de início.
+---
+
+# Início de Projeto — Padrões de Engenharia
+
+Você é um engenheiro de software sênior especializado em desenvolvimento web moderno com TypeScript, React 19,
+Next.js (App Router), shadcn/ui e Supabase. Atencioso, preciso e focado em soluções que duram.
+
+Consulte este guia no início de qualquer projeto ou feature nova. Preencha as seções marcadas com `[PREENCHER]`
+com os dados do projeto específico antes de começar a codar.
+
+---
+
+## Princípios de Produto (sempre aplicar)
+
+| Código | Princípio | Regra prática |
+|--------|-----------|---------------|
+| P-001 | **Linguagem do domínio** | UI fala o idioma do usuário — nunca "entidade", "registro", "submeter", "payload" |
+| P-002 | **Mobile-first real** | Tela primária = celular em contexto real. Web = versão adaptada para escritório |
+| P-003 | **Defaults inteligentes / auto-save** | Usuário não clica "Salvar" durante rascunho. Uma decisão no fim: "Concluir" ou "Descartar" |
+| P-004 | **Filtragem proativa** | Mostrar só itens elegíveis para a ação — nunca mostrar tudo e alertar depois |
+| P-005 | **Validação no servidor** | Cliente é cosmético. Toda regra de negócio re-validada no backend com Zod |
+| P-006 | **Estado na URL** | Filtros, seleção, aba ativa e etapa de wizard em query params. F5 mantém estado |
+| P-007 | **Soft delete e auditoria** | Nada é apagado. `deleted_at timestamp` em toda tabela de domínio. Eventos críticos em `audit_logs` |
+
+---
+
+## Contexto do Projeto
+
+```
+Nome: [PREENCHER]
+Objetivo: [PREENCHER — 3-5 linhas: o que resolve, para quem, diferencial]
+Personas:
+  - A-001 [PREENCHER — quem usa, contexto, fluência digital]
+  - A-002 [PREENCHER]
+  - A-003 [PREENCHER — persona crítica, quem usa mais em condições adversas]
+MVP: [PREENCHER — módulos, escopo single/multi-tenant]
+```
+
+> **Pendências críticas:** ao encontrar uma decisão que bloqueia implementação, registre aqui e pergunte ao usuário antes de assumir um default.
+
+---
+
+## Stack do Projeto
+
+| Categoria | Tecnologia |
+|-----------|------------|
+| Framework | Next.js (App Router) |
+| UI | React 19, Tailwind CSS, shadcn/ui |
+| Linguagem | TypeScript (obrigatório) |
+| Auth | Clerk |
+| Banco | Supabase (PostgreSQL) |
+| Validação | Zod |
+| Formulários | React Hook Form + Zod |
+| Data Fetching | React Query (@tanstack/react-query) |
+| Data/Hora | dayjs |
+| Notificações | Sonner |
+| Ícones | @tabler/icons-react ou lucide-react |
+| Mascaras | react-number-format |
+
+---
+
+## Glossário do Domínio
+
+> Crítico: toda label, mensagem, botão e erro usa estes termos — nunca termos técnicos de software.
+
+```
+[PREENCHER — ex:]
+  extração → busca de leads
+  workspace → empresa / conta
+  crédito → crédito de extração
+
+Termos PROIBIDOS na UI (genéricos):
+  "registro", "entidade", "submeter", "validação", "transação", "objeto",
+  "instância", "tenant", "request", "payload", "null", "undefined", "erro 500"
+```
+
+---
+
+## Padrões Arquiteturais
+
+Mapeie cada módulo a um padrão antes de codar.
+
+### P0 — Ciclo de Vida com Rascunho
+Para fluxos onde o usuário monta dados em etapas e decide no fim.
+
+**Estados:** `rascunho` → `confirmado` → `estornado` | `descartado`
+
+**Auto-save (P-003):** rascunho persiste a cada alteração (debounce 300ms). Sem botão "Salvar". Decisão única: **Concluir** ou **Descartar**.
+
+**Filtragem proativa (P0.5):** tela de seleção só mostra itens elegíveis. Não confiar em validação depois.
+
+Enum Supabase:
+```sql
+CREATE TYPE status_workflow AS ENUM ('rascunho', 'confirmado', 'descartado', 'estornado');
+```
+
+### P1 — Operações com Cascatas
+Confirmação dispara cascatas em outros módulos. Toda cascata na MESMA transação (RPC Supabase). Falha em qualquer cascata = rollback completo.
+
+### P2 — Lançamentos com Estado Calculado
+NÃO armazenar estado — calcular em runtime a partir de datas/saldos. Movimentações são append-only (nunca update, apenas insert).
+
+### P3 — Telas Analíticas (Dashboards)
+Read-only. Cache de 5-15 min para KPIs pesados, ≤1 min para KPIs operacionais. Mobile-first prioriza KPIs operacionais acima do fold.
+
+---
+
+## Estrutura de Pastas
+
+```
+src/
+├── app/
+│   ├── (auth)/                    # rotas públicas (login, signup)
+│   ├── (app)/
+│   │   ├── dashboard/             # P3 — analítico
+│   │   ├── [modulo]/
+│   │   │   ├── page.tsx
+│   │   │   └── [id]/page.tsx
+│   │   └── configuracoes/
+│   └── api/
+│       ├── [modulo]/
+│       │   └── route.ts           # validação Zod + lógica de negócio
+│       └── webhooks/              # sempre verificar assinatura antes de processar
+├── components/
+│   ├── ui/                        # shadcn/ui base (não editar)
+│   └── [modulo]/                  # componentes de domínio reutilizáveis
+├── features/
+│   └── [modulo]/
+│       ├── components/            # componentes específicos do módulo
+│       ├── services/              # lógica de negócio (chamadas Supabase)
+│       └── hooks/                 # React Query hooks do módulo
+├── hooks/
+│   ├── queries/                   # use-[entidade].ts
+│   ├── mutations/                 # use-[acao].ts
+│   └── use-url-state.ts           # estado em URL (P-006)
+├── lib/
+│   ├── supabase/
+│   │   ├── client.ts              # client browser
+│   │   └── server.ts              # client server (service role — apenas server-side)
+│   ├── api/
+│   │   ├── response.ts            # ok() / fail() helpers
+│   │   └── handle-route-error.ts  # mensagens seguras (não vazar detalhes internos)
+│   ├── security/
+│   │   └── rate-limit.ts          # enforceRateLimit helper
+│   └── format/                    # formatCurrency, formatDate, etc.
+└── types/                         # interfaces e tipos compartilhados
+```
+
+---
+
+## Padrões de API Routes (Supabase + Zod)
+
+Toda rota de API que recebe input de usuário:
+```ts
+// src/app/api/[modulo]/route.ts
+import { auth } from "@clerk/nextjs/server"
+import { z } from "zod"
+import { handleRouteError } from "@/lib/api/handle-route-error"
+import { ok, fail } from "@/lib/api/response"
+import { enforceRateLimit } from "@/lib/security/rate-limit"
+
+const schema = z.object({
+  workspaceId: z.string().uuid(),
+  campo: z.string().min(1).max(500),
+})
+
+export async function POST(request: Request) {
+  const { userId } = await auth()
+  if (!userId) return fail("Não autenticado", 401)
+
+  await enforceRateLimit({ key: `modulo:${userId}`, limit: 10, windowSeconds: 60 })
+
+  const body = await request.json()
+  const parsed = schema.safeParse(body)
+  if (!parsed.success) return fail("Dados inválidos", 400)
+
+  // lógica de negócio aqui — revalidar regras de negócio no servidor (P-005)
+}
+```
+
+**Regras de API routes:**
+- SEMPRE valide com Zod (`.safeParse()` ou `.parse()`)
+- SEMPRE filtre por `workspace_id` nas queries Supabase
+- NUNCA confie em cálculos do cliente — recalcule no server
+- NUNCA vaze detalhes internos em mensagens de erro
+- Webhooks SEMPRE verificam assinatura antes de processar o body
+
+---
+
+## Schemas Supabase (padrões)
+
+Toda tabela de domínio:
+```sql
+CREATE TABLE [modulo] (
+  id uuid PRIMARY KEY DEFAULT gen_random_uuid(),
+  workspace_id uuid NOT NULL REFERENCES workspaces(id),
+  -- campos do domínio
+  deleted_at timestamp,          -- soft delete (P-007)
+  created_at timestamp NOT NULL DEFAULT now(),
+  updated_at timestamp NOT NULL DEFAULT now()
+);
+
+-- RLS obrigatório
+ALTER TABLE [modulo] ENABLE ROW LEVEL SECURITY;
+CREATE POLICY "workspace_isolation" ON [modulo]
+  USING (workspace_id = (SELECT workspace_id FROM workspace_members WHERE user_id = auth.uid()));
+```
+
+**Regras de dados:**
+- Valores monetários SEMPRE em centavos (integer). Display com `formatCurrency()`
+- Unidades físicas SEMPRE na menor unidade (integer) no banco
+- Datas como `timestamp` (UTC). Display com dayjs no locale do usuário
+
+---
+
+## Formulários (React Hook Form + Zod)
+
+```tsx
+"use client"
+import { useForm } from "react-hook-form"
+import { zodResolver } from "@hookform/resolvers/zod"
+import { z } from "zod"
+
+const schema = z.object({
+  campo: z.string().min(1, "Preencha o campo"),
+})
+
+type FormData = z.infer<typeof schema>
+
+export function MeuForm() {
+  const form = useForm<FormData>({ resolver: zodResolver(schema) })
+
+  async function onSubmit(data: FormData) {
+    const res = await fetch("/api/meu-modulo", {
+      method: "POST",
+      body: JSON.stringify(data),
+    })
+    // tratar resposta
+  }
+
+  return (
+    <form onSubmit={form.handleSubmit(onSubmit)}>
+      {/* shadcn/ui Form components */}
+    </form>
+  )
+}
+```
+
+---
+
+## Estado na URL (P-006)
+
+```ts
+// Filtros, abas, paginação sempre em query params
+// F5 mantém estado, link é compartilhável
+
+// Exemplos de hooks canônicos:
+useUrlState<"ativo" | "inativo">("status", "ativo")
+useUrlListState("categoria")        // ?categoria=A,B
+useUrlDateRange("criado")          // ?criadoDe=...&criadoAte=...
+
+// Wizard multi-etapa: ?etapa=1
+// Só persistir etapas navegáveis, não estados transientes (loading, sucesso)
+```
+
+---
+
+## Segurança (embutida por padrão)
+
+Ver skill `web-security` para checklist completa. Resumo:
+- Validação Zod em TODOS os endpoints que recebem input
+- `enforceRateLimit` em endpoints de escrita, cobrança, operações caras
+- Comparação de tokens/secrets com `crypto.timingSafeEqual` (nunca `===`)
+- Soft delete via `deleted_at` em toda tabela de domínio
+- Logs de auditoria append-only para eventos críticos
+- `.env*` nunca commitado; secrets via variáveis de ambiente da plataforma
+- `SUPABASE_SERVICE_ROLE_KEY` apenas server-side
+
+---
+
+## Regras de Código
+
+- SEMPRE TypeScript. Sem `any` explícito.
+- Nomes descritivos: `isLoading`, `hasError`, `handleConfirmarAcao`
+- **kebab-case** para arquivos e pastas: `confirmar-acao.ts`
+- SOLID e Clean Code; funções < 50 linhas; arquivos < 800 linhas
+- DRY: componentes reutilizáveis para padrões repetidos
+- NUNCA escreva comentários no código
+- NUNCA rode `npm run dev` para testar TypeScript — use `npx tsc --noEmit`
+- Imutabilidade: SEMPRE crie novos objetos, NUNCA mutate (spread, map, filter)
+- Sem `console.log` em produção
+
+---
+
+## Checklist de Início de Projeto
+
+- [ ] Glossário de domínio preenchido (termos do usuário, termos proibidos)
+- [ ] Personas definidas (especialmente A-003, quem usa em condições adversas)
+- [ ] Cada módulo mapeado a um padrão P0/P1/P2/P3
+- [ ] RLS configurado nas tabelas Supabase
+- [ ] `.env.example` criado (sem valores reais) e `.env*` no `.gitignore`
+- [ ] Headers de segurança em `next.config.ts`
+- [ ] `enforceRateLimit` nos endpoints de escrita/cobrança
+- [ ] Auto-save implementado para módulos P0 (debounce 300ms)
+- [ ] Estado em URL para filtros/abas/etapas (P-006)
+- [ ] `deleted_at` em tabelas de domínio (P-007)

package/src/skills-lib/launch-strategy/SKILL.md

@@ -0,0 +1,353 @@
+---
+name: launch-strategy
+description: "When the user wants to plan a product launch, feature announcement, or release strategy. Also use when the user mentions 'launch,' 'Product Hunt,' 'feature release,' 'announcement,' 'go-to-market,' 'beta launch,' 'early access,' 'waitlist,' 'product update,' 'how do I launch this,' 'launch checklist,' 'GTM plan,' or 'we're about to ship.' Use this whenever someone is preparing to release something publicly. For ongoing marketing after launch, see marketing-ideas."
+metadata:
+  version: 1.1.0
+---
+
+# Launch Strategy
+
+You are an expert in SaaS product launches and feature announcements. Your goal is to help users plan launches that build momentum, capture attention, and convert interest into users.
+
+## Before Starting
+
+**Check for product marketing context first:**
+If `.agents/product-marketing-context.md` exists (or `.claude/product-marketing-context.md` in older setups), read it before asking questions. Use that context and only ask for information not already covered or specific to this task.
+
+---
+
+## Core Philosophy
+
+The best companies don't just launch once—they launch again and again. Every new feature, improvement, and update is an opportunity to capture attention and engage your audience.
+
+A strong launch isn't about a single moment. It's about:
+- Getting your product into users' hands early
+- Learning from real feedback
+- Making a splash at every stage
+- Building momentum that compounds over time
+
+---
+
+## The ORB Framework
+
+Structure your launch marketing across three channel types. Everything should ultimately lead back to owned channels.
+
+### Owned Channels
+You own the channel (though not the audience). Direct access without algorithms or platform rules.
+
+**Examples:**
+- Email list
+- Blog
+- Podcast
+- Branded community (Slack, Discord)
+- Website/product
+
+**Why they matter:**
+- Get more effective over time
+- No algorithm changes or pay-to-play
+- Direct relationship with audience
+- Compound value from content
+
+**Start with 1-2 based on audience:**
+- Industry lacks quality content → Start a blog
+- People want direct updates → Focus on email
+- Engagement matters → Build a community
+
+**Example - Superhuman:**
+Built demand through an invite-only waitlist and one-on-one onboarding sessions. Every new user got a 30-minute live demo. This created exclusivity, FOMO, and word-of-mouth—all through owned relationships. Years later, their original onboarding materials still drive engagement.
+
+### Rented Channels
+Platforms that provide visibility but you don't control. Algorithms shift, rules change, pay-to-play increases.
+
+**Examples:**
+- Social media (Twitter/X, LinkedIn, Instagram)
+- App stores and marketplaces
+- YouTube
+- Reddit
+
+**How to use correctly:**
+- Pick 1-2 platforms where your audience is active
+- Use them to drive traffic to owned channels
+- Don't rely on them as your only strategy
+
+**Example - Notion:**
+Hacked virality through Twitter, YouTube, and Reddit where productivity enthusiasts were active. Encouraged community to share templates and workflows. But they funneled all visibility into owned assets—every viral post led to signups, then targeted email onboarding.
+
+**Platform-specific tactics:**
+- Twitter/X: Threads that spark conversation → link to newsletter
+- LinkedIn: High-value posts → lead to gated content or email signup
+- Marketplaces (Shopify, Slack): Optimize listing → drive to site for more
+
+Rented channels give speed, not stability. Capture momentum by bringing users into your owned ecosystem.
+
+### Borrowed Channels
+Tap into someone else's audience to shortcut the hardest part—getting noticed.
+
+**Examples:**
+- Guest content (blog posts, podcast interviews, newsletter features)
+- Collaborations (webinars, co-marketing, social takeovers)
+- Speaking engagements (conferences, panels, virtual summits)
+- Influencer partnerships
+
+**Be proactive, not passive:**
+1. List industry leaders your audience follows
+2. Pitch win-win collaborations
+3. Use tools like SparkToro or Listen Notes to find audience overlap
+4. Set up affiliate/referral incentives
+
+**Example - TRMNL:**
+Sent a free e-ink display to YouTuber Snazzy Labs—not a paid sponsorship, just hoping he'd like it. He created an in-depth review that racked up 500K+ views and drove $500K+ in sales. They also set up an affiliate program for ongoing promotion.
+
+Borrowed channels give instant credibility, but only work if you convert borrowed attention into owned relationships.
+
+---
+
+## Five-Phase Launch Approach
+
+Launching isn't a one-day event. It's a phased process that builds momentum.
+
+### Phase 1: Internal Launch
+Gather initial feedback and iron out major issues before going public.
+
+**Actions:**
+- Recruit early users one-on-one to test for free
+- Collect feedback on usability gaps and missing features
+- Ensure prototype is functional enough to demo (doesn't need to be production-ready)
+
+**Goal:** Validate core functionality with friendly users.
+
+### Phase 2: Alpha Launch
+Put the product in front of external users in a controlled way.
+
+**Actions:**
+- Create landing page with early access signup form
+- Announce the product exists
+- Invite users individually to start testing
+- MVP should be working in production (even if still evolving)
+
+**Goal:** First external validation and initial waitlist building.
+
+### Phase 3: Beta Launch
+Scale up early access while generating external buzz.
+
+**Actions:**
+- Work through early access list (some free, some paid)
+- Start marketing with teasers about problems you solve
+- Recruit friends, investors, and influencers to test and share
+
+**Consider adding:**
+- Coming soon landing page or waitlist
+- "Beta" sticker in dashboard navigation
+- Email invites to early access list
+- Early access toggle in settings for experimental features
+
+**Goal:** Build buzz and refine product with broader feedback.
+
+### Phase 4: Early Access Launch
+Shift from small-scale testing to controlled expansion.
+
+**Actions:**
+- Leak product details: screenshots, feature GIFs, demos
+- Gather quantitative usage data and qualitative feedback
+- Run user research with engaged users (incentivize with credits)
+- Optionally run product/market fit survey to refine messaging
+
+**Expansion options:**
+- Option A: Throttle invites in batches (5-10% at a time)
+- Option B: Invite all users at once under "early access" framing
+
+**Goal:** Validate at scale and prepare for full launch.
+
+### Phase 5: Full Launch
+Open the floodgates.
+
+**Actions:**
+- Open self-serve signups
+- Start charging (if not already)
+- Announce general availability across all channels
+
+**Launch touchpoints:**
+- Customer emails
+- In-app popups and product tours
+- Website banner linking to launch assets
+- "New" sticker in dashboard navigation
+- Blog post announcement
+- Social posts across platforms
+- Product Hunt, BetaList, Hacker News, etc.
+
+**Goal:** Maximum visibility and conversion to paying users.
+
+---
+
+## Product Hunt Launch Strategy
+
+Product Hunt can be powerful for reaching early adopters, but it's not magic—it requires preparation.
+
+### Pros
+- Exposure to tech-savvy early adopter audience
+- Credibility bump (especially if Product of the Day)
+- Potential PR coverage and backlinks
+
+### Cons
+- Very competitive to rank well
+- Short-lived traffic spikes
+- Requires significant pre-launch planning
+
+### How to Launch Successfully
+
+**Before launch day:**
+1. Build relationships with influential supporters, content hubs, and communities
+2. Optimize your listing: compelling tagline, polished visuals, short demo video
+3. Study successful launches to identify what worked
+4. Engage in relevant communities—provide value before pitching
+5. Prepare your team for all-day engagement
+
+**On launch day:**
+1. Treat it as an all-day event
+2. Respond to every comment in real-time
+3. Answer questions and spark discussions
+4. Encourage your existing audience to engage
+5. Direct traffic back to your site to capture signups
+
+**After launch day:**
+1. Follow up with everyone who engaged
+2. Convert Product Hunt traffic into owned relationships (email signups)
+3. Continue momentum with post-launch content
+
+### Case Studies
+
+**SavvyCal** (Scheduling tool):
+- Optimized landing page and onboarding before launch
+- Built relationships with productivity/SaaS influencers in advance
+- Responded to every comment on launch day
+- Result: #2 Product of the Month
+
+**Reform** (Form builder):
+- Studied successful launches and applied insights
+- Crafted clear tagline, polished visuals, demo video
+- Engaged in communities before launch (provided value first)
+- Treated launch as all-day engagement event
+- Directed traffic to capture signups
+- Result: #1 Product of the Day
+
+---
+
+## Post-Launch Product Marketing
+
+Your launch isn't over when the announcement goes live. Now comes adoption and retention work.
+
+### Immediate Post-Launch Actions
+
+**Educate new users:**
+Set up automated onboarding email sequence introducing key features and use cases.
+
+**Reinforce the launch:**
+Include announcement in your weekly/biweekly/monthly roundup email to catch people who missed it.
+
+**Differentiate against competitors:**
+Publish comparison pages highlighting why you're the obvious choice.
+
+**Update web pages:**
+Add dedicated sections about the new feature/product across your site.
+
+**Offer hands-on preview:**
+Create no-code interactive demo (using tools like Navattic) so visitors can explore before signing up.
+
+### Keep Momentum Going
+It's easier to build on existing momentum than start from scratch. Every touchpoint reinforces the launch.
+
+---
+
+## Ongoing Launch Strategy
+
+Don't rely on a single launch event. Regular updates and feature rollouts sustain engagement.
+
+### How to Prioritize What to Announce
+
+Use this matrix to decide how much marketing each update deserves:
+
+**Major updates** (new features, product overhauls):
+- Full campaign across multiple channels
+- Blog post, email campaign, in-app messages, social media
+- Maximize exposure
+
+**Medium updates** (new integrations, UI enhancements):
+- Targeted announcement
+- Email to relevant segments, in-app banner
+- Don't need full fanfare
+
+**Minor updates** (bug fixes, small tweaks):
+- Changelog and release notes
+- Signal that product is improving
+- Don't dominate marketing
+
+### Announcement Tactics
+
+**Space out releases:**
+Instead of shipping everything at once, stagger announcements to maintain momentum.
+
+**Reuse high-performing tactics:**
+If a previous announcement resonated, apply those insights to future updates.
+
+**Keep engaging:**
+Continue using email, social, and in-app messaging to highlight improvements.
+
+**Signal active development:**
+Even small changelog updates remind customers your product is evolving. This builds retention and word-of-mouth—customers feel confident you'll be around.
+
+---
+
+## Launch Checklist
+
+### Pre-Launch
+- [ ] Landing page with clear value proposition
+- [ ] Email capture / waitlist signup
+- [ ] Early access list built
+- [ ] Owned channels established (email, blog, community)
+- [ ] Rented channel presence (social profiles optimized)
+- [ ] Borrowed channel opportunities identified (podcasts, influencers)
+- [ ] Product Hunt listing prepared (if using)
+- [ ] Launch assets created (screenshots, demo video, GIFs)
+- [ ] Onboarding flow ready
+- [ ] Analytics/tracking in place
+
+### Launch Day
+- [ ] Announcement email to list
+- [ ] Blog post published
+- [ ] Social posts scheduled and posted
+- [ ] Product Hunt listing live (if using)
+- [ ] In-app announcement for existing users
+- [ ] Website banner/notification active
+- [ ] Team ready to engage and respond
+- [ ] Monitor for issues and feedback
+
+### Post-Launch
+- [ ] Onboarding email sequence active
+- [ ] Follow-up with engaged prospects
+- [ ] Roundup email includes announcement
+- [ ] Comparison pages published
+- [ ] Interactive demo created
+- [ ] Gather and act on feedback
+- [ ] Plan next launch moment
+
+---
+
+## Task-Specific Questions
+
+1. What are you launching? (New product, major feature, minor update)
+2. What's your current audience size and engagement?
+3. What owned channels do you have? (Email list size, blog traffic, community)
+4. What's your timeline for launch?
+5. Have you launched before? What worked/didn't work?
+6. Are you considering Product Hunt? What's your preparation status?
+
+---
+
+## Related Skills
+
+- **marketing-ideas**: For additional launch tactics (#22 Product Hunt, #23 Early Access Referrals)
+- **email-sequence**: For launch and onboarding email sequences
+- **page-cro**: For optimizing launch landing pages
+- **marketing-psychology**: For psychology behind waitlists and exclusivity
+- **programmatic-seo**: For comparison pages mentioned in post-launch
+- **sales-enablement**: For launch sales collateral and enablement materials