Tools & Workflow
Updated June 2026
The tools change relatively often. The workflow changes less: understand the problem, define the decisions, sketch the remaining uncertainty, review the risks, build, then tighten the running interface.
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 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.
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.
Ship & Learn
Public work ships through Vercel or GitHub Pages. Afterwards I update the process: sharper prompts, better skills, useful checks, and steps that no longer earn their place.
