UV Suite

A portable layer that turns Claude Code, Cursor, or Codex into a labeled, observable, anti-slop dev environment — with named sessions, a real-time observability and control dashboard, anti-slop guardrails, and per-session memory across launches.

By Utsav · github.com/utsavanand/uv-suite

Install

npm install -g uv-suite
uvs claude pro                # auto-installs into the current project on first launch

Or with npx:

npx uv-suite install          # explicit install only

Note: The CLI is uvs, not uv. The name uv belongs to Astral's Python package manager and likely already exists on your system.

Quick Start

uvs claude pro                # Claude Code, Professional persona
uvs codex auto                # Codex, Auto persona
uvs pro                       # Shorthand for uvs claude pro
uvs install                   # Explicit install (also runs automatically on launch)
uvs watch                     # Open the Watchtower observability + control dashboard
uvs info                      # Show what's installed

On every uvs launch, you'll be prompted to label the session:

Label this session (Enter to skip — you'll be reminded):
  name:                     payments retry refactor
  kind [long/outcome]:      outcome
  purpose:                  ship retry-on-5xx for the Stripe webhook handler
  priority [low/med/high]:  high

Skip any field with Enter. If you skip the name, /session init will be suggested every few prompts until you label it. Set UVS_NO_PROMPT=1 to suppress prompts entirely.

Start here

After uvs claude pro, pick the path that matches what you're doing. Each path names the first skill to run and the canonical next steps.

Existing codebase (you didn't write this)

1. /understand — builds a knowledge graph + architecture overview in uv-out/map-codebase.md. Other skills (/architect, /review, /review --security) read it automatically.
2. /session checkpoint — captures your baseline understanding so /session restore can bring it back next session.
3. Then: /review on the current diff, or /spec for the next feature.

New project (you're starting from scratch)

1. /spec — converts your idea into a structured spec in uv-out/specs/.
2. /architect — breaks the spec into Acts with cycle budgets. Reads the spec automatically.
3. Then: implement Act by Act. Use /test and /review per Act.

Reviewing a PR

1. /review [branch-name] — reads diff + CLAUDE.md + DANGER-ZONES.md + prior uv-out/ artifacts.
2. /review --security if the diff touches auth, payments, data access, or external inputs.

Shipping

1. /session checkpoint to capture state.
2. /commit — runs review, tests, commits, optionally opens a PR.

Picking a persona (Spike / Sport / Professional / Auto) is a separate axis from picking a first skill — see Personas below for which mode fits which situation.

Sessions and Watchtower

Each uvs launch generates a UVS_SESSION_ID and writes metadata to .uv-suite-state/sessions/<id>.json. This unlocks:

• Concurrent terminals don't collide. Two uvs launches in the same repo run as distinct sessions with separate names, checkpoints, and dashboard rows.
• uvs watch shows them all. The Watchtower control plane at localhost:4200 streams every session live and lets you act on them from the browser — see Watchtower at a glance.
• Per-session checkpoints. /session checkpoint writes to uv-out/checkpoints/<sid>/, and /session restore auto-picks the current session's latest. Pass a session id prefix or name to restore from a different one.
• Status line shows it all. The Claude Code status bar shows session name, persona, priority, and elapsed time continuously.

Watchtower at a glance

uvs watch starts the dashboard at localhost:4200 — Python + embedded SQLite, no Docker and no database to set up (it provisions its own deps on first run). It's a control plane, not just a viewer, laid out in three panes:

• Heartbeat (left) — a live, scrolling stream of what every agent is doing, as it happens.
• Sessions (center) — each session as a flat row (state · tokens · tool calls · last activity). Filter by time / priority / kind and search by name; expand a row to checkpoint, view checkpoint history, compact, fork, close, or delete it.
• Needs human (right) — sessions waiting on you (a tool-permission prompt or an idle wait), with the tool + command as context. Approve / Deny from the browser; for uvs-launched (tmux-owned) sessions the keystroke is sent for you.

Sessions launched via uvs run inside a transparent tmux so Watchtower can act on them. Hooks forward every Claude Code event (PreToolUse, PostToolUse, UserPromptSubmit, Notification, SessionStart, Stop, ...) with session metadata merged in. A Node-only fallback (no Python) is available via uvs watch --legacy.

Personas

Four modes for different contexts. Pick one when you start a session.

             Spike          Sport        Professional       Auto
             ─────          ─────        ────────────       ────
Purpose      Research       Build new    Ship to prod       Let it run
             & document     things

Model        Opus           Sonnet       Inherit            Inherit
Effort       max            high         high               max

Writes       New files      Anything     Anything           Anything
             only                        (reviewed)         (autonomous)
Edits        Blocked        Allowed      Allowed            Allowed

Guardrails   Doc slop       None         All 6              All 6
Human gates  After each     End only     Every Act          Final output
             map                         boundary           only

When to use what

| Situation | Mode | Why | |---|---|---| | Joining a new codebase | Spike | Understand before changing. Writes docs, not code. | | Architecture review | Spike | Map the system, write ADRs, document findings. | | Prototyping a demo | Sport | Move fast, iterate freely, quality comes later. | | Hackathon or new project | Sport | Get the foundation down without review gates. | | Fixing a bug in production code | Professional | Every change matters. Full review rigor. | | Adding a feature to an existing service | Professional | Team depends on this code. Slop-checked. | | Well-scoped task with a clear spec | Auto | Let the agent build, test, review end-to-end. | | Batch of small tasks | Auto | Agent handles repetitive work autonomously. |

Common progressions:

• Spike → Sport → Professional (understand, explore, harden)
• Spike → Auto (research thoroughly, then let the agent execute)
• Sport → Professional (prototype fast, switch to rigor when it matters)

Skills (slash commands)

12 skills. Each skills/<name>/SKILL.md is a thin orchestrator that dispatches to agents.

| Command | What it does | |---|---| | /understand [dir] | Map a codebase or whole stack — auto-detects repo vs stack | | /spec [requirements] | Write a technical specification | | /architect [spec] | Design architecture, decompose into Acts | | /test [file] | Write tests or evals: --unit / --integration / --eval (DeepEval compatible) | | /review | Multi-specialist code review; add --security (OWASP via Semgrep/Gitleaks/Trivy) or --slop (anti-slop audit) | | /prototype [concept] | Build a static React prototype | | /qa | Browser QA via Playwright MCP | | /investigate | Systematic root-cause debugging | | /commit | Review → test → commit (and optionally PR) | | /session init\|checkpoint\|restore\|end\|auto | Session lifecycle — label, checkpoint, restore, end, or auto-checkpoint | | /confirm [on\|off\|<n>] | Toggle reframe-and-confirm for prompts over <n> words | | /uv-help | List every skill, agent, hook, guardrail, and persona |

Hooks (lifecycle automation)

Fire automatically on Claude Code events. You never invoke these. ~26 scripts live in hooks/.

| Hook | Fires on | What it does | |---|---|---| | auto-lint | File write | Runs prettier, ruff, or gofmt | | slop-grep | File edit/write | Ambient slop detection on sport / professional / auto personas | | doc-slop-grep | File edit/write | Catches vague adjectives in markdown on the spike persona | | danger-zone-check | File edit | Warns if file is in DANGER-ZONES.md | | block-destructive | Bash command | Blocks rm -rf /, force push to main, DROP TABLE | | confirm-prompt | UserPromptSubmit | For prompts over the threshold, requires Claude to restate before any work starts | | session-label-nag | UserPromptSubmit | Reminds you to run /session init every Nth prompt while the session has no name | | context-warning | PostToolUse | Warns when context usage crosses thresholds | | watchtower-send | All events | Forwards every event (with session metadata) to localhost:4200 | | session-start | SessionStart | Records start time, fires bootstrap event with session metadata | | session-timer | PostToolUse | Reminders at 45 / 90 / 180 minutes | | session-end | Stop | Shows duration, today's total, reflection prompt | | session-review-reminder | Stop | Nudges you to review uncommitted changes | | uv-out-* | Session events | Manage session-scoped artifacts under uv-out/sessions/<sid>/ | | status-line | Continuous | Renders session label, persona, priority, and timer in the Claude Code status bar |

Agents

8 agents. The canonical definitions are agents/claude-code/*.md. The Cursor (.mdc) and Codex (.toml) variants are generated from those by agents/generate.py at install — they're not hand-maintained.

| Agent | Subsystem | Model | Cycle Budget | |---|---|---|---| | Cartographer | Index | Opus | 1 | | Spec Writer | Acts | Opus | 1 | | Architect | Acts | Opus | 2 | | Reviewer | Guard | Opus | 1 | | Test Writer | Acts | Sonnet | 3 | | Eval Writer | Acts | Opus | 2 | | Anti-Slop Guard | Guard | Opus | 1 | | Prototype Builder | Acts | Sonnet | 3 |

Artifacts

Agents write persistent output to uv-out/. Each agent reads prior artifacts automatically.

| Output | Read by | |---|---| | uv-out/map-codebase.md | /architect, /review, /review --security | | uv-out/specs/*.md | /architect, /test, /test --eval | | uv-out/architecture/*.md | /review, /test, /review --slop | | uv-out/review-*.md | /review --slop, /review --security | | uv-out/checkpoints/<sid>/*.md | /session restore |

Integrations

| Tool | Used by | Purpose | |---|---|---| | Graphify | Cartographer | Knowledge graph from codebase via Tree-sitter | | Semgrep | Security | SAST with 4000+ OWASP-mapped rules | | Gitleaks | Security | Secret detection in git repos | | Trivy | Security | Dependency vulnerability scanning | | DeepEval | Eval Writer | Pytest-compatible LLM evaluation | | Playwright | Prototype, Test Writer | Browser automation and e2e testing |

Project Structure After Install

.claude/
  settings.json          Permissions and hooks (seeded from your persona on first install)
  agents/                8 agent definitions (canonical .md)
  skills/                12 slash commands
  hooks/                 ~26 hook scripts
  rules/                 6 anti-slop guardrails (Pro / Auto only)
  personas/              4 persona configs
.codex/agents/           8 Codex agent definitions (generated from .claude/agents)
.cursor/rules/           8 Cursor rule definitions (generated from .claude/agents)
AGENTS.md                Codex instruction file
DANGER-ZONES.md          Risky areas (commit this)
.uv-suite-state/         Session metadata + counters (gitignored)
  current-session.txt
  sessions/<sid>.json
uv-out/                  Agent output artifacts (gitignored)
  checkpoints/<sid>/     Per-session checkpoints

Documentation

| Document | What it covers | |---|---| | CONTRIBUTING.md | Working on UV Suite — adding skills/agents/hooks, running the tests | | personas.md | 4 personas, 7 knobs, when to use each | | knowledge/practices.md | Working principles (honesty, parallelism, scope, completion) | | acts-methodology.md | Acts delivery framework with worked examples | | knowledge/human-in-the-loop.md | Cycle budgets, intervention types, learning loops | | knowledge/sharing-and-standards.md | Danger zones, team standards, sharing levels | | research/landscape.md | Open source tools and references for each agent | | research/comparison.md | UV Suite vs gstack vs Claude Code built-in — feature comparison + prompt-depth deep dive | | research/tool-comparison.md | Claude Code vs Cursor vs Codex — how UV Suite works across all three | | research/best-practices.md | Subagent patterns, remote sessions, sharing with engineers, cost optimization |

Author

Built by Utsav — utsava.xyz.

License

MIT