vibe-new-applisted

Full spec-driven setup workflow for building a brand new app from scratch with an AI coding agent. Triggers on "new:" prefix, "I want to build a new app", "starting a new project", "help me spec out a new app", "new project". Always use when the user is starting a greenfield project — even without the exact prefix. Generates CLAUDE.md at project root and the complete vibe/ folder. Reads BRIEF.md and ARCHITECTURE.md if they exist — skips questions already answered. Step 5 generates a complete multi-phase feature map in PLAN.md — every feature sequenced, dependencies explicit, parallel opportunities identified, future phases sketched. TASKS.md Phase 2+ shows ordered features with dependencies visible — not slugs. Generates a minimal ARCHITECTURE.md from PLAN.md if architect: was skipped. TASKS.md is the single human-facing file. TODO.md does not exist. Requires: frontend-design skill for Step 3 wireframe generation.
aakashdhar/vibe-skill · ★ 7 · AI & Automation · score 68

Install: claude install-skill aakashdhar/vibe-skill

# Vibe New App Skill Generates the complete project kit from brief and architecture. Produces CLAUDE.md at project root and the full vibe/ folder the AI coding agent uses. **Always run in Plan Mode (Shift+Tab). Exit Plan Mode only before task execution.** > **Autonomous / headless mode.** At startup resolve the settings with > `python3 ~/.claude/skills/vibe-mode/scripts/vibe_state.py mode`. If `vibe_mode` is > `autonomous`, every "wait", "ask", "confirm" and approval step in this skill follows > vibe-mode's `references/HEADLESS.md` §2 instead: take the recommended option, accept your > own draft after one self-check, log each choice to `vibe/DECISIONS.md`, never ask the > user, and stop — writing `vibe/.run_state.json` — only when a person is genuinely required. --- ## The O'Reilly principles this enforces **Spec before code** — SPEC.md with acceptance criteria exists before any task runs. **Context preservation** — CLAUDE.md, CODEBASE.md, ARCHITECTURE.md, SPEC_INDEX.md, TASKS.md read every session so the agent never re-discovers what's been built. **Incremental verifiable progress** — TASKS.md breaks the build into single verifiable tasks. **Drift prevention** — DECISIONS.md created ready to log from the first task forward. --- ## Two audiences. Two file types. **Human-facing — open this:** - `vibe/TASKS.md` — your single progress view. Plain English. Updated after every task. **Agent-facing — agent reads these, you never need to open them:** - `CLAUDE.md` · `vibe/