gstack-design-review

To run a visual QA audit, trigger the Skill to detect spacing, hierarchy, and alignment issues in your live UI, then let it apply targeted source code fixes. It commits each logical fix atomically and verifies the visual improvements with before/after screenshots.

Yes, you can use the plan-mode design review variant to get pre-implementation feedback on layouts. Triggering the /plan-design-review command allows you to find visual problems early and audit designs before you actually build them.

The best way to fix AI slop and visual regressions is through an iterative visual audit that applies source code fixes for spacing and polish. Each correction is committed atomically and re-verified with before/after screenshots to prevent regressions.

Screenshot verification works by capturing before and after states of your UI during the visual QA process. After detecting layout consistency issues and applying source code fixes, it re-visualizes the page to confirm the design improvements hold.

No, you do not need to commit code manually during the design audit workflow. The Skill automatically commits each logical visual fix atomically as it iterates through the source code corrections and verifies them with screenshots.

A design audit catches specific visual problems like layout spacing errors, typographic hierarchy issues, alignment inconsistencies, and general AI slop patterns. It finds these UI polish issues and directly applies code fixes to correct them.