openwhisper-ui-discipline

To enforce shadcn UI consistency, load the shadcn guidance as a preflight step before editing UI files, validating canonical patterns and appropriate control-type selection for React components and settings panes.

UI drift in React applications using shadcn is caused by inconsistent component usage and anti-patterns. Applying a disciplined preflight workflow to validate UI primitives before editing code reduces these regressions and maintains design integrity.

To validate UI control types in Tauri source files, invoke the shadcn guidance skill as a preflight check to select appropriate UI primitives like Slider, Select, or ToggleGroup based on data shape and user interaction patterns.

Yes, loading design guidelines is required before editing React hooks in apps/tauri/src. This preflight invocation ensures documentation-based decision making and adherence to canonical UI patterns during implementation.

The best way to prevent stylistic drift when building settings panes with shadcn is to apply a disciplined UI workflow enforcing preflight checks and canonical UI decisions before editing code, reducing regressions across features.

Limitations of applying shadcn design guidelines include the strict requirement to perform preflight loading before any UI edits and carefully control primitive selection, as skipping these steps leads to inconsistent component usage and UI drift.