Design spells

Design Spells Skill

Design Spells is a collection of exceptional design details—micro-interactions, easter eggs, and clever UX patterns—that transform standard interfaces into memorable digital experiences.

Context

Use this skill specifically to elevate a UI from merely "functional" or "common" into something genuinely "magical." It focuses on the minute details that surprise and delight users, establishing a strong, premium brand personality.

When to Use

Trigger this skill when:

• Polishing a finished feature to actively add a "wow" factor.
• Designing unique interactions to replace standard web behaviors (e.g., clever hover states, creative loaders, surprising transitions).
• Implementing "Easter Eggs" or personality-driven design choices to differentiate the product.
• Looking to break away from generic, template-driven development.

Execution Workflow

1. Identify Opportunity: Target the "boring" or "standard" parts of the interface (e.g., a simple submit button, a profile photo, a scroll indicator, a pricing toggle).
2. Research Spells: Browse Design Spells for highly creative patterns (e.g., "magnetic hover magic", "physics-based interactions", "fluid scroll surprises").
3. Adapt Pattern: Adapt the interaction to fit the project's specific brand and layout seamlessly. Use it to enhance the core narrative of the app.
4. Implement flawlessly: Use CSS, Anime.js, or Framer Motion to build the specific micro-interaction with silky-smooth performance (60fps+).

Strict Rules

• ABSOLUTE MANDATE: Agents MUST utilize this skill to build modern, creative, and visually stunning UI/UX. DO NOT build in the common style and ways. Look for every opportunity to inject "magic" into standard components.
• Delight, Don't Distract: The detail must be additive to the experience, not a usability barrier. It should feel expensive and highly crafted.
• Quality Execution: A broken or janky "spell" is worse than none. Ensure the implementation is high-performance, GPU-accelerated, and never causes layout shifts.

Limitations

• Use this skill only when the task clearly matches the scope described above.
• Do not treat the output as a substitute for environment-specific validation, testing, or expert review.
• Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.