create-baton 1.0.0

package/templates/skills/core/launch-prep/SKILL.md

@@ -0,0 +1,232 @@
+---
+name: launch-prep
+description: >-
+  Launch preparation and shipping guidance. Covers pre-launch questions,
+  launch options (silent/soft/public), launch checklists, and post-launch
+  protocol. Use at session 8+ when approaching launch, when the user
+  mentions launching, shipping, or getting real users.
+---
+
+# Launch Prep Skill
+
+> Building is easy. Launching is hard.
+> Start thinking about launch from Session 8, not Session 20.
+
+---
+
+## When to Load This Skill
+
+- Session 8+ (after MVP features work)
+- When user mentions "launch" or "users"
+- When backlog keeps growing without shipping
+
+---
+
+## The Launch Mindset
+
+Most projects fail not because they're bad, but because they never launch.
+
+**The formula:**
+```
+Launched + Imperfect > Perfect + Never Shipped
+```
+
+---
+
+## Pre-Launch Questions (Session 8-10)
+
+Ask the user:
+
+### 1. Who is the first user?
+
+> "Who will use this first?
+> - Yourself only?
+> - Friends/family?
+> - A specific person you know?
+> - Strangers on the internet?"
+
+**Why it matters:** First user determines launch complexity.
+
+### 2. How will they find it?
+
+> "How will first users discover this?
+> - You'll send them a link directly
+> - Post on social media
+> - Product Hunt / Hacker News
+> - SEO / organic search
+> - Other?"
+
+**Why it matters:** Distribution determines what needs to be ready.
+
+### 3. What's the minimum to launch?
+
+> "If you had to launch tomorrow, what's truly missing?
+> List only BLOCKERS, not nice-to-haves."
+
+**Why it matters:** Separates real blockers from perfectionism.
+
+---
+
+## Launch Options
+
+### Option A: Silent Launch
+
+Just deploy. Share link with a few people. No announcement.
+
+**Good for:**
+- Testing with real users
+- Low pressure
+- Finding bugs before public launch
+
+**Requires:**
+- [ ] Core feature works
+- [ ] No obvious crashes
+- [ ] Basic error handling
+- Nothing else
+
+### Option B: Soft Launch
+
+Deploy + announce to a small audience (Twitter, friends, community).
+
+**Good for:**
+- Getting initial feedback
+- Building early users
+- Testing positioning
+
+**Requires:**
+- [ ] Everything from Silent Launch
+- [ ] Landing page / clear value prop
+- [ ] Way to collect feedback
+- [ ] Basic analytics
+
+### Option C: Public Launch
+
+Product Hunt, Hacker News, press outreach.
+
+**Good for:**
+- Maximum initial exposure
+- Building credibility
+- "Launch moment" marketing
+
+**Requires:**
+- [ ] Everything from Soft Launch
+- [ ] Polished UI/UX
+- [ ] Ready for traffic spike
+- [ ] Prepared for feedback/criticism
+
+---
+
+## Launch Checklist
+
+### Must Have (Blockers)
+
+- [ ] Core feature works reliably
+- [ ] Users can sign up / log in
+- [ ] No data loss bugs
+- [ ] Basic error handling (doesn't crash)
+- [ ] Works on mobile (if web app)
+- [ ] HTTPS enabled
+
+### Should Have (Important)
+
+- [ ] Clear value proposition on landing page
+- [ ] Way to contact you (email, chat)
+- [ ] Basic analytics installed
+- [ ] Error monitoring (Sentry)
+- [ ] Feedback collection method
+
+### Nice to Have (Not Launch Blockers)
+
+- [ ] Perfect UI polish
+- [ ] All edge cases handled
+- [ ] Comprehensive onboarding
+- [ ] Advanced features
+- [ ] Performance optimization
+
+**Don't let "nice to have" delay launch.**
+
+---
+
+## Launch Week Protocol
+
+### 3 Days Before
+
+- [ ] Final smoke test
+- [ ] Check production environment
+- [ ] Prepare announcement (post, tweet, email)
+- [ ] Tell 2-3 friends to be ready to try it
+
+### Launch Day
+
+- [ ] Deploy final version
+- [ ] Verify everything works
+- [ ] Post announcement
+- [ ] Monitor for errors (watch Sentry/logs)
+- [ ] Respond to all feedback quickly
+
+### Week After
+
+- [ ] Collect feedback themes
+- [ ] Fix critical bugs immediately
+- [ ] Note feature requests (don't build yet)
+- [ ] Thank early users personally
+
+---
+
+## Post-Launch: What's Next?
+
+After launch, priorities change:
+
+```
+Before launch: Build features
+After launch:  Fix what users report + observe usage
+```
+
+### First 2 Weeks After Launch
+
+1. **Fix bugs** reported by real users
+2. **Observe** how people actually use it
+3. **Talk** to users directly
+4. **Don't** add new features yet
+
+### Then
+
+Use real feedback to decide what to build next.
+Not your backlog. Not your ideas. What users actually need.
+
+---
+
+## When User Keeps Delaying
+
+If user repeatedly says "one more feature before launch":
+
+> "I notice we've delayed launch a few times. Can I share an observation?
+>
+> Most successful products launch earlier than feels comfortable. The feedback from ONE real user is worth more than 10 features built in isolation.
+>
+> What would it take to do a silent launch this week, just to a few people?"
+
+---
+
+## Marketing Basics (If Needed)
+
+### Minimum Viable Marketing
+
+1. **One sentence:** What does it do? For whom?
+2. **Screenshot:** What does it look like?
+3. **Link:** Where can people try it?
+
+That's enough to launch.
+
+### If User Wants More
+
+Point to resources:
+- Product Hunt launch guide
+- Marketing skills (if available)
+- Launch strategy templates
+
+But don't let marketing planning delay the actual launch.
+
+---
+
+*Last updated: Baton Protocol v3.1*

package/templates/skills/core/milestones/SKILL.md

@@ -0,0 +1,167 @@
+---
+name: milestones
+description: >-
+  Project milestone tracking and scope creep detection. Defines standard
+  milestone phases (Foundation, MVP, Polish, Launch, Iterate) with session
+  targets and review checkpoints. Use when planning project phases,
+  detecting scope creep, or when milestones slip.
+---
+
+# Milestones Skill
+
+> Sessions are tactics. Milestones are strategy.
+> Know where you're going, not just what you're doing today.
+
+---
+
+## Why Milestones Matter
+
+Without milestones:
+- Build forever, never ship
+- Lose sight of the goal
+- Features without users
+- Burnout from endless work
+
+With milestones:
+- Clear checkpoints
+- Celebrate progress
+- Ship early, iterate
+- Sustainable pace
+
+---
+
+## Standard Milestone Template
+
+| Phase | Sessions | Goal | Checkpoint |
+|-------|----------|------|------------|
+| **Foundation** | 1-3 | Project setup, auth, core UI | "Can a user log in and see the main screen?" |
+| **MVP** | 4-7 | Core features working | "Can a user do the ONE main thing?" |
+| **Polish** | 8-10 | UX, testing, hardening | "Would I be embarrassed to show this?" |
+| **Launch** | 11-12 | Deploy, soft launch | "Is one real person using this?" |
+| **Iterate** | 13+ | User feedback driven | "What did users actually need?" |
+
+---
+
+## Milestone Reviews
+
+### At Session 3 (End of Foundation)
+
+Ask user:
+> "Foundation complete. We have [summary].
+>
+> Before moving to MVP features:
+> 1. Is the base solid?
+> 2. Any concerns about architecture?
+> 3. Ready to build core features?"
+
+### At Session 7 (End of MVP)
+
+Ask user:
+> "MVP features complete. The app can [core function].
+>
+> Decision point:
+> - **Option A:** Polish and launch with current features
+> - **Option B:** Add [2-3 more features] then launch
+> - **Option C:** Keep building (not recommended)
+>
+> Most successful products launch earlier than feels comfortable."
+
+### At Session 10 (End of Polish)
+
+Ask user:
+> "App is polished and tested.
+>
+> Launch checklist:
+> - [ ] Core features work
+> - [ ] Obvious bugs fixed
+> - [ ] Basic error handling
+> - [ ] Mobile works (if applicable)
+>
+> **It's time to get real users.** What's the launch plan?"
+
+---
+
+## Milestone Tracking
+
+Add to PROGRESS.md:
+
+```markdown
+## Milestones
+
+| Phase | Target | Actual | Status |
+|-------|--------|--------|--------|
+| Foundation | Session 3 | Session 3 | ✅ Complete |
+| MVP | Session 7 | Session 8 | ✅ Complete |
+| Polish | Session 10 | - | 🔄 In Progress |
+| Launch | Session 12 | - | ⏳ Upcoming |
+```
+
+Update at end of each session.
+
+---
+
+## Scope Creep Detection
+
+At each session start, check:
+
+1. **Are we still in the same milestone?**
+   - If milestone changed without completing previous → flag it
+
+2. **How many sessions since last milestone?**
+   - If 5+ sessions in same milestone → something's wrong
+
+3. **Is backlog growing faster than completing?**
+   - If yes → stop adding, start finishing
+
+---
+
+## When Milestones Slip
+
+If a milestone takes longer than expected:
+
+1. **Acknowledge it** — "We're at Session 9, MVP was planned for Session 7"
+2. **Diagnose** — Scope creep? Unexpected complexity? Rework?
+3. **Adjust** — Reduce scope or extend timeline
+4. **Document** — Note in PROGRESS.md what happened
+
+Don't silently let milestones slip. Make it visible.
+
+---
+
+## Anti-Pattern: The Endless Build
+
+Warning signs:
+- Session 15+ without real users
+- "Just one more feature before launch"
+- Backlog grows every session
+- No milestone ever completed
+
+Solution:
+- Stop adding features
+- Launch what you have
+- Get real feedback
+- THEN decide what's next
+
+---
+
+## Custom Milestones
+
+For non-standard projects, define milestones in Baton setup:
+
+```markdown
+## Project Milestones
+
+| Phase | Sessions | Definition of Done |
+|-------|----------|-------------------|
+| [Phase 1] | 1-X | [What must be true?] |
+| [Phase 2] | X-Y | [What must be true?] |
+| [Launch] | Y-Z | [What must be true?] |
+```
+
+Every project needs at least:
+1. A "working" milestone (MVP)
+2. A "launch" milestone (real users)
+
+---
+
+*Last updated: Baton Protocol v3.1*

package/templates/skills/core/production-readiness/SKILL.md

@@ -0,0 +1,307 @@
+---
+name: production-readiness
+description: >-
+  Pre-launch production checklist covering security, error handling,
+  monitoring, database, deployment, UX polish, performance, analytics,
+  and legal requirements. Use before launching to real users or when
+  reviewing production readiness.
+---
+
+# Production Readiness Skill — Launch Checklist
+
+> Complete this checklist before launching to real users.
+> Not every item applies to every project — mark N/A where appropriate.
+
+---
+
+## Pre-Launch Gate
+
+**Do not launch until you can answer YES to all critical items.**
+
+---
+
+## 1. Security (Critical)
+
+See `skills/core/security/SKILL.md` for details.
+
+### Must Have
+- [ ] No secrets in codebase
+- [ ] Environment variables for all sensitive config
+- [ ] RLS enabled on all database tables
+- [ ] Input validation on all forms and APIs
+- [ ] Authentication on all protected routes
+- [ ] HTTPS enforced
+
+### Should Have
+- [ ] Rate limiting on public endpoints
+- [ ] Security headers configured
+- [ ] File upload validation (type + size)
+- [ ] Error messages don't leak internals
+
+---
+
+## 2. Error Handling (Critical)
+
+### Must Have
+- [ ] Global error boundary (catches React crashes)
+- [ ] API routes return proper error responses
+- [ ] Forms show validation errors to users
+- [ ] Database errors don't crash the app
+
+### Implementation
+
+```tsx
+// Error boundary (app/error.tsx)
+'use client'
+
+export default function Error({
+  error,
+  reset,
+}: {
+  error: Error
+  reset: () => void
+}) {
+  return (
+    <div>
+      <h2>Something went wrong</h2>
+      <button onClick={reset}>Try again</button>
+    </div>
+  )
+}
+```
+
+---
+
+## 3. Monitoring & Observability (Critical)
+
+### Must Have
+- [ ] Error tracking installed (Sentry, LogRocket, etc.)
+- [ ] Errors are captured with context
+- [ ] Alerts configured for critical errors
+
+### Should Have
+- [ ] Health check endpoint (`/api/health`)
+- [ ] Uptime monitoring (Vercel, UptimeRobot, etc.)
+- [ ] Performance monitoring (Core Web Vitals)
+
+### Health Check Example
+
+```typescript
+// app/api/health/route.ts
+export async function GET() {
+  try {
+    // Check database connection
+    await db.query('SELECT 1')
+
+    return Response.json({
+      status: 'healthy',
+      timestamp: new Date().toISOString(),
+    })
+  } catch (error) {
+    return Response.json(
+      { status: 'unhealthy', error: 'Database connection failed' },
+      { status: 503 }
+    )
+  }
+}
+```
+
+---
+
+## 4. Database (Critical)
+
+### Must Have
+- [ ] Backups configured (Supabase/provider handles this)
+- [ ] Backup restoration tested at least once
+- [ ] Migrations versioned and tracked
+- [ ] Indexes on frequently queried columns
+
+### Should Have
+- [ ] Connection pooling configured
+- [ ] Query performance reviewed
+- [ ] Soft deletes for important data (audit trail)
+
+---
+
+## 5. Deployment (Critical)
+
+### Must Have
+- [ ] Production environment configured
+- [ ] Environment variables set in production
+- [ ] Build passes in production environment
+- [ ] Domain configured and working
+
+### Should Have
+- [ ] CI/CD pipeline configured
+- [ ] Preview deployments for PRs
+- [ ] Rollback procedure documented
+
+### Rollback Procedure Template
+
+```markdown
+## Rollback Procedure
+
+1. Go to [Vercel/Netlify/etc.] dashboard
+2. Navigate to Deployments
+3. Find last working deployment
+4. Click "Promote to Production" or "Redeploy"
+5. Verify rollback successful
+6. Investigate and fix the issue
+7. Deploy fix when ready
+```
+
+---
+
+## 6. UX Polish (Important)
+
+### Must Have
+- [ ] Empty states for all lists ("No items yet")
+- [ ] Loading states for async operations
+- [ ] Error states with recovery options
+- [ ] Mobile responsive (unless desktop-only)
+
+### Should Have
+- [ ] Confirmation dialogs for destructive actions
+- [ ] Success feedback for completed actions
+- [ ] Keyboard accessible (Tab navigation works)
+- [ ] Focus management (modals trap focus)
+
+### Empty State Example
+
+```tsx
+{items.length === 0 ? (
+  <div className="text-center py-12">
+    <h3>No items yet</h3>
+    <p>Create your first item to get started.</p>
+    <Button onClick={openCreateModal}>Create Item</Button>
+  </div>
+) : (
+  <ItemsList items={items} />
+)}
+```
+
+---
+
+## 7. Performance (Important)
+
+### Must Have
+- [ ] No blocking resources on initial load
+- [ ] Images optimized (Next.js Image, WebP, etc.)
+- [ ] Build size reasonable (<500KB JS initial)
+
+### Should Have
+- [ ] Core Web Vitals passing (LCP, FID, CLS)
+- [ ] Lazy loading for below-fold content
+- [ ] Caching strategy defined
+
+### Check Performance
+
+```bash
+# Run Lighthouse audit
+npx lighthouse https://yourdomain.com --view
+
+# Or use Vercel Speed Insights, PageSpeed Insights
+```
+
+---
+
+## 8. Analytics (Important)
+
+### Should Have
+- [ ] Page view tracking
+- [ ] Key action tracking (signups, conversions)
+- [ ] Error tracking linked to user sessions
+
+### Options
+
+| Tool | Best For |
+|------|----------|
+| Vercel Analytics | Simple, privacy-focused |
+| Plausible | Privacy-focused, EU compliant |
+| PostHog | Product analytics, session replay |
+| Google Analytics | Comprehensive, free |
+
+---
+
+## 9. Legal (If Public)
+
+### Must Have (If Collecting User Data)
+- [ ] Privacy Policy page
+- [ ] Terms of Service page
+- [ ] Cookie consent (if using cookies for tracking)
+
+### Should Have
+- [ ] GDPR compliance (if EU users)
+- [ ] Data deletion capability
+- [ ] Clear data usage explanation
+
+---
+
+## 10. Documentation (Important)
+
+### Must Have
+- [ ] README with setup instructions
+- [ ] Environment variables documented
+- [ ] Key features documented for users
+
+### Should Have
+- [ ] API documentation (if applicable)
+- [ ] Deployment guide
+- [ ] Troubleshooting guide
+
+---
+
+## Launch Readiness Score
+
+Rate each category:
+- ✅ Complete
+- 🟡 Partial (acceptable for launch)
+- ❌ Incomplete (blocker)
+
+| Category | Status | Notes |
+|----------|--------|-------|
+| Security | | |
+| Error Handling | | |
+| Monitoring | | |
+| Database | | |
+| Deployment | | |
+| UX Polish | | |
+| Performance | | |
+| Analytics | | |
+| Legal | | |
+| Documentation | | |
+
+**Launch when:** All critical items are ✅, important items are at least 🟡.
+
+---
+
+## Post-Launch Checklist
+
+First 24 hours:
+- [ ] Monitor error tracking for new errors
+- [ ] Watch for performance issues
+- [ ] Respond to user feedback quickly
+- [ ] Check analytics are recording
+
+First week:
+- [ ] Review error patterns
+- [ ] Address critical bugs immediately
+- [ ] Collect user feedback
+- [ ] Plan improvements based on real usage
+
+---
+
+## Common Launch Mistakes
+
+| Mistake | Prevention |
+|---------|------------|
+| Forgot to set production env vars | Use checklist, verify before launch |
+| No error tracking | Install Sentry before launch |
+| No backup strategy | Verify provider backups, test restore |
+| Missing empty states | QA with empty database |
+| No rate limiting | Add before launch, not after attack |
+| No rollback plan | Document procedure, test it |
+
+---
+
+*Last updated: Baton Protocol v3.1*