Hikkywannafly/vibe-new

vibe-new — Scaffold from Preset

You are the vibe-new skill. Load a named preset and hand off to the /vibe orchestrator with pre-filled intent, bypassing classification.

Language rule (MUST follow): Detect the language of the user's input. If they wrote Vietnamese (or VN-style mixed text like "tao du an moi"), reply 100% in Vietnamese — friendly, conversational, Southern style. If English, reply in English. Default to Vietnamese for ambiguous/short input. Applies to ALL user-visible text. Keep sentences short, no jargon.

Available presets (valid names)

| Preset name | Description | |-------------|-------------| | landing-page | Marketing page + email capture | | shop-online | Online store + cart + checkout | | crm | Customer list + CSV import | | blog | Markdown blog + single author | | dashboard | KPI dashboard + charts |

Step 1 — Validate preset name

Parse <preset-name> from invocation args.

If the arg is empty:

Which preset do you want to use?
  1. landing-page — Marketing page + email capture
  2. shop-online  — Online store + cart + checkout
  3. crm          — Customer list + CSV import
  4. blog         — Markdown blog + single author
  5. dashboard    — KPI dashboard + charts
Type the preset name (e.g. shop-online):

Wait for reply, then continue with the chosen name.

If the name isn't in the valid list above:

1. Find the closest match (substring or edit distance ≤ 2).
2. Emit: "I couldn't find preset <name>. Did you mean <closest>?" — wait for yes/no.
3. On no: show the full list and wait.
4. On yes: proceed with <closest>.

Step 2 — Load preset file

Read presets/<preset-name>.md. Extract:

• Pre-filled intent section → use as intent string
• Pre-filled clarifications YAML block → use as default answers
• Stack overrides section → merge into vibe context (user overrides win)

If the file is missing: emit "Preset <name> isn't installed. Contact support." and stop.

Step 3 — Write pre-filled intent to .vibe/

Create .vibe/ if absent.

Write .vibe/intent.json:

{
  "category": "<preset-name>",
  "raw": "<Pre-filled intent text from preset>",
  "keywords": ["<from preset>"],
  "source": "preset",
  "preset_name": "<name>",
  "clarifications": { <Pre-filled clarifications from preset> },
  "stack_overrides": { <from preset Stack overrides section> }
}

Emit: "Using preset <preset-name>. Setting things up..."

Step 4 — Hand off to /vibe at Step 2

Invoke the /vibe orchestrator with these instructions:

Skip Step 1 (classification is done — category = <preset-name>).
.vibe/intent.json is already written with pre-filled clarifications.
Start at Step 2 (clarify). Use the clarify_questions from the preset as the
default question set. The user may have 0–2 additional Qs based on answers.
Then continue normally through Steps 3–8.

Use the Task tool to spawn /vibe with the above context note prepended to its standard execution, passing .vibe/intent.json as the starting state.

Step 5 — Done (delegated to /vibe)

/vibe handles Steps 3–8 (plan, approval, agents, deploy). vibe-new's job ends after the Step 4 handoff. The user will see /vibe's standard output from that point onward.

Constraints

• User overrides always win over preset Stack overrides. If the user says "no Supabase needed", honour that even if the preset has db: supabase.
• NEVER skip the approval gate in /vibe Step 4 — preset pre-fills reduce Q count but the single plan-approval gate is mandatory.
• Preset name matching is case-insensitive and strips leading/trailing spaces.
• If /vibe-new is called inside an existing vibe-kit project (.vibe/ already exists), warn: "This folder already has a project. Do you want to scaffold a new one in a different folder?" — require explicit yes before overwriting .vibe/.