Website UX Orchestrator

What it does

Selects, sequences and coordinates the smallest useful set of UX micro-features across the T7 library.

When to use it

Use when planning a build and deciding which of the many focused UX skills are actually needed, and in what order.

Problems it prevents

Stops a project either missing an obviously needed UX pattern or bolting on features nobody asked for.

Typical workflow

1. Start from real project context
2. Route each need to the right specialist skill
3. Sequence the build order
4. Run the combined validation pass

Example output

A short list of the specific focused skills a project actually needs, in build order, with the rest deliberately skipped.

What's included

1. 01
   The complete prompt

   The full manual as a ready-to-save SKILL.md file, matched exactly to what ships in the T7 library.

2. 02
   Install walkthrough

   Personal (~/.claude/skills/) and project (.claude/skills/) folder instructions, whichever fits how you work.

3. 03
   Use notes

   How Claude invokes it, what a good result looks like, and what to check before you trust the output.

Works well with

• SystemProject Planner

  Turns a loose client brief into routes, features, content needs, dependencies, risks and acceptance checks.

• SystemLaunch Readiness

  Classifies and verifies what customers, search engines and operators actually need before a production launch.

• SystemDesign System Governance

  Governs a reusable design system: token and component ownership, versioning, accessibility contracts, adoption.