domains / families / software-engineering / build-ui

build-ui

authentic

Step-by-step workflow for UI work: read the project, follow the plan for the job (new screen, dashboard, polish, simplify, review), then render, fix and check again.

When to use

• Use when asked to build a new screen, page, feature or app UI.
• Use when building a dashboard, admin or data-heavy view.
• Use when asked to polish, simplify or review an existing interface ("make this UI better").
• Use when UI work should end with a checked, rendered result rather than code alone.

When not to use

• Needs a way to render the UI (browser, simulator or preview) for the final check; without one it says what it could not verify.
• Follows the project's existing design system; it does not invent a new visual style unless a redesign is asked for.
• Real app and website references need the optional UXKIN MCP tools and a UXKIN plan; the workflow runs without them.

Skill page

Source