Core loop
Creative-engineering protocol
The Understand→Ship loop agents follow for brand-bound creative work with visual proof gates.
Pax replaces vague "make it beautiful" prompts with a versioned protocol every supported agent adapter implements from the same canonical source.
Loop
Understand → Direct → Design → Build → Render → Critique → Repair → Ship| Stage | You prove |
|---|---|
| Understand | Brand scan and repository context |
| Direct | Creative thesis, composition, typography, motion rationale |
| Design | Registry selections bound to tokens |
| Build | Implementation with reduced-motion paths |
| Render | Captures at mobile, tablet, desktop |
| Critique | .pax/reports/check.json |
| Repair | Targeted fixes mapped to finding ids (max 3 passes) |
| Ship | Handoff with rationale and reproduction commands |
Install
paxfx protocol info
paxfx protocol install
paxfx protocol parityGenerated adapters live in the Pax repository under packages/adapters/generated/. Parity checks ensure they cannot drift from docs/protocol/creative-engineering.v1.json without failing CI.
Checkpoints
Resume from .pax/protocol/run.json after any completed stage. Do not replay the full chat.
Skill
Use pax-protocol as the orchestrator; medium skills (pax-brand, pax-blocks, pax-qa, etc.) cover stage tooling.
Schemas
Related
Was this page helpful?
Answers are not recorded or transmitted. Pax has no telemetry.