Vuesax
Teach your agent the catalog
How the three catalogs are organised, which tool to call in what order, where every file belongs once it lands, and how theming and effects are wired.
- MCP connection and auth
- The 13 tools and what each costs
- Discovery flow: search → docs → source
- +2
Motion signature
Make new things feel like Vuesax
The three moves that carry the whole feel — panels that grow out of the control that opened them, the cursor-proximity light, and the press ripple — with the real curves, durations and rules behind them.
- The morph engine and its five rules
- Curve vocabulary: which bezier, when
- Proximity glow, wiring and radii
- +3
House rules
Keep the codebase consistent
The conventions that keep pasted components looking like one system: token-only colors, the shared prop vocabulary, extending instead of forking, motion and accessibility rules.
- Reuse before building new UI
- Zero hardcoded colors, both themes
- The shared prop vocabulary
- +3
Reference wallpapers
Create original desktop backgrounds
Generate faithful-but-original 16:9 wallpapers from visual references, remove every trace of text or branding, and save optimized numbered WebP assets in public/bg/.
- 80/20 reference-based variation
- Text and watermark rejection
- 16:9 desktop composition
- +2
Frontend practices
Write code that survives
Comments that earn their place, component and state design, lazy loading and code splitting, images, fonts, rendering and runtime performance, accessibility, frontend security, and what is actually worth testing — each rule with its reason and its exception.
- What to comment and what not to
- Component, prop and state design
- Lazy loading, splitting, Core Web Vitals
- +4
Save the file where your editor reads instructions — each skill lists the path.
Restart it once. Instruction files load at startup, not per message.
Forget about it. The assistant applies it on its own — you never invoke it.