Open-source creative engine

Give your coding agent taste.

Pax is the open-source creative engine for coding agents. It turns a brief and a brand into interfaces, motion, Lottie, and product films, then critiques and repairs the work before it ships.

Install
pnpm paxfx init

From a Pax checkout. See installation for Node, pnpm, and optional FFmpeg.

You are watching Liquid, a real Pax WebGL engine over this headline. Select an engine above. Under reduced motion, every engine holds a designed still. If WebGL fails, the headline stays readable.

Same prompt

One brief. Two outcomes.

The Phase 14 website proof used this exact brief. Without Pax, the agent improvises. With Pax, every stage leaves an artifact you can inspect.

The brief

Build a distinctive marketing page foundation with editorial hierarchy, responsive layout, meaningful CTA interaction, and token-bound code presentation. Audience: developers evaluating Pax. Emotional target: calm confidence; proof through clarity, not decoration.

Approach
Agent writes HTML, CSS, and motion from chat memory.
Brand
Ad hoc hex values. Drift from the first revision.
Direction
Implicit in the thread. No rejection list.
QA
Manual eyeball, or skipped entirely.
Outcome
Ships fast. No provenance. Critic gates fail on overflow and reduced motion.

Evidence: plans/evidence/phase-14-proofs. Human intervention on the With Pax run is labeled in the comparison doc.

The production loop

Eight steps. One discipline.

Every Pax workflow follows the same loop. Each step has an owner, a CLI entry, and structured output your agent can resume from disk.

  1. Understand

    Scan the repository and bind brand tokens before any pixels move.

    paxfx brand ingest
  2. Direct

    Generate directions with thesis, rejection criteria, and locked constraints.

    paxfx direct generate
  3. Design

    Match registry assets to intent with responsive layout and token bindings.

    paxfx design plan
  4. Build

    Compile scenes, blocks, and surfaces from structured artifacts.

    paxfx recipes run
  5. Render

    Export Lottie, dotLottie, DOM previews, and deterministic films.

    paxfx film render
  6. Critique

    Run contrast, motion, overflow, and performance gates at real viewports.

    paxfx check --rendered
  7. Repair

    Fix diagnosed findings with snapshots and bounded repair passes.

    paxfx repair
  8. Ship

    Export with manifests, reproducibility commands, and critic evidence.

    paxfx export

Canonical protocol: Creative-engineering protocol v1.0.0

Four pillars

Design. Motion. Film. Critic. One engine.

Pax is not a component catalog wearing a trench coat. It is a creative production system with four surfaces your agent can operate end to end.

Pax Design

Interfaces that read like decisions

128 registry assets, 25 canvas engines, and 9 dither charts. Semantic roles, responsive recomposition, and WebGL budgets your agent can cite by id.

Pax Motion

Motion with a declared cost

Five motion personalities, reduced-motion substitutions, and orchestration that names its price before it runs.

Pax Film

Product films from a brief

Lottie, dotLottie, and deterministic mp4 renders from one scene model. Preview and production share one compile path.

Contrast
pass
Reduced motion
pass
Overflow
pass
Mode
rendered

Pax Critic

Proof before ship

Contrast, accessibility, overflow, and performance budgets checked at mobile, tablet, and desktop. Repairs gated behind your approval.

Flagship proof

Website foundation. Built through the loop.

Phase 14 proof one: editorial hierarchy, token-bound CSS, critic pass at three viewports. This is the rendered output, not a mockup. Reproduce it with node fixtures/proofs/website/reproduce.mjs.

Open standalone proof · View fixture

CLI and agents

One CLI. 23 MCP tools. Four editors.

paxfx operates the loop on your machine. The MCP server exposes registry browse, install, validate, and export tools. 5 write or export tools are marked dangerous and gated behind approval.

terminal
pnpm paxfx init
pnpm paxfx doctor
pnpm paxfx mcp serve

Supported agents

Protocol adapters install via paxfx protocol install. Skills live in skills/.

More proof

Two more projects. Same loop, different surfaces.

Lottie interaction and product film proofs from Phase 14. Every artifact traces to a brief, command, and manifest.

Proof two

Interactive dotLottie favorite

Eight state-machine transitions tested. Deterministic compile hash. Reproduce with node fixtures/proofs/lottie/reproduce.mjs.

paxfx create interactive --recipe favorite-button

fixtures/proofs/lottie

Proof three

Cinematic product launch film

20 second mp4 from a declarative film document. Preview matches render. outputSha256 in manifest.

paxfx film render pax-product-launch.film.json

fixtures/proofs/film

Verifiable open source

Inspect everything. Reproduce everything.

MIT licensed. No account. No telemetry by default. Three Phase 14 proofs ship with external fixtures and reproduction scripts you can run on a clean machine.

reproduce-all-proofs.sh
pnpm install
pnpm exec playwright install chromium
node scripts/reproduce-phase-14-proofs.mjs

Install Pax

Give your agent the loop tonight.

One command initializes Pax in your repository: brand scan, agent instructions, MCP wiring, and a sample you can inspect. No account. No cloud.

pnpm paxfx initlocal only

Protocol and skills: creative-engineering loop, skill packs.