qualia-polish

Remove AI-generated UI patterns using deterministic grep-based checks to detect generic fonts, repetitive card grids, and blue-purple gradients, then enforce design standards for typography and color. This process cleans templated artifacts and establishes a coherent, human-crafted design system.

Enforce accessibility standards by adding semantic HTML, hover and focus states, and reduced-motion fallbacks, then run WCAG checks. This ensures the web project meets accessibility requirements and hardens interactive states for user usability and trust.

Fix scattered styles by enforcing CSS and Tailwind conventions, establishing a single source of color tokens, and applying fluid type scaling. This creates a unified visual hierarchy and removes hardcoded widths from the frontend repository.

Yes, you can use a DESIGN.md file to apply custom design standards. The polish pass reads the DESIGN.md specification when present, enforcing its rules alongside static detectors to ensure the UI meets your specific brand and responsive requirements.

Run a post-verification design pass after the verify phase to convert a verified feature release into a production-quality UI. This is when you fix layout, motion, and typography issues, transitioning the project state to polished.

Yes, the UI polish process runs TypeScript checks to harden the codebase before producing a single commit. It combines these type checks with static grep detectors to ensure the final commit marks the project as polished without breaking types.