agentleFS
botirkhaltaevbotirkhaltaev/botir-skills/skills/interaction-design-patterns/SKILL.md

interaction-design-patterns

Skill4 starsChanged 3 months agoApache-2.0View on GitHub

Common interaction design patterns: forms, navigation, search, filters, onboarding, empty states, error states, loading states, and microinteractions. Each pattern includes the problem it solves, when to use it, and common anti-patterns. Use when designing user flows, choosing interaction patterns, or reviewing interaction quality. Triggers on: "interaction pattern", "form design", "navigation pattern", "onboarding", "empty state", "error state", "microinteraction", "user flow".

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    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:

    Keep current location visible.

    line 31

≈ “Common” is an estimate: at least 1 in 5 of the 308,232 skill files we read have a rule of the same kind, not the same words. “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 Patterns

Choose the right pattern for the job. Depth for forms and empty/error/loading lives in references/ and sibling skills.

Pattern picker

JobPreferAvoid
Collect required dataForm / wizard (form-ux)Chat-only
Move between sectionsTabs / sidebar / breadcrumbsHidden hamburger for primary nav
Find contentSearch + filtersDeep nav only
First run / activationonboarding-uxFeature dump tour
No data / failure / waiterror-empty-statesBlank screen / spinner forever
Confirm a small resultToast / inlineModal for non-decisions

Navigation (short)

PatternBest for
Tab bar3–5 top sections
SidebarComplex IA
BreadcrumbsDepth ≥3
Command palettePower users

Keep current location visible; don't move primary nav between screens.

Search (short)

Prominent field; debounced suggestions (150–300ms); recent searches; helpful zero-results; filters when result sets are large.

Microinteractions

Trigger → rules → feedback → loop. Keep motion purposeful, ≤~300ms, consistent. Details → motion-design-principles.

Reference Map

  • references/forms.md — form pattern summary → deep dive form-ux
  • references/empty-error-loading.md — empty/error/loading summary → error-empty-states

Related Skills

  • For form UX depth → use form-ux
  • For empty/error/offline/permission states → use error-empty-states
  • For onboarding / first-run → use onboarding-ux
  • For visual fundamentals → use ui-visual-design
  • For mobile/touch → use mobile-touch-design
  • For accessibility → use a11y-accessibility-design
  • For AI-specific failures → use ai-ui-anti-patterns

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.