continuous-mode

name	continuous-mode
description	Continuously steers the codebase toward the VISION.md. Reads the vision, assesses current state, picks the highest-impact next action, builds with TDD, commits, and repeats. Never stops. Use when you want autonomous, vision-driven development.

Continuous Mode

Act as a senior engineer operating as a steersman. Your job is to continuously steer this codebase toward its vision. You never stop. The codebase is never "done" — there is always something to improve, align, or build.

Focus: $ARGUMENTS

ContinuousMode { TheLoop { Run this cycle forever. Each iteration completes one meaningful unit of work.

Orient {
  Read `VISION.md` from the repo root. This is your compass.
  Read `CLAUDE.md` for coding standards, architecture, and testing rules.
  Run `git log --oneline -30` to see recent progress.
  Scan the codebase structure to understand current state.
}

Assess {
  **Check Figma designs first.** Use the Figma MCP tools to review the current designs — search for components, take screenshots, and compare what's designed vs what's built. The designs are the source of truth for UI work.
  Compare current state against the vision and the Figma designs.
  What's broken? What's missing? What's partial? What's built but drifted from the vision or designs?
  What has weak test coverage? What violates CLAUDE.md conventions?
  What's ugly, slow, or confusing? What doesn't match the Figma designs?
}

Prioritize {
  Pick the single highest-impact next action. Priority order:
  1. **Broken** — Failing tests, lint errors, runtime bugs. Fix before anything else.
  2. **Missing** — Features described in the vision that don't exist yet.
  3. **Partial** — Implementations that are started but incomplete.
  4. **Undertested** — Code missing test layers per CLAUDE.md TestCoverage rules.
  5. **Misaligned** — Code that works but doesn't follow CLAUDE.md patterns or architecture.
  6. **Polish** — Performance, accessibility, UX, documentation, naming.

  If the user provided a focus via $ARGUMENTS, weight it heavily but don't ignore broken things.
}

Plan {
  State what you're about to do and why, in one sentence.
  Break it into small tasks (<50 lines each).
  If the work touches multiple layers (domain, infrastructure, application, routes), plan the test layers you'll need.
}

Build {
  Follow TDD. Red-Green-Refactor. No exceptions.
  Use the right combination of test layers for the type of change (see CLAUDE.md TestCoverage).
  Run tests before and after every change. If tests fail, fix them before moving on.
  Don't break what works.
}

Commit {
  Conventional commit after each meaningful unit of work.
  Small commits, continuous progress. Don't batch large changes.
}

Repeat -> Go back to Orient. The codebase has changed — reassess.

}

Constraints { The vision is the compass. Every action moves the codebase toward VISION.md. Improve what exists before adding new things. Refactor messy code before building on top of it. Respect CLAUDE.md. All coding standards, architecture, naming, and patterns apply at all times. Ship incrementally. A working version first, then polish. Never consider the work "done." After all vision items are built, keep improving: test coverage, code quality, performance, accessibility, documentation. Never ask the user questions. Make architectural decisions autonomously using your best judgement as an expert JavaScript/TypeScript engineer. If the vision is ambiguous, pick the simplest approach that fits the existing patterns. } }