skill: vibe-code-webapp

Name: Vibe-Coding Web App Builder (onboard → scan existing → research → evaluate → build pack + todo → confirm → build step-by-step → audit → report + everything-auditor → deliver) Description: Turns any app idea — "I want to build something like X with Next.js" — into a complete, distraction-free build pack and then a working, production-ready web app. The skill first onboards you with a detailed idea interview, and if you're already in a project with code, scans the existing structure so the plan extends what exists instead of restarting. Then it researches the idea, evaluates it (kill the dud ideas cheaply), and writes the Build Pack: PRD.md (what to build) + stack-blueprint.md (exactly HOW — locked open-source design system, backend architecture, paste-ready data model, numbered build order) + sitemap.md (the whole app on one page — full sitemap, every frontend page, backend architecture, workflows) + TODO.md (the task list with P0/P1/P2 priorities). You confirm the pack AND the todo list before any code — and you can add tasks or re-prioritize them anytime, even mid-build. The pack is tool-agnostic: build with any CLI (Claude Code, Cursor, Codex, Gemini CLI, Antigravity, Grok Build, Freebuff) or paste it into web builders (Lovable, Bolt, v0). A daily MEMORY.md records decisions, progress and next steps so you (or any AI, in any tool) can pick up exactly where you left off — every single day. The production audit runs on whatever folder any tool produces.

When to use

• "I want to build something like X" / "an app with Next.js" — any idea + optional stack preference (new project)
• "Extend my app / add this feature to the project I already have" — existing project mode: the skill scans your structure first, then plans the extension on top of it
• "Turn this idea into a SaaS / MVP / tool" — full pipeline
• User has a stack in mind ("React + Vite", "Next.js + Supabase") → the skill validates it and locks it into the pack
• Non-SaaS too (tools, internal apps, landing+waitlist): skip monetization-specific checks, keep the rest
• "Start the day with context" / "remember where we are" → the memory protocol (MEMORY.md) is always on

Invariant: Research, scanning and evaluation are always allowed; no code is written before the user has approved the Build Pack (PRD.md + stack-blueprint.md + sitemap.md) and the todo list (TODO.md).