JsonUI
← ToolsAgents for Claude / CodexNine agents + eleven skills + five rules that teach Claude Code (and Codex) how to run the spec-first JsonUI workflow. Install once, and every project it is installed into gets the whole pipeline — from 'write a spec' to 'run the tests' — without the operator having to explain it each time. Since 2026-05 the agents also know the DTO + Domain data-model layer: conductor inspects API state at startup, define understands `x-jui-skip-domain` and `api.schemas.skip_domain`, implement applies the DTO-vs-Domain return-type rule, debug traces swagger → DTO → Domain → Repository → VM. See /concepts/data-models-from-openapi.~10 min read
What shipsThe Claude Code install writes everything under the project's .claude/: .claude/agents/jsonui-*.md (nine agents, each with its own system prompt + tool allow-list), .claude/skills/<name>/SKILL.md with its examples/ (eleven skills the agents invoke for specific sub-tasks like localization, data-flow authoring, test runner setup), .claude/jsonui-rules/*.md (five invariants every agent is expected to honor), .claude/jsonui-workflow.md (the workflow menu and routing table), .claude/commands/jsonui.md (the /jsonui command), and a SessionStart hook merged into .claude/settings.json that makes the menu the default entry point. Your CLAUDE.md is never created or touched. The Codex pack installs the same content as AGENTS.md, .codex/config.toml, agents/*.toml, skills/ and rules/.
The conductor flowYou never invoke the specialist agents (define / implement / test / debug) directly. In Claude Code, a SessionStart hook the installer merges into `.claude/settings.json` puts `.claude/jsonui-workflow.md` into every new session, so Claude opens by asking one question — what workflow are you here for (New work / Modify / Investigate / Backend) — and `/jsonui` asks it again mid-session. Choices 1–3 launch the jsonui-conductor agent. The conductor inspects the repo through the MCP server (57 typed tools, including `list_api_specs` so it knows whether the project consumes OpenAPI), asks one or two clarifying questions, and hands off to exactly the right specialist with the right context already loaded. In Codex the entry is `Read AGENTS.md` (with multi_agent enabled), and the conductor is `/agent conductor`. Everything flows through that single entry point.
conductor handshake
(new session — the SessionStart hook loads .claude/jsonui-workflow.md;
/jsonui shows the same menu at any time. Codex: "Read AGENTS.md")
Claude> Which workflow?
1. New work
2. Modify existing
3. Investigate
4. Backend
Select 1–4.
You> 1
Claude> [launches jsonui-conductor]
conductor> inspects repo via MCP, asks 1–2 questions,
then routes to jsonui-define / implement / test / debug.
Agent catalogNine agents in total — one conductor + eight specialists. Three of those specialists are the navigation writers (iOS / Android / web), which keeps platform-specific router code isolated from the spec and layout authors.
jsonui-conductorROUTER
Entry point. Inspects the repo through MCP, asks 1–2 questions, routes to the right specialist.
jsonui-defineAUTHOR
Authors or edits screen / component specs. Validates via doc_validate_spec + jui_verify. Also closes contract coverage (Task 6): drafts rows for the statuses `contracts coverage` reports uncovered, from the spec, OpenAPI and mocks only, and writes the ones you accept.
jsonui-groundBOOTSTRAP
One-time per project: runs jui init, scaffolds platform folders, sets up the test runner CLI.
jsonui-implementBUILDER
Implements a screen from a validated spec. Generates Layout / ViewModel base, then authors the hand-edited halves.
jsonui-testTESTER
Authors screen and flow tests (`tests/**/*.test.json`), generates branch tests from a spec's branchContracts, and writes test documentation. Validates through the test_validate MCP tool.
jsonui-debugINVESTIGATOR
Read-only: diagnoses a bug from the spec down. Never writes files. Produces a structured report + routing recommendation.
jsonui-navigation-iosPLATFORM
Writes iOS NavigationStack / UIKit UINavigationController glue from a spec's userActions + transitions.
jsonui-navigation-androidPLATFORM
Writes Jetpack Compose Navigation or XML NavGraph + Fragment glue. Kotlin-specific.
jsonui-navigation-webPLATFORM
Writes React Router or Next.js App Router glue. TypeScript-specific.
Adding your ownDrop a Markdown file into .claude/agents/your-agent.md with a frontmatter block declaring its name, description, and allowed tools — the same shape the shipped nine agents use. Add a route for it to .claude/jsonui-workflow.md, or tell the conductor when to hand off to it — routing lives there, not in CLAUDE.md. Your agent can call the MCP server just like the built-ins; authoring one is not a special privilege, just a discipline about where its triggering responsibilities live.
Keep reading
jsonui-cliThe jui orchestrator and per-platform builders the agents invoke./tools/cli
jsonui-mcp-server57 typed MCP tools — the API surface every agent uses to inspect the repo, including the Group E discovery tools and the Group F test tools./tools/mcp