User Guide

Quick start — first session

1. Connect — On the home Connect section, pick your tool's tab and paste the prompt to your agent.
2. Log in — Once in the browser with Google/GitHub. (lasts 30 days)
3. Start — /purpleprint:start (or natural language “start PurplePrint” → pp_start). When the welcome shows, reply “let's start” and Phase 0 begins.

Already have writing·notes·Notion? Paste them in too — it pulls the core and backfills what's missing.

Here's how the first conversation flows:

It's a demo — the real thing runs on your idea, inside your tool. Stuck? Just say “again” or “simpler” and it fixes course.

Connect your tool

Our server is remote HTTP MCP + OAuth. No API keys, no config secrets — pick your tool and paste the prompt to your agent, and it registers itself and walks you through login. One login lasts 30 days.

Pick your tool, paste, done

Pick your tool's tab and paste the prompt straight to your agent. It registers and walks you through login.

Press the login button and this screen appears — one tap with Google or GitHub:

Stuck? See Troubleshooting below.

{
  "servers": {
    "purpleprint": {
      "url": "https://purpleprint-mcp.purpleprintai.workers.dev/mcp"
    }
  }
}

# ~/.codex/config.toml
[mcp_servers.purpleprint]
url = "https://purpleprint-mcp.purpleprintai.workers.dev/mcp"

{ "mcpServers": {
    "purpleprint": { "url": "https://purpleprint-mcp.purpleprintai.workers.dev/mcp" }
} }

Phase 0~9 flow

This is the heart of PurplePrint — a 10-step coaching flow that turns a daunting one-line idea into a build-ready design. So you never start alone and stuck, the coach leads one step at a time, one question at a time. Each step stacks on the previous one's conclusion, building the “why→who→what→how” purpose chain with no gaps in the middle.

How it goes — see for yourself

Try the tabs. The coach closes the gap first, you answer in plain words, and if you don't like it you can push back·debate — each of these is a way to use the product. It's not pressing “sounds good” like a general AI — you lead.

And then, a whole session end to end

How those usage modes actually play out — I followed a whole session, from Phase 0 to 9, on the one line “a cover-letter service.” Scroll and each step plays, and when a step finishes the artifact appears right there.

Command reference

Below is the /purpleprint:<command> form for slash clients (Claude Code·Cursor). Tool clients (Codex) use the same features as pp_<command> — e.g. /purpleprint:status = pp_status.

Here's how a Hyper-Review series run progresses (dev-design DAR example):

A demo — in practice it runs on your design docs, across the three tiers (service-design Review · dev-design DAR · Code Audit) the same way. Only Code Audit keeps the code off the server — your AI agent audits it locally.

Privacy — content-free

The design coach runs content-free — our server doesn't see what you're building or what you wrote. Exactly what lives where:

Trial · pricing FAQ

Troubleshooting

Still stuck? — server-health (self-diagnosis: server reachability·source version·auth status + per-tool recovery) and manual (detailed install·auth·troubleshooting) tell you the recovery path directly.