JADO — Just Another Design Orchestrator
The design process: research, positioning, experience, code prototypes and design systems.
- Status
- Observed
- Last reviewed
- 2026-10-10
JADO brings together the operating method, Mermaid maps, skills and agent profiles for Claude Code, Codex and OpenCode in the same repository. The JSON graph is the source for routing and generated maps; the Fumadocs playbook preserves the process.
This playbook describes a designer’s working method: understand the problem, study alternatives, design and test the experience, organize the design system in code and share decisions with the team.
Code is a design tool: it makes it possible to try realistic interactions, test a prototype with users and contribute components and stories through PRs. The development team independently chooses architecture, tools, skills, task organization and the release process.
For an assignment, use jado-run and consult the JADO router. To read about the design cycle, use the workflow map or the stages below.
Loading diagram…
Mermaid source
flowchart TD
A[Problem and research] --> B[Competitors and positioning]
B --> C[Stories, journeys and flows]
C --> D[Alternatives and code prototype]
D --> E[User testing]
E --> F{What did we learn?}
F -->|Needs revision| C
F -->|Supported direction| G[Design system and Storybook]
G --> H[Handoff and contribution through PR]
H --> I[Feedback and new questions]
I --> A| Stage | Question | Outcome |
|---|---|---|
| Initial analysis | What need and context? | Brief, evidence and hypotheses |
| Competitors and references | How is the same problem addressed? | Reasoned comparison and opportunities |
| Positioning and copy | Who are we speaking to and what value do we promise? | Marketing context and messages to validate |
| Definition | What experience do we want to explore? | Scope and observable criteria |
| Experience design | What paths, states and outcomes are needed? | Stories, journeys, flows and scenarios |
| Code prototype | What interaction do we need people to try? | Prototype with declared limitations |
| User testing | What works and what needs revision? | Observations, decisions and another iteration |
| Design system | Which choices are reusable? | Tokens, components and stories |
| Handoff | What does the team need to understand and evaluate? | Evidence, experience specifications and scoped PRs |
How to read evidence
Observed indicates a practice stated or verified in the sources. Proposed indicates an operating procedure to adapt together. Unresolved indicates an open decision. The research procedures proposed here do not attest to interviews or tests already conducted.
See roles and boundaries and sources.