Skip to content
cccskills
FreePublished on GitHub

design-spells

Use when adding curated micro-interactions, delightful animations, and subtle design details that add magic and personality to web and mobile apps.

The English summary is being prepared. Showing the original description.

See how to install

Files included (1)

  • SKILL.md3.9 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

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.

Overview

Focuses on micro-interactions and motion design that elevate the user experience through subtle feedback and delight.

Core Process

  1. Identify the trigger and intent of the micro-interaction.
  2. Apply the animation using approved motion curves.
  3. Verify performance to ensure 60fps execution.
  4. Ensure the animation respects prefers-reduced-motion.

Common Rationalizations

RationalizationReality
I'll skip the animation, it's too subtle to matter.Micro-interactions are what separate good apps from great ones; they provide critical feedback.
A simple hover color change is enough.Missing the opportunity to guide the user's focus and provide satisfying tactile feedback.
I don't need to consider accessibility for this visual effect.Animations must respect 'prefers-reduced-motion' to avoid causing user distress.

Red Flags

  • Adding animations that do not respect reduced-motion settings.
  • Overusing complex animations that distract from the main user goal.
  • Implementing micro-interactions without verifying performance (jank).

Verification

  • Animations check for prefers-reduced-motion.
  • Frame rates remain stable during the micro-interaction.
  • The interaction enhances feedback rather than just being decorative.

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

Use when manage multiple local CLI agents via tmux sessions (start/stop/monitor/assign) with cron-friendly scheduling.

The English summary is being prepared. Showing the original description.

hybridlabor-api/aos6Updated Oct 16, 2026

Use when a hybrid memory system that provides persistent, searchable knowledge management for AI agents (Architecture, Patterns, Decisions).

The English summary is being prepared. Showing the original description.

hybridlabor-api/aos6Updated Oct 16, 2026

Reference for how BDB structures autonomous software engineering work — the seven-node dispatcher graph (Architect, TechLead, UI/UX, Engineering, Media/EventTech, Reviewer, Shipping) that /startcycle-graph actually runs. Use when you need the high-level lifecycle framing without inventing your own process.

The English summary is being prepared. Showing the original description.

hybridlabor-api/aos6Updated Oct 16, 2026

Tools are how AI agents interact with the world. A well-designed tool is the difference between an agent that works and one that hallucinates, fails silently, or costs 10x more tokens than necessary. This skill covers tool design from schema to error handling.

The English summary is being prepared. Showing the original description.

hybridlabor-api/aos6Updated Oct 16, 2026

Harness patterns for coding agents — memory, permissions, context engineering, delegation, skills, hooks, bootstrap.

The English summary is being prepared. Showing the original description.

hybridlabor-api/aos6Updated Oct 16, 2026

agenttrail: live map of a multi-agent build in the browser: which plan component is being worked on, by which agent or harness, what is done and what is stuck. Use when a multi-agent pipeline starts (/startcycle, /startcycle-graph, /teamwork-preview) or after a plan-canvas approve, when the user asks to see what the agents are doing ("live map", "build board", "who is running now"), or by yourself whenever a multi-agent run is under way — no user prompt needed.

The English summary is being prepared. Showing the original description.

hybridlabor-api/aos6Updated Oct 16, 2026

See all skills by hybridlabor-api

Report a problem with this skill