agentleFS
Sign inStart free
podopodo/design-agent-skills/skills/interaction-design/SKILL.md

interaction-design

Skill32 starsChanged 6 months agoMITView on GitHub

Interaction design (IxD) principles and frameworks for digital product work. Covers interaction flows, component state design (hover/focus/error/loading/empty), micro-interactions, affordances, feedback mechanisms, mental models, task flows, gesture design, response time guidelines, and handoff annotations. Grounded in Norman's design principles and Tognazzini's first principles of interaction design.

20 other projects use a version of this, 1 of them edited.

Adopted by

Most recently taken up by

Used with

Projects with it also use accessibility-compliance, design-system-patterns and 9 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • CodeWithBehnamSkill

    accessibility-compliance

    Implement WCAG 2.2 compliant interfaces with mobile accessibility, inclusive design patterns, and assistive technology support. Use when auditing accessibility, implementing ARIA patterns, building for screen readers, or ensuring inclusive user experiences.

    Also in 3 projects that use this

  • wpankSkill

    design-system-patterns

    Foundational design system architecture — token hierarchies, theming infrastructure, token pipelines, and governance. Use when creating design tokens, implementing theme switching, setting up Style Dictionary, or establishing multi-brand theming. Triggers on design tokens, theme provider, Style Dictionary, token pipeline, multi-brand theming, CSS custom properties architecture.

    Also in 3 projects that use this

  • HamzaSheikh768Skill

    responsive-design

    Implements mobile-first responsive design using Tailwind's responsive utilities, proper breakpoints, flexible layouts, and accessibility considerations.

    Also in 3 projects that use this

  • dillonluiSkill

    design-review

    Review a view or flow for UX and UI issues. Provides severity-ranked, actionable findings grounded in established design heuristics. Use when the user asks for design feedback, UX review, or UI critique.

    Also in 6 projects that use this

  • ElasticSkill

    accessibility

    Accessibility guidance for Kibana. Use this skill when working with or reviewing EUI components, resolving a11y-related (@elastic/eui) ESLint issues, and ensuring proper use of ARIA attributes, focus management, keyboard interactions, and accessible naming conventions.

    Also in 4 projects that use this

  • ozgureyilmazSkill

    apple-design

    Apple's approach to interface design and fluid, physical motion, translated for the web. Use when building or reviewing gesture-driven UI, spring animations, drag/swipe/sheet interactions, momentum and interruptible transitions, translucent materials and depth, typography (optical sizing, tracking, leading), reduced-motion, or the design foundations (feedback, spatial consistency, restraint) behind Apple-style interfaces.

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

1 rule. 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 16 edited versions we read keep these.

  • 1

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    License: no LICENSE file in the repo <!-- das:install:end -->

    line 57

“Common” is measured: kept by at least 6 in 10 of the 16 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

interaction-design

Catalogue stub — full skill: rastian/interaction-design-skills

<!-- das:install:start — generated from stub.yaml by `npm run generate`; edit stub.yaml, not this block -->

Decision tree

  1. Is the full skill already installed?
    • Global: f=~/.agents/skills/interaction-design/SKILL.md; [ -f "$f" ] && ! grep -q "^das:" "$f" && echo "installed" || echo "pointer"
    • Project: f=.agents/skills/interaction-design/SKILL.md; [ -f "$f" ] && ! grep -q "^das:" "$f" && echo "installed" || echo "pointer"
    • installed → the skill is installed as interaction-design, invoke it and proceed
    • pointer → go to step 2

  2. Detect scope, then install:

    [ -e ~/.agents/skills/interaction-design ] && echo "global" || echo "project"

    Global:

    npx skills add rastian/interaction-design-skills --skill interaction-design -g -y

    Project:

    npx skills add rastian/interaction-design-skills --skill interaction-design -y

    Claude Code: send a command as a chat message starting with ! to run it without leaving the conversation.

Heads-up

  • License: no LICENSE file in the repo
<!-- das:install:end -->

Invoke after install

  • Skill name: interaction-design
  • Trigger phrases: "interaction design", "interaction flow", "component states", "micro-interaction", "affordance", "interaction spec"

What it does

A practitioner's guide to interaction design — from foundational principles to practical state design, flow specification, and interaction review:

  • Interaction flows — task flows, user flows, navigation patterns, decision trees
  • State design — the full set of component states: default, hover, focus, active, disabled, loading, error, success, empty, skeleton
  • Micro-interactions — trigger → rules → feedback → loops model; timing and easing guidelines
  • Affordances — signifiers, feedback, constraints, mapping, consistency, discoverability
  • IxD principles — Norman's principles (Design of Everyday Things) and Tognazzini's First Principles of Interaction Design
  • Response time — 100ms/1s/10s thresholds, progress indicators, optimistic UI
  • Interaction specs — handoff annotation format, interaction specification documents
  • Interaction audit — review checklist against established principles

The install includes a reference/ folder with the principles, response-time and patterns-and-flows notes the skill points to.

When NOT to use

  • UX journey mapping + Playwright testing → use neo-user-journey
  • Animation and motion timing → use gsap-skills or framer-motion-skills
  • WCAG accessibility audit → use wcag-ai-skill
  • Full UX strategy → use ux-designer-skill

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free