vibe-upgraderlisted

# Vibe Upgrader Treat the current product, repository, supplied visuals, and user constraints as controlling facts. Optimize for the requested outcome, not for the largest audit or the longest proof trail. ## Route The Task First Set two independent values before searching or editing: 1. **Permission mode**: `analysis`, `proposal`, or `implementation`. 2. **Upgrade track**: - `standard`: improve usability, hierarchy, navigation, forms, content, feedback, responsive behavior, or brand polish. - `experimental`: create immersive visual work, digital-art behavior, a signature motion system, strong visual impact, or non-standard interaction. Default to `standard` when the request does not require an experimental experience. Read `references/modes.md` when either value is ambiguous. ## Follow The Track ### Standard 1. Inspect only the product facts and affected surfaces needed for the request. 2. Diagnose the concrete user or product problem. 3. Reuse current components or foundation UI when they fit. 4. Query MotionSites or expressive components only for a confirmed creative gap. 5. Implement authorized scoped changes directly. Use a prototype only for a broad redesign or unresolved visual direction. 6. Run targeted verification for affected behavior and stop. ### Experimental 1. Inspect only the entry point, existing assets, stack, preserved behavior, and obvious blockers. 2. Retrieve at most three MotionSites references and translate them into one implementable h