Ejecuta cualquier Skill en Manus
con un clic

Ejecuta cualquier Skill en Manus con un clic

$pwd:

mvp-launch

Name: Mvp Launch
Author: ooiyeefei

// Web app MVP launch checklist knowledge. Auto-triggered when conversation involves "launch readiness", "MVP checklist", "production ready", "go live", or pre-launch verification. Provides the 10-point criteria for what counts as "done" in each area. Based on "Realistic MVP Launch Checklist (from building 30+ apps)".

Ejecutar en Manus

$ git log --oneline --stat

stars:432

forks:48

updated:9 de enero de 2026, 22:14

Explorador de archivos

3 archivos

SKILL.md

readonly

name	mvp-launch
description	Web app MVP launch checklist knowledge. Auto-triggered when conversation involves "launch readiness", "MVP checklist", "production ready", "go live", or pre-launch verification. Provides the 10-point criteria for what counts as "done" in each area. Based on "Realistic MVP Launch Checklist (from building 30+ apps)".

MVP Launch Checklist

A battle-tested 10-point checklist for web app MVP launches. Based on building 30+ apps.

Philosophy: "Don't overbuild. Just make it stable, usable, and something people can trust."

The 10-Point Checklist

1. Stripe Setup (Payment Infrastructure)

What counts as DONE:

Trials configured with appropriate period
Plan switching works (upgrade/downgrade)
Failed payment handling with retry logic
Webhook endpoint registered in Stripe Dashboard
Live keys tested (not just test mode)

Required Webhook Events:

customer.subscription.trial_will_end
customer.subscription.created
customer.subscription.updated
customer.subscription.deleted
invoice.payment_succeeded
invoice.payment_failed
invoice.created
checkout.session.completed

Verification: See references/stripe-testing.md

2. Mobile-First Design

What counts as DONE:

Tested on real phones (not just browser resize)
Touch targets appropriately sized (44x44px minimum)
Forms work on mobile keyboards
No horizontal scroll on mobile

Key insight: Browser resize mode lies. Real device testing is mandatory.

Bonus (not required):

PWA manifest for installability
Offline capability for core features

3. Smooth Onboarding

What counts as DONE:

Steps kept minimal (3-5 max)
Users guided to a fast first win
Progress indicator if multi-step
Can be skipped/completed later

Anti-pattern: Don't require 10 fields before users see value.

4. AI & Automation Stability

What counts as DONE:

API errors handled gracefully
Retry logic with exponential backoff
Edge cases don't crash the app
Timeouts configured appropriately
Fallback behavior when AI fails

Good defaults:

3 retry attempts
30-60s timeout for complex operations
User-friendly error messages

5. Critical Emails

What counts as DONE:

Welcome email (immediate after signup)
Trial-ending email (before trial expires)
Failed payment email (when charge fails)
Password reset (if not using external auth)

Nice to have (don't overbuild):

Support acknowledgment email
Usage milestone emails

6. Error Logging

What counts as DONE:

Error tracking service configured (Sentry, Bugsnag, etc.)
PII scrubbed from logs
Critical errors trigger alerts
Enough context to debug issues

Goal: Catch bugs before users notice them.

7. User Feedback Loop

What counts as DONE:

Simple form or tool to collect feedback
Screenshots/context capture (optional but helpful)
Feedback reaches the team (email, Slack, GitHub Issues)

Examples: Typeform, in-app widget, email link, GitHub Issues integration.

8. Authentication & Roles

What counts as DONE:

Secure page protection (no unauthorized access)
Password reset works (or external auth handles it)
Basic roles defined (admin vs user minimum)
Session management (logout, expiry)

If using external auth (Clerk, Auth0): Most of this is handled for you.

9. Custom Domain with SSL

What counts as DONE:

Own domain configured (no .vercel.app, .replit.app)
HTTPS enabled (auto or manual SSL)
DNS properly configured

Why it matters: Trust. Users won't pay for myapp.replit.app.

10. Real Database & Backups

What counts as DONE:

Production database (not dev/local DB)
Automated backups configured
Point-in-time recovery possible

Good choices: Supabase, Neon, PlanetScale, Convex, AWS RDS.

Anti-pattern: Replit DB, SQLite in production, no backups.

Scoring

Score	Meaning
10/10	Fully implemented, production-ready
7-9/10	Mostly complete, minor gaps
4-6/10	Partial implementation, needs work
1-3/10	Minimal/broken implementation
0/10	Not implemented

Overall (sum of 10 areas):

85-100: Launch Ready
70-84: Nearly Ready
50-69: Needs Work
<50: Not Ready

References

references/search-patterns.md - Grep patterns for discovery
references/stripe-testing.md - Stripe CLI verification commands

related-skills.json

mismo repositorio

htmldrop.md

from "ooiyeefei/ccc"

This skill should be used when the user asks to "share this HTML", "publish HTML", "get a link for this file", "share this report", "make this shareable", "upload this HTML", or wants to publish any HTML artifact for others to view. ALSO use it for collaborative review on an HTML doc/spec/report — triggers include "get feedback on this", "let reviewers comment", "collect feedback", "share for review", "let people annotate this", "synthesize the feedback", "converge the feedback", "what did reviewers say", "incorporate the comments", or "improve this from the feedback". Wraps Surge.sh for zero-cost hosting with guided privacy options, plus an embedded annotation + AI converge workflow.

2026-05-27432

agentic-system-design.md

from "ooiyeefei/ccc"

Prescriptive Q&A workflow for designing agentic pipelines, multi-model councils, sub-agent hierarchies, and tool-loop hardening for any domain. Use when the user asks to "design an agent", "design a multi-agent system", "should I use a council/debate", "build a [domain] review agent" (HAZOP, finance, tutorial, marketing, compliance, accounting), "real agency vs workflow", "how to add sub-agents", "AI for [domain] review", or names patterns like "orchestrator-worker", "evaluator-optimizer", "Magentic", "ReAct", "plan-and-execute", "handoffs". Walks the user through 12 stages one question at a time and emits a buildable design doc with citations. Do NOT use for general coding questions, single-shot prompt tuning, or bare "use Claude to do X" requests with no agency requirement.

2026-05-08432

self-improving-systems.md

from "ooiyeefei/ccc"

Decide whether your agent actually needs persistent memory, feedback loops, or closed-loop learning, then design the smallest thing that pays for itself. Use when the user says "add memory", "give my agent context management", "make my agent learn", "self-improving / closed-loop", "Reflexion / mem0 / Letta / MemGPT", "AriGraph", "agent memory architecture", "long-term memory for chatbot", "why does my agent keep forgetting / making the same mistake", "fine-tune from agent traces", or asks for a memory schema / experience store / reward model. Filters ruthlessly — most teams want a state cache, not memory + learning. Default position is scratchpad-only with a stateless agent shipped first.

2026-05-08432

rethink-surveys.md

from "ooiyeefei/ccc"

Design, critique, or scaffold surveys grounded in Caroline Jarrett, Dillman, and Tourangeau methods. Use when designing a new survey, critiquing an existing one, scoring or clustering responses, or turning questions into an app. Triggers on "survey", "questionnaire", "user research", "customer discovery", "intent capture", "interview script", "lint my survey", "score responses", or "how to ask better questions". When the bundled MCP server is connected, prefer its deterministic tools (`critique_survey`, `get_template`, `design_survey_session`, `score_response`, `cluster_responses`) over manual reasoning. Captures real past behavior over hypotheticals, supports text/voice/AI-interviewer modalities, and includes templates for event organizers, startup founders, and gig-economy workers.

2026-05-05432

landing-page-gtm.md

from "ooiyeefei/ccc"

Build and update high-converting SaaS landing pages with GTM-aware marketing copy, competitive positioning, and sales psychology. Use when creating new landing pages, rewriting feature cards, updating marketing copy, launching product pages, or transforming technical features into customer-facing sales language. Triggers on "build landing page", "update feature cards", "rewrite marketing copy", "create product page", "launch page", "GTM", "sales copy", "competitive positioning", or when converting product features into conversion-focused web pages.

2026-03-17432

excalidraw.md

from "ooiyeefei/ccc"

Generate architecture diagrams as .excalidraw files from codebase analysis, with optional PNG/SVG export. Use when the user asks to create architecture diagrams, system diagrams, visualize codebase structure, generate excalidraw files, export excalidraw diagrams to PNG or SVG, or convert .excalidraw files to image formats.

2026-02-15432

package.json

"author": "ooiyeefei"

"repository": "ooiyeefei/ccc"

Abrir repositorio de GitHub Ver repositorios del creador

$ install --global

$ download --local

Ejecutar en Manus

$ useful --forSOC

Gerentes generales y de operacionesOcupaciones de dirección y gestión11-1021L4

name	mvp-launch
description	Web app MVP launch checklist knowledge. Auto-triggered when conversation involves "launch readiness", "MVP checklist", "production ready", "go live", or pre-launch verification. Provides the 10-point criteria for what counts as "done" in each area. Based on "Realistic MVP Launch Checklist (from building 30+ apps)".

MVP Launch Checklist

A battle-tested 10-point checklist for web app MVP launches. Based on building 30+ apps.

Philosophy: "Don't overbuild. Just make it stable, usable, and something people can trust."

The 10-Point Checklist

1. Stripe Setup (Payment Infrastructure)

What counts as DONE:

Trials configured with appropriate period
Plan switching works (upgrade/downgrade)
Failed payment handling with retry logic
Webhook endpoint registered in Stripe Dashboard
Live keys tested (not just test mode)

Required Webhook Events:

customer.subscription.trial_will_end
customer.subscription.created
customer.subscription.updated
customer.subscription.deleted
invoice.payment_succeeded
invoice.payment_failed
invoice.created
checkout.session.completed

Verification: See references/stripe-testing.md

2. Mobile-First Design

What counts as DONE:

Tested on real phones (not just browser resize)
Touch targets appropriately sized (44x44px minimum)
Forms work on mobile keyboards
No horizontal scroll on mobile

Key insight: Browser resize mode lies. Real device testing is mandatory.

Bonus (not required):

PWA manifest for installability
Offline capability for core features

3. Smooth Onboarding

What counts as DONE:

Steps kept minimal (3-5 max)
Users guided to a fast first win
Progress indicator if multi-step
Can be skipped/completed later

Anti-pattern: Don't require 10 fields before users see value.

4. AI & Automation Stability

What counts as DONE:

API errors handled gracefully
Retry logic with exponential backoff
Edge cases don't crash the app
Timeouts configured appropriately
Fallback behavior when AI fails

Good defaults:

3 retry attempts
30-60s timeout for complex operations
User-friendly error messages

5. Critical Emails

What counts as DONE:

Welcome email (immediate after signup)
Trial-ending email (before trial expires)
Failed payment email (when charge fails)
Password reset (if not using external auth)

Nice to have (don't overbuild):

Support acknowledgment email
Usage milestone emails

6. Error Logging

What counts as DONE:

Error tracking service configured (Sentry, Bugsnag, etc.)
PII scrubbed from logs
Critical errors trigger alerts
Enough context to debug issues

Goal: Catch bugs before users notice them.

7. User Feedback Loop

What counts as DONE:

Simple form or tool to collect feedback
Screenshots/context capture (optional but helpful)
Feedback reaches the team (email, Slack, GitHub Issues)

Examples: Typeform, in-app widget, email link, GitHub Issues integration.

8. Authentication & Roles

What counts as DONE:

Secure page protection (no unauthorized access)
Password reset works (or external auth handles it)
Basic roles defined (admin vs user minimum)
Session management (logout, expiry)

If using external auth (Clerk, Auth0): Most of this is handled for you.

9. Custom Domain with SSL

What counts as DONE:

Own domain configured (no .vercel.app, .replit.app)
HTTPS enabled (auto or manual SSL)
DNS properly configured

Why it matters: Trust. Users won't pay for myapp.replit.app.

10. Real Database & Backups

What counts as DONE:

Production database (not dev/local DB)
Automated backups configured
Point-in-time recovery possible

Good choices: Supabase, Neon, PlanetScale, Convex, AWS RDS.

Anti-pattern: Replit DB, SQLite in production, no backups.

Scoring

Score	Meaning
10/10	Fully implemented, production-ready
7-9/10	Mostly complete, minor gaps
4-6/10	Partial implementation, needs work
1-3/10	Minimal/broken implementation
0/10	Not implemented

Overall (sum of 10 areas):

85-100: Launch Ready
70-84: Nearly Ready
50-69: Needs Work
<50: Not Ready

References

references/search-patterns.md - Grep patterns for discovery
references/stripe-testing.md - Stripe CLI verification commands

mvp-launch

MVP Launch Checklist

The 10-Point Checklist

1. Stripe Setup (Payment Infrastructure)

2. Mobile-First Design

3. Smooth Onboarding

4. AI & Automation Stability

5. Critical Emails

6. Error Logging

7. User Feedback Loop

8. Authentication & Roles

9. Custom Domain with SSL

10. Real Database & Backups

Scoring

References

Más de este repositorio

Más de este repositorio

MVP Launch Checklist

The 10-Point Checklist

1. Stripe Setup (Payment Infrastructure)

2. Mobile-First Design

3. Smooth Onboarding

4. AI & Automation Stability

5. Critical Emails

6. Error Logging

7. User Feedback Loop

8. Authentication & Roles

9. Custom Domain with SSL

10. Real Database & Backups

Scoring

References