rudder-ui-polish-maintainer

To fix Rudder UI alignment and density issues from a screenshot, the skill converts specific visual complaints into a scoped, committed front-end change. It applies narrow fixes to spacing, overflow, and layout without triggering broad redesign work.

Screenshot-driven UI polish is the process of turning visual complaints into implemented frontend fixes. This approach handles narrow visual and interaction issues like hover affordances, badges, labels, and empty states by applying minimal coherent changes.

Yes, you can use this workflow to remove redundant routes and fix onboarding states in Rudder. It scopes changes to narrow UI behavior fixes including route removals, empty states, and menu adjustments while ensuring intent classification and contract alignment.

You verify visual verification for small UI behavior fixes by running the narrowest meaningful checks and validating the rendered outcome. When visual proof is blocked, the process ensures clear reporting rather than committing unverified changes.

The limitation of using scoped front-end changes for layout density is that it only applies to small-to-medium UI behavior fixes. It is not intended for broad redesign work and will route advice-only or explain-only prompts away from implementation.