← Back




VibeCoder-Standalone Refinement Plan

VibeCoder-Standalone Refinement Plan

v2 — with status. Premise (corrected from pact, not from old guesses): VibeCoder is a sovereign workspace (one of 4: Origin, VibeCoder, VibeScope, FreshCards). Two layouts: Vibe (Stencil + Preview + Inspector) and Coder (code editor + VSIL execution + Logs). Co-equal, not 'main + sidekick'. Centre pane IS the Monaco code editor per the pact. Externalize it for build size, do NOT replace it.

Plan composed 2026-07-29 18:24 BST. v2 with status 2026-07-30 00:10 BST. 9 steps. 12-13h total estimated. 9 deploys.

Status

#StepStateTime estRisk
0 Register on Mavis HQ + import past state DONE 2026-07-29 18:24 BST 15 min Zero
0.5 Read pact canon (workspace-model, governance, behaviour, vibe-card-variant, vibecoder-aware-mode) DONE 2026-07-29 17:00 BST 30 min Zero
1 Build foundation: externalize monaco, hash-stamp prebuild hook, MAVIS_BYPASS_TOKEN lookup WAITING — needs G's go 30 min Zero (pure config)
2 Pact corrections: rename right surface per layout (Vibe -> Inspector, Coder -> Logs), add DNA + lineage hooks, finish ⌘K command palette, 3-tab Inner Card toast WAITING — needs G's go 1.5 h Medium (constitutional)
3 Parked: dynamic daily-notes date WAITING 15 min Zero
4 Parked: file-tree filter/sort/search (per vibe-card-variant §2) WAITING 45 min Low
5 Parked: responsive inspector / mobile collapse (~768px breakpoint) WAITING 1.5 h Low
6 Parked: property editor for workspace settings (theme, default layout, surface toggles) WAITING 2 h Medium
7 Parked: real simple-git project clone (right-click context menu per vibe-card-variant §2) WAITING 2 h Medium
8 Parked: real TypeScript LSP for editor (Coder Layout only, skips Vibe Layout) WAITING 2-3 h Medium (proven in FVS Phase 4.4)
9 Final: drift-check + Playwright screenshot (1440x900 + 375x667) + memory update WAITING 1 h Zero

Progress: 2 of 11 done (registration + pact read). 9 to ship. All "WAITING" because G hasn't said "go" yet.
Thread: vibecoder-standalone-mavis (thread_id 9 on Mavis HQ)
Repos: avidtech6/vibecoder-standalone + avidtech6/freshvibestudio (FVS module, untracked files only)
Live URL: vibecoder.freshvibeapps.com (stale — needs Phase 4.0+4.1+4.4 dist refresh, current is Phase 3.2 from 2026-07-08)

Decisions needed from G

  1. Step 1 (build foundation) go ahead? Pure config, zero risk. I can start now.
  2. Step 2 (pact corrections) — is the layout naming right? "Vibe Layout" + "Coder Layout" as the two co-equal layouts, with a switcher chip in the top row?
  3. Do all 8 in sequence, or pick which to do first? I can stop after any step.
  4. Real AI integration (Vibe Layout Stencil + chat) — in scope for the standalone, or is Vibe Layout just inspector + preview with no AI? (Pact says Stencil is part of Vibe Layout, but I don't have an LLM call site wired up yet for the standalone.)
  5. Vibe Chat (Studio-level feature per §24) — does the standalone need it? Or is the standalone pure VibeCoder with no Vibe Chat?

What I'm blocked on (not the operator's fault)

If G answers "go + no AI + no Vibe Chat"

I can finish all 9 in about 12 hours. You'd have a working, pact-correct, mobile-friendly VibeCoder at vibecoder.freshvibeapps.com by end of day tomorrow, with the live URL going from Phase 3.2 (stale) to Phase 4.0+4.1+4.4 (current FVS) + 6 parked items (Step 2 + 3 + 4 + 5 + 6 + 7 + 8) + drift-check pass (Step 9).

What I'm NOT doing

Last updated 2026-07-30 00:10 BST.