UI Router

Shared UI routing plugin for Codex and Claude Code.

It preserves the original named skill universe—including Taste, Hallmark, Interface Design, Impeccable, Emil, Jakub, Meng, Addy, ibelick, shadcn, systems extraction, image-to-code, writing, and marketing skills—while keeping two truths separate:

1. the canonical researched chain;
2. the chain actually available in the current host environment.

The plugin contributes:

• /ui-router:route-ui-work, an auto-invocable UI routing skill;
• /ui-router:route-3d-work, an auto-invocable real-time 3D routing skill (1.19.0);
• /ui-router:install-ui-stack, a manual, plan-first optional installer;
• read-only scout and critic agents plus one sole-writer UI builder;
• the complete routing catalog and quality references;
• the two polished UI reference cards;
• a one-editor writing route that hands product or brand constraints to Natural Writing for the final prose pass;
• a PreToolUse hook that blocks sudo.

Model reviews include Arena's relevant WebDev/design categories and Work Router's regular benchmark sources. Within Codex, typical substantial new UI work starts with Sol 6.1, with Astra for exceptionally difficult unresolved quality-first direction. The October 2 update starts Claude UI implementation at Opus 5.5 medium and consequential review at high, after checking actual provider alias resolution. When host choice is open, current WebDev evidence supports a quality-focused Opus 5.5 route; its Max-only result does not settle medium/high performance or native completion time. Read the release assessment. Preserve concrete reference direction, rendered comparison and interaction checks.

The router does not silently install third-party skills. The bundled installer refuses root and sudo, prints sources and commands before execution, and installs only explicit skills or curated profiles.

Claude Code's official frontend-design plugin is a strong installed fallback, but it does not erase the canonical named lead when Taste, Hallmark, or Interface Design is the researched fit.

For copy, the router does not stack humanizers. It selects one product/UX or marketing semantics owner only when needed, then uses the companion natural-writing plugin as the sole final editor. Verify that companion separately; package presence is not installation evidence. If it is unavailable, select exactly one documented fallback.

Animated explainers and authored video

The motion-explainer route selects creative direction separately from rendering and narration. It uses the supplied reference, plans visual changes and scene continuity, and checks a short moving proof before a full film. Official HyperFrames creative/animation skills, video-shotcraft with Remotion, and an existing custom pipeline are conditional routes. Recorded walkthroughs and ordinary UI interactions keep their own workflows. See the source review for evidence and limits.

Inspiration sources and visual resources

The resource map selects inspiration by design question. Mobbin and Refero cover product screens, styles and flows; 21st.dev adds component and section samples with selected implementation candidates. Beautiful UI, AI Elements, Agent Elements and PAIR apply when users encounter AI behavior. Motion references include Transitions.dev and the existing product, experimental and spatial sources. Inspect exposed tools and actual access before assuming a service is available or missing.

Choose one or two relevant sources, inspect the actual visual or interaction evidence, and preserve creator credit. Clear references and small edits stay direct. Neuform and Aura can generate directions, HTML prototypes and handoff material, while ThreeUI Pro can deliver entitled spatial-code source; none is a direct CMS/page-builder import guarantee. ThreeUI Community, Toolcraft, Canvas UI and HyperFrames remain implementation choices; adding the map neither installs them nor grants paid access.

For broad redesigns or unexplained usability problems, product-decision routing helps distinguish missing user evidence, unclear product objects, flow problems and surface polish. Defined visual edits stay direct. Completion checks distinguish an attractive preview from working behavior and a verified export.

The routing skill checks current host capabilities and reads this map for relevant creative, reference, or component work. Restart or reload the host after installing an update, then verify the expected skill is listed. Local source updates are not automatically published to the marketplace.

Resource recommendations distinguish free source, account-free tools, free account allowances and paid upgrades. Motion's official specialist and free documentation MCP complement the existing motion guidance; 21st's free search and limited code retrieval can be used through its supported CLI. Live tool and entitlement checks govern the available features. See the access review.

Immersive entrances and media experiences

For playback failures, compare the same source in the actual browser and page origin before making a platform-wide claim. Check player-readiness timeouts, settled pause state after seeks/returns, preview-data preservation and the loaded code revision. These are conditional media checks, not a required matrix for ordinary static edits.

A public landing page can also be the usable product. The router now distinguishes that case, preserves the route from an expressive scene into the real task, and checks sound/video controls, shared playback time, visible words and interruption/recovery when media is part of the work. Its focused question examples cover unresolved page purpose, navigation, sound entry and physical use. They do not create routine approval rounds or reopen settled preferences. See the September 20 source review.

Real-time 3D, interactive worlds and learning tasks

Since 1.19.0, route-3d-work owns playable worlds, spatial scenes, three.js/WebGL/WebXR builds, Blender-to-web pipelines and Dream Loop. It keeps the project's own pipeline as lead and maps the runtime to knowledge layers (three.js llms.txt, Meng 3D and game-development, blender-web-pipeline, 3dviz-pro-max retrieval), tools (Blender CLI and MCP, capture harnesses, a Needle Inspector trial) and exclusions. Dream Loop runs in the host you are in. Its references: specialists, fidelity loop and gate, runtime and playable slice, live AI and host delivery, spatial realism and interaction contracts. The old route-ui-work reference paths remain as redirect stubs for one release. See the source review and the October 18 three.js builder review.

Rendered-site annotation review

The annotation review procedure tracks exact routes and selected elements, exercises relevant media and controls, and keeps findings, saved fixes and deployment evidence separate. It complements the existing baseline-preservation and quality gates rather than adding another design lead. Small edits remain scoped; a site-wide review checks every requested page.

Graphical apps and visual refinement

UI Router selects and coordinates; upstream specialists supply their detailed craft. The upstream routes point to exact Meng skill entrypoints. Load the complete selected procedure and required references; install selected complete folders for repeated use within authorization. Keep shared principles in the router and preserve source/version information.

Substantial high-fidelity 3D work routes to route-3d-work, which uses Dream Loop under the fidelity execution gate. The visual build loop remains a lighter, explicitly labeled adaptation. See the execution review and the review.

Design direction without a prompting course

Design steering makes unresolved choices visible: show two or three references at the start, component samples for a prominent choice, a working slice before expansion, or a focused comparison during a meaningful iteration. Label source examples and adaptations, recommend a direction, and use comparable content and playable motion where relevant. Clear references and small edits stay direct; these are useful decision points, not routine approval gates.

Infer audience and character from each project. The user's profession and use of AI to build do not prescribe business software or an AI interface. Consumer, creative, editorial and experimental work retain their own direction; an audience label does not impose an aesthetic ceiling. Keep settled choices and selected component sources in project notes. Verify adapted components in context rather than treating a gallery demo as evidence that the finished product works.

For substantial work, make composition and type decisions concrete, refine a few variables at a time, and inspect the whole requested surface. Custom motion and spatial work use focused quality checks for input alternatives, semantic text, animation ownership, lifecycle and observed performance. These practices come from a dated repository review; they do not mandate a visual style, graphics stack or extra checks for static edits.

Art direction and skill variants

The router records the selected design lead’s provider and path, because same-named skills may apply different aesthetic rules. For expressive work, it preserves the product’s purpose separately from its old appearance and checks that the chosen palette and reference interactions appear in the result. See the focused art-direction guidance. This is not a universal ban on any palette or effect.