Further Reading for Pi
Tutorials, documentation and walkthroughs for designing with Pi, as listed in the published guide.
How to design interfaces with Pi in OpenDesign: portable skills, the model and key you choose, one plan-comparison task from brief to reviewed file, and the limits to know before you start.
“Plan comparison with one
portable skill, any model.”
THREE WAYS INTO THIS PI GUIDE
This guide: brief, references, design rules and a reviewed HTML result.
Read this guide SETUPHere is the full path from a clean machine to a Pi that can build and verify UI.
Go to setup COMPARISONHow Pi differs from Codex, Claude Code, Cursor for design work, and when to choose another workflow.
See the comparisonOne Complete Pi Design Task
A single task, shown end to end: the brief and constraints you hand over, the artifact that comes back, and the checks you still run before it is done. The interface below is an illustrative example built for this page, not a recorded Pi run.
BriefDesign a plan comparison page for a note-taking app: free, personal and team plans, a feature comparison and a short FAQ. Desktop and phone.
data-od-id hooksWrite the brief, select the design system and define the acceptance criteria.
Plans the layout, writes the HTML, CSS and JavaScript and revises it on request.
Provides the design system and skill, renders the preview and stores every version as a file in the project.
Visual hierarchy, spacing on the 8px grid, both breakpoints and every interaction are checked before handoff.
Three plans and the comparison share the 8px grid; feature rows align across columns.
Price and plan name first; the accent marks the most-chosen badge and its button.
Personal plan first, then free, then team; the toggle stays at the top.
Flip the toggle, tab through CTAs, expand one comparison row.
Fit
Compatibility
This guide covers Pi as connected through the OpenDesign desktop app. Published references checked on 6 September 2026.
Pi is an open-source (MIT) terminal AI coding agent from earendil-works. It reads your codebase, edits files, and runs commands from a small four-tool core — read, write, edit, bash. This page is about designing interfaces with Pi through OpenDesign, not about Pi’s own interface. OpenDesign’s setup notes list the available agents.
Your own provider API key (BYOK) or subscription login via /login. Authenticate with your own provider API key (BYOK) or a subscription login — credentials stay on your machine. This page does not promise a quota or price.
Check the download page for desktop builds. The Node.js and pnpm requirements in the source quickstart apply to running from source, not to installing a desktop package. Minimum compatible Pi version: not verified here.
Follow the connection instructions shown by your installed version, then run a small task. Confirm that Pi handled it and that the artifact opens. A download alone does not establish a working connection.
Start with the desktop app
Download first, complete the Pi setup for your installed version, then check a small result. You do not need to build OpenDesign from source to follow this path.
Choose the package for your computer, install it and open the app.
Download OpenDesignFollow the Pi instructions in your installed version. Authenticate with your own provider API key (BYOK) or a subscription login — credentials stay on your machine.
Pi providers & authentication docs# 1. Install the Pi coding agent CLI (Node)
npm install -g --ignore-scripts @earendil-works/pi-coding-agent
# 2. Authenticate with your own provider key (BYOK)
export ANTHROPIC_API_KEY=sk-ant-... # or OPENAI_API_KEY=sk-...
# (or run /login inside Pi for a Claude / ChatGPT / Copilot subscription)From the Pi setup notes in the published guide; check the vendor documentation for the current command.
Use a small brief so you can judge the whole loop, including one revision.
Build a settings screen with a profile form and a save confirmation. Use my design rules. Check it at desktop and mobile widths.
To run OpenDesign from source, follow the technical quickstart instead.
The Pi design workflow
The same plan comparison page task, followed from brief to verified file. Each step lists what you provide, what Pi does, what OpenDesign contributes and what you check.
Plain language, three to six lines. Name the audience, the job of the screen and the platforms.
A design system and a few hard rules. This is what separates on-brand output from a generic look.
Pi writes a self-contained HTML file: layout, styles, interactions and stable hooks.
The file renders inside OpenDesign at the widths you asked for. This is where the design is judged.
data-od-id targets for comments and edits.Request changes by pointing at elements in the preview. Every revision is a new file; nothing is overwritten silently.
Resources
Tutorials, documentation and walkthroughs for designing with Pi, as listed in the published guide.
The artifact types Pi can produce in OpenDesign, one skill per type.
Brand tokens and components to bind before Pi generates anything.
Starting points for decks, landing pages and product screens.
Limitations
FAQ
Start with a small task, judge the round trip, then bring the real brief. Choose the option that matches your setup; the page does not detect it.