interaction-design · aj-geddes — Claude Code skill: microinteractions and UI
A skill for designing interactions: animations, loading and error states, feedback on touch. Useful when the interface works but feels flat.
npx skills add aj-geddes/useful-ai-prompts --skill interaction-design -a claude-codeWhat interaction-design does
The skill gives the agent a frame for interaction design: gestures, transitions, feedback after an action. It ships reference guides in the references/ directory covering animation and transition design, error handling and feedback, and accessibility in interactions. Alongside them sits a practice list: keep animations under 400ms, make interactions reversible, provide keyboard and screen reader alternatives.
The quick start covers common gestures — swipe, tap and hold, pinch and zoom, drag and drop, double tap. Each entry names where it fits, what feedback to give, and what to offer people who cannot use the gesture. It suggests starting a hold around 500ms before the trigger fires.
One limit is worth knowing up front: the skill designs, it does not test. Without keyboard and screen reader tests in your project, the accessibility advice stays on paper. That is a reason to check whether such tests exist before letting the agent rewrite your transitions.
What it helps with
- design loading and error states for a checkout form
- pick duration and easing for a screen transition
- add a keyboard alternative to a swipe gesture
- describe drag-and-drop behaviour for reorderable cards
- check whether an animation breaks users sensitive to motion
Example prompts for the agent
- Design microinteractions for a product card: tap, hold, add to favourites
- Walk through loading and error states for the payment form using the interaction-design guide
- Review my screen transitions: durations, easing, keyboard alternatives
How to install interaction-design
1Skills CLI (Vercel)
npx skills add aj-geddes/useful-ai-prompts --skill interaction-design -a claude-code2Manually: put the files in place
~/.claude/skills/interaction-design/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/interaction-design/
1Skills CLI (Vercel)
npx skills add aj-geddes/useful-ai-prompts --skill interaction-design -a codex2Manually: put the files in place
.agents/skills/interaction-design/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add aj-geddes/useful-ai-prompts --skill interaction-design -a cursor2Manually: put the files in place
.cursor/skills/interaction-design/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install aj-geddes/useful-ai-prompts interaction-design2Manually: put the files in place
.github/skills/interaction-design/SKILL.md1Skills CLI (Vercel)
npx skills add aj-geddes/useful-ai-prompts --skill interaction-design -a gemini-cli2Platform CLI
gemini skills install https://github.com/aj-geddes/useful-ai-prompts --path skills/interaction-designManually: put the files in place
.devin/skills/interaction-design/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add aj-geddes/useful-ai-prompts --skill interaction-design -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about interaction-design
How do I install interaction-design in Claude?
Run npx skills add aj-geddes/useful-ai-prompts --skill interaction-design -a claude-code. The skill file then lives at ~/.claude/skills/interaction-design/SKILL.md.
What does interaction-design do?
It helps the agent design interactions: gestures, animations, error and loading states, feedback on actions. It draws on guides for animation, error handling and accessibility.
Which platforms does the skill support?
Besides Claude it lists Codex, Cursor, GitHub Copilot, Gemini CLI and OpenCode. Each platform has its own install command and its own SKILL.md path.
Source text
SKILL.md · MIT
--- name: interaction-design description: > Design meaningful interactions and microinteractions. Create delightful user experiences through thoughtful animation, feedback, and responsive interface design. --- # Interaction Design ## Table of Contents - [Overview](#overview) - [When to Use](#when-to-use) - [Quick Start](#quick-start) - [Reference Guides](#reference-guides) - [Best Practices](#best-practices) ## Overview Interaction design focuses on how users engage with systems, creating intuitive and delightful experiences through feedback and responsiveness. ## When to Use - Designing user flows and touchpoints - Creating animations and transitions - Defining error and loading states - Building microinteractions - Improving usability and feedback - Mobile interaction patterns ## Quick Start Minimal working example: ```yaml Common Interaction Patterns: Swipe: Use: Mobile lists, carousels Feedback: Visual sliding, momentum Accessibility: Keyboard alternative (arrows) Tap & Hold: Use: Context menus, drag prep Feedback: Visual feedback after delay Duration: ~500ms before trigger Pinch & Zoom: Use: Image viewing, maps Feedback: Smooth zoom animation Boundaries: Set min/max zoom levels Drag & Drop: Use: Reordering, moving items Feedback: Visual during drag, drop confirmation Fallback: Alternative method (buttons) Double Tap: Use: Zoom, favorite, select Feedback: Immediate visual response // ... (see reference guides for full implementation) ``` ## Reference Guides Detailed implementations in the `references/` directory: | Guide | Contents | |---|---| | [Animation & Transition Design](references/animation-transition-design.md) | Animation & Transition Design | | [Error Handling & Feedback](references/error-handling-feedback.md) | Error Handling & Feedback | | [Accessibility in Interactions](references/accessibility-in-interactions.md) | Accessibility in Interactions | ## Best Practices ### ✅ DO - Keep animations under 400ms - Provide clear visual feedback - Use animations to guide attention - Respect motion preferences - Make interactions reversible - Test with keyboard and screen readers - Provide multiple interaction methods - Design for touch and mouse - Use appropriate easing curves - Document interaction behavior ### ❌ DON'T - Animate for decoration only - Use animations longer than 500ms - Ignore motion-sensitive users - Remove focus indicators - Trap users in modals - Use confusing animations - Animate everything - Ignore loading states - Forget error states - Skip accessibility testing
© aj-geddes · MIT · aj-geddes/useful-ai-prompts
Similar skills
Everything for Design →interaction-design by other authors comes first.