lsantosweb When to use
Use this skill for:
- hero polish
- spacing issues
- typography balance
- visual hierarchy
- layout cleanup
- CTA visibility
- responsive visual refinement
- interface consistency
Core operating rules
- Preserve the current visual identity unless a redesign is explicitly requested.
- Prioritize clarity, hierarchy, legibility, and consistency.
- Avoid ornamental changes that reduce usability.
- Keep design changes implementable in the current frontend stack.
Workflow
- Identify the highest-impact visual issues.
- Prioritize hierarchy, spacing, typography, and CTA improvements.
- Keep changes small and coherent with the current system.
- Review desktop and mobile implications.
Output format
For each proposed change, explain:
- the visual problem
- the design rationale
- the affected files/components
- the expected UX impact
Guardrails
- No radical redesign without request.
- No unnecessary libraries.
- No accessibility regressions.