build

name	build
description	Build or redesign production-quality LoveUI pages, dashboards, product surfaces, and app workflows with a clear visual direction.
user-invokable	true

Use this skill when the user asks to create, redesign, or substantially improve a UI.

Load

• references/design-system.md
• references/structure-architecture.md
• references/interaction-states.md
• references/implementation-quality.md
• Add references/content-accessibility.md when the work includes copy, forms, accessibility, onboarding, or public-facing content.

Process

1. Inspect the existing app before designing.
2. State product type, audience, core jobs, and constraints.
3. Choose one visual direction that fits the domain.
4. Select a blueprint and LoveUI registry candidates when relevant.
5. Build foundations first: tokens, layout rhythm, responsive constraints.
6. Compose reusable UI with semantic structure and complete states.
7. Verify mobile and desktop, then fix visible rough edges.

Direction Rules

• Make one domain-specific visual choice people can remember.
• Avoid generic AI aesthetics: purple/blue gradients, glowing dark panels, glassmorphism everywhere, gradient headings, identical icon-card grids, and decorative blobs.
• Operational tools should be calm, dense, and scannable.
• Consumer, game, editorial, or creative tools can be more expressive, but still need clarity and state completeness.
• Do not make a landing page when the user asked for an app or tool; build the usable product surface first.

Expected Result

The final UI should feel coherent, responsive, accessible, and production-ready. It should include the core workflow, not only a static happy path.