菜单
Playbook de lanzamiento semana a semana para productos o servicios. Usar cuando: "plan de lanzamiento", "go-to-market", "GTM", "voy a lanzar", "estrategia de lanzamiento", "pre-launch checklist", "cómo lanzo mi producto", "launch campaign". Genera LAUNCH-PLAYBOOK.md.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Vercel a profundidad — CLI avanzado, CI/CD, env vars y patrones Next.js App Router (Next 16). Reemplaza al plugin oficial de Vercel (43 skills) condensado a lo esencial. Complementa a `deployment` (que cubre el deploy básico). Usar cuando: "vercel link", "monorepo vercel", "vercel build --prebuilt", "vercel promote", "vercel rollback", "CI/CD vercel", "GitHub Actions vercel", "VERCEL_TOKEN", "vercel env pull", "OIDC token", "VERCEL_OIDC_TOKEN", "project.json vs repo.json", "App Router", "server component async", "cookies() headers() params async", "middleware proxy.ts", "revalidateTag", "next/router next/navigation", "getServerSideProps migrar", "next 16 breaking changes". Do NOT use for: deploy básico a Vercel (usar `deployment`), Railway, Express puro, ni AI SDK/Workflow/shadcn del plugin (esos quedaron fuera del recorte — reactivar el plugin oficial si se necesitan).
Autenticación en Next.js: NextAuth v5 (Auth.js), JWT, sesiones, middleware y RBAC. Stack: Next.js App Router + NextAuth v5 / Supabase Auth / JWT custom. Usar cuando: "NextAuth", "Auth.js", "login", "sesión", "JWT", "middleware de auth", "proteger rutas", "RBAC", "roles y permisos", "OAuth", "credentials provider", "useSession", "getServerSession", "auth middleware", "redirect si no autenticado".
Colas de trabajo asíncronas con BullMQ + Redis en Node.js/Express. Reintentos, concurrencia, delays anti-ban, workers y monitoreo. Usar cuando: "cola de mensajes", "job queue", "BullMQ", "tareas en background", "envío masivo", "anti-ban WhatsApp", "rate limiting mensajes", "worker", "reintentar tarea fallida", "procesar en segundo plano", "Bull", "Redis queue", "scheduled jobs", "delayed jobs".
Agrega un chatbot, asistente IA o chat widget a un sitio web o app. Usar cuando: "chatbot", "chat widget", "asistente virtual", "chat flotante", "bot de ventas", "bot de soporte", "FAQ bot", "useChat", "streaming chat", "Vercel AI SDK", "asistente inteligente", "chat con IA", "embedded chat".
Integra un CMS headless a Next.js para que el cliente edite contenido sin código. Stack: Sanity / Contentful / Strapi. Usar cuando: "CMS", "headless CMS", "Sanity", "sitio administrable", "blog con CMS", "el cliente quiere editar", "GROQ", "live preview", "contenido dinámico", "Strapi".
Dashboards y visualización de datos en React/Next.js. Stack: Recharts / Chart.js. Usar cuando: "dashboard", "gráfica", "chart", "KPIs", "métricas", "stat cards", "bar chart", "pie chart", "line chart", "heatmap", "panel de analytics", "reporting dashboard", "admin panel con datos", "visualizar datos".
| name | market-launch |
| description | Playbook de lanzamiento semana a semana para productos o servicios. Usar cuando: "plan de lanzamiento", "go-to-market", "GTM", "voy a lanzar", "estrategia de lanzamiento", "pre-launch checklist", "cómo lanzo mi producto", "launch campaign". Genera LAUNCH-PLAYBOOK.md. |
Genera un playbook de lanzamiento táctico y personalizado: timeline semana a semana, templates de email listos para copiar, posts por canal, coordinación de partners, métricas en tiempo real y plan post-lanzamiento. Output es copy listo para usar, no frameworks vacíos.
Si el usuario ya corrió /market audit o /market brand, pull findings para informar positioning y mensajes.
Formato de salida: ver references/output-template.md.
Ask only what's missing -- infer from context:
| Launch Type | Best For | Primary Channel | Timeline |
|---|---|---|---|
| Product Hunt | SaaS, dev tools, consumer apps | Product Hunt + X | 4-6 weeks |
| Email List | Course, info product, SaaS | Email sequences | 6-8 weeks |
| Social-First | Consumer product, personal brand | Twitter/X, LinkedIn, IG | 4-6 weeks |
| Paid Ads | E-commerce, proven product | Meta / Google Ads | 2-4 weeks |
| Community | Niche tools, developer products | Reddit, Discord, Slack | 6-8 weeks |
| Partner | B2B, enterprise, marketplace | Partner channels | 8-12 weeks |
| Hybrid | High-stakes launch | Multi-channel coordinated | 8-12 weeks |
Full task lists per phase: see references/launch-frameworks.md.
Phases:
Compressed timeline (<8 weeks): Combine phases, prioritize email + community, cut audience-building to 1 week.
Minimum viable launch (bootstrapped):
Generate complete, product-specific email copy -- not placeholders. Full templates: references/launch-frameworks.md.
Pre-launch (Weeks 5-6):
Launch (Week 7):
Platform-specific posts for launch week. Full templates: references/social-templates.md.
Per platform:
Provide partners: free product access, swipe copy (email/social/blog), branded graphics, unique referral link, commission structure, launch-day schedule.
Timeline: initial contact Week 3 -> confirmation + swipe copy Week 5 -> launch-day coordination Week 7.
Track in real-time during launch week. Full benchmarks: references/metrics-framework.md.
Key live metrics: website traffic by source, landing/checkout conversion rate, email open rates, revenue + AOV vs target, CPA (if paid).
