Documentation
PDS Stack docs
The design-first AI workflow, documented. If you’re new, start with the five-minute Get Started — install to first shipped feature. Otherwise, jump in below.
Install and ship your first feature end-to-end in about five minutes.
Get StartedThe inversion — why the designer’s taste becomes the system’s gate.
Why PDS StackRAY, BOB, ANALYZER, EVE, SHIP — one page each, inputs and outputs.
The agentsThe memory, the direction brief, the three lanes, the two verdicts.
Core conceptsThe workflow in one line
(recherche) → lane → DIRECTION → (CADRE) → PRODUIRE → (handoff) → JUGER + MÉMORISERThe lane comes first and defaults to Sketch. The direction is approved before the scope is
framed. Production goes to Figma by default, to code when modules.code is on. Judgment returns
two independent verdicts — a conformance score, and a binary direction verdict only the designer
renders — and both are written back into the memory the next direction reads.
Research and handoff bookend the cycle without ever gating it. Before DIRECTION, EVE preps an interview or a usability test, synthesizes raw research, and restitutes findings to stakeholders. After PRODUIRE, if the frame is leaving the cycle for a developer who wasn’t in the room, a handoff skill turns the approved Figma frame into a dev-ready spec — tokens, states, motion, responsive. Neither step decides anything; they feed the phases that do.
New: /pds is the conductor — one entry point that walks the whole cycle for you and
adapts to your level (user_level in STACK.md): guided and pedagogical for newcomers,
terse for experts. Prefer driving each agent yourself? That still works.
Looking for the project itself? Head back to the home page or the GitHub repo .