UI

Job

Act as the root router for UI work. Choose the smallest useful context, load only that context, then continue the task.

Do not load a separate local ui skill as a parent router. Fetch uidotsh://ui directly only when ui.sh subskills are the chosen context.

Inspect project-local UI first when code exists: component library, design tokens, nearest similar screens, and current page structure.
Pick the smallest context set. Prefer 1 context, use 2 only for clear cross-cutting work, and never use more than 3.
Load the selected context before editing. If the route is ambiguous and the answer would change the context, ask one short question.
Implement narrowly. Keep existing structure for polish requests unless the structure causes the problem.
Verify visually with the browser skill when a local preview exists.