ui-ux-excellence

Design, audit, and refactor frontend UI surfaces with token discipline and accessibility standards.

1|Updated May 8, 2026
One-click install
npx skills add https://github.com/dicarsmtz/product-engineering-kit --skill ui-ux-excellence-dicarsmtz
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ui-ux-excellence
Source: https://github.com/dicarsmtz/product-engineering-kit/tree/main/plugins/product-engineering/skills/ui-ux-excellence
Command: npx skills add https://github.com/dicarsmtz/product-engineering-kit --skill ui-ux-excellence-dicarsmtz

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Frontend work often ships with hardcoded colors, inconsistent components, verbose copy, missing focus states, and unverified layouts. This Skill enforces a repeatable bar for building, auditing, and polishing user-facing surfaces so UI changes stay token-driven, accessible, and consistent with the project's design contract. ## Core Features & Use Cases - Design audits and redesigns: Run a structured audit covering tokens, components, copy, inputs, accessibility, naming, and states, then produce a punch list before editing. - Token and component discipline: Enforce a three-file token contract (code tokens, CSS variables, design docs) and reusable primitives for cards, buttons, badges, forms, and empty/loading/error states. - Editorial and input standards: Apply concise copy rewrites, floating-label input rules, and i18n sync across every supported language. - Use Case: Ask the agent to redesign a settings page; it reads the project's design foundations and AGENTS.md, audits existing tokens and components, implements the changes with floating labels and double-ring focus states, then runs lint, typecheck, tests, build, and a browser pass at mobile and desktop widths. ## Quick Start Use the ui-ux-excellence skill to audit and polish this dashboard page with token-driven styling, accessible focus states, and concise copy.

Frequently Asked Questions about ui-ux-excellence

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I audit a frontend page before redesigning it?

Run the redesign audit covering tokens, components, copy, inputs, accessibility, naming, states, and dependencies. Report the findings as a punch list with a proposed direction, then proceed with edits once the direction is accepted.

How should design tokens be structured in a frontend project?

Keep tokens in three synchronized places: exported constants in code, CSS variables or theme files for runtime styling, and human-readable design documentation. When a token changes, update all three in the same change.

Does this work with Material UI or shadcn projects?

Yes. For Material UI, override every customer-facing component in the theme and disable Paper's default background image. For shadcn, Radix, or other kits, map kit primitives to the project token contract rather than shipping the starter theme.

What verification is required after making UI changes?

Run the project's lint, typecheck, test, and build gates, then do a browser pass covering the golden path, mobile at 600px or less, desktop at 1200px or more, both themes if present, all touched languages, and keyboard focus navigation.

When should placeholders be used in form inputs?

Use floating labels as the primary identifier and reserve placeholders for format hints or examples like MM/DD/YYYY. Never use a placeholder as the only label, and replace helper text with error text when validation fails.