redesignlisted

# Stage 6P-R: Frontend Design Elevation (Interactive Redesign) Unlike the standard Stage 6P (visual polish — which fixes defects within an existing design system), this stage performs a FULL design elevation: collecting project context interactively, studying reference products, extracting Figma design tokens, making deliberate design decisions with the user, and implementing a cohesive visual overhaul. Read the detailed guide at `${CLAUDE_SKILL_ROOT}/references/redesign-detailed-guide.md` for full phases, anti-slop patterns, component matrices, review procedures, and report templates. ## When to Use This vs. Standard 6P | Scenario | Use | |---|---| | App looks functional but needs contrast fixes, hover states, spacing consistency | Standard 6P (polish skill) | | App looks like generic AI-generated SaaS and needs a distinctive visual identity | **This skill** (redesign) | | Rebranding or major design direction change | **This skill** | | First-time design system establishment | **This skill** | | Post-launch design refresh based on user feedback | **This skill** | ## Pipeline Position **Stage 6P-R** occupies the same pipeline slot as 6P (after all Stage 6 quality passes, before Stage 7 deployment). It is an ALTERNATIVE to standard 6P, not an addition. Run one or the other, not both. If 6P has already been run and you want to switch to 6P-R, revert 6P changes first (`git revert` the 6P commit). **Mutual Exclusion with 6P**: 6P and 6P-R are mutually exclusive. To switch