brainstorming

Start by exploring the current project context, then answer clarifying questions one at a time about purpose, constraints, and success criteria. The process proposes 2-3 approaches with trade-offs, presents the design in sections for approval, and writes a spec document before any implementation begins.

A design spec is a written document capturing the approved architecture, components, data flow, error handling, and testing approach for a feature. It is saved to a dated file, self-reviewed for placeholders and contradictions, and must be approved by the user before implementation planning starts.

Run the start-server.sh script with a project directory to launch a local server, then write HTML content fragments to the screen directory it returns. The browser displays mockups, option cards, and diagrams, and user clicks are recorded as JSON events you can read on the next turn.

Yes, the start script auto-detects Windows (Git Bash) and Codex environments and switches to foreground mode since those platforms reap background processes. On Windows, launch it with a background shell call; on Codex, run it normally with no extra flags.

Never. The process explicitly requires a design for every project regardless of perceived simplicity, since simple projects are where unexamined assumptions cause the most wasted work. The design can be just a few sentences, but it must be presented and approved.