Tools & Workflow
Updated July 2026
Tools change often, the workflow changes less: understand the problem, define the decisions, map the uncertainty, review the risks, build, then refine the output. Superpowers runs underneath as a substrate, its skills invoked implicitly throughout.
Frame
Start with the brief. /grill-with-docs makes the terms, scope, ownership, states, and failure cases explicit before anything gets designed.
Shape
Once the decisions are clear, /paper-prototype turns the open interface question into options in Paper. Lo-fi when structure is the risk. Hi-fi when behaviour, visual treatment, or build path needs testing.
Review
Before code, /pre-build-review looks for the things that usually break later: missing states, mobile pressure, accessibility gaps, weak data assumptions, and unclear build details. Anything unresolved goes back to the right step.
Build
Codex is my main workspace at the moment. I’m also testing Cursor, Conductor and cmux running Pi to keep the setup agent-agnostic.
One branch per outcome, one worktree per parallel thread. Separate worktrees keep experiments clean without cluttering the repo.
/ui-craft keeps the build sharp across components, interaction, accessibility, copy, motion, and detail.
When a thread pauses or context runs long, /handoff compacts the session into a Markdown document any agent or harness can resume from — state, decisions, and the next move, not a transcript.
Refine
Once it runs, I mark up the interface directly on the browser: spacing, hierarchy, states, copy, motion, and edge cases until the result is tight.
Papercuts too small for a full session go through /polish-fix: one fix, a before/after screenshot, and a PR approvable on sight.
Ship & Learn
Before anything ships, /post-build-review — the read-only mirror of /pre-build-review — checks the built change against the intent that was set and its promised states, then assembles the handoff evidence.
Public work ships through Vercel for larger projects, or Drop for a quick share. Afterwards, I refine the process: sharper prompts, better skills, useful checks, and anything that no longer earns its place gets cut.
