ux-compiler

name	ux-compiler
description	Compile raw product or UI intent into a User Journey Intelligence Brief and Codex Implementation Brief before code. Supports Claude-orchestrated and Codex solo mode with a required critique pass.
layer	orchestrator
category	workflow
triggers	["/ux-compile","/codex-brief","ux compile","user journey intelligence","codex solo compiler","make codex smarter","before UI implementation","journey brief","implementation brief","founder intent","raw product idea","UI product flow","product flow","ui rework","rework UI","rework this UI","ui redesign","redesign UI","rework screen","redesign screen","follow Design.md","follow design.md","docs path","source relevance"]
linksTo	["ultra-ui","uncodixfy","ui-polish","design-kit","goal","handoff"]

UX Compiler

Use this skill before UI, product-flow, onboarding, settings, dashboard, checkout, editor, admin, or workflow-screen implementation.

UltraThink's core contract:

• Claude is the preferred product strategist and journey interpreter when available.
• Codex is the implementation executor.
• UltraThink is the context compiler between them.
• When Claude is unavailable, Codex must run the same compiler loop itself before coding.

Required Flow

1. Restate intent without code. Convert the user's raw request into product intent, target user, workflow, and business goal.

2. Classify referenced docs before using them. If the user says "follow DESIGN.md", "use design guidelines", or points at docs paths, classify each source before it affects the brief:

   • product/page brief: may shape audience, copy, content hierarchy, and journey
   • brand/design system: tokens/components only unless page-specific
   • architecture/codebase docs: implementation constraints only
   • generic guideline/reference: QA/process only
   • stale/irrelevant: ignore and state why

3. Produce the User Journey Intelligence Brief. Follow docs/protocols/ux-compile.md exactly enough to capture user identity, situation, job-to-be-done, journey steps, UX priorities, screen responsibility, and component mapping.

4. Critique the brief. Check for missing:

   • user type or skill level
   • emotional state or fear
   • entry point or trigger
   • trust requirement
   • empty/loading/error/success/recovery states
   • unclear primary action
   • acceptance criteria that only describe DOM output
   • docs or architecture language accidentally treated as product/page intent

5. For UI work, run the Uncodixfy start gate. Before component mapping or code, name the default Codex UI moves the task tempts you to make, ban them, and replace them with normal product patterns from existing tokens/components.

6. Produce the Codex Implementation Brief. Turn the approved journey into files to inspect, files to edit, components, state/API requirements, visual/interaction requirements, acceptance criteria, and no-go constraints.

7. Create or update a Markdown task ledger. Use docs/protocols/task-ledger.md; update checkboxes as each implementation slice lands.

8. Explore with VFS first. Use VFS/code-intel before broad source reads when available.

9. Implement in narrow slices. Preserve the journey contract. Do not replace intent with generic CRUD.

10. Verify and review backward from the journey. Tests are required where risk warrants, but final review must also check the user path, states, trust, and recovery behavior.

Codex Solo Rule

If Codex is working without Claude orchestration, the brief and critique are mandatory visible artifacts. Codex may skip the full journey brief only for tiny mechanical UI fixes, and must state why the task is mechanical.

Output Artifacts

For substantial work, keep the artifacts in the task ledger or a nearby scratch doc:

# User Journey Intelligence Brief
...

# Source Relevance Gate
...

# Brief Critique
...

# Codex Implementation Brief
...

References

• Protocol: docs/protocols/ux-compile.md
• Task ledgers: docs/protocols/task-ledger.md
• Runtime contract: docs/architecture/runtime-provider-contract.md
• Ultra UI pipeline: docs/design/ultra-ui-human-pipeline.md