ux-ui ยท diff
git:20260920.ac44dda to git:20261022.08bdce3
10 added, 6 removed. Audit A to A.
What this update changes in the checks
No check changed: every fixed check gives the same answer before and after this update.
A tripped check is a label, not a verdict: read the matched text and the lines below. This week's updates that newly trip a check.
---
name: ux-ui
- description: Use when creating or changing a user-facing interface. Applies the project's theme ownership and browser accessibility-test contracts.
+ description: Use when creating or changing a user-facing interface. Applies the project's styling, component placement, theme, icon, and accessibility-test conventions.
---
# UX/UI
- - Style components with Tailwind utilities. Share repeated UI through components and variants, not CSS class bundles. Use custom CSS for generated content, document-level rules, or complex effects where utilities would obscure the implementation.
- - Reuse existing components. Keep feature-specific UI within its feature, components shared across features in `src/shared/ui`, and components shared across apps in `packages/ui`. Extract shared components when their consumers should share behavior and styling.
- - Shared visual values live in each application's established theme. Components consume semantic tokens instead of raw palette values; author theme colors in `oklch(...)`.
- - Prefer Lucide React (`lucide-react`) for icons in React interfaces.
- - Browser-rendered apps use Playwright and `@davidvornholt/a11y-testing` for automated accessibility checks. Add or update coverage for routes and meaningful interaction states affected by the change.
+ Style with Tailwind utilities in the markup. When UI repeats, share it as a component with variants rather than an `@apply` class. Custom CSS is fine where utilities would obscure the intent.
+
+ Shared UI goes in `src/shared/ui` within an app and in `packages/ui` across apps.
+
+ Components use the app theme's semantic tokens rather than raw palette values. Author theme colors in `oklch(...)`.
+
+ Use Lucide (`lucide-react`) for icons in React interfaces.
+
+ Browser-rendered apps check accessibility with Playwright and `@davidvornholt/a11y-testing`, which provides the axe scanner and the shared Playwright configuration. Each app lists the routes and UI states it scans in `a11y/*.a11y.ts`. When a change adds or alters a route or a meaningful UI state, update its coverage there.