agentleFS
inttegrointtegro/labor/skills/fluid-interface-design/SKILL.md

fluid-interface-design

Skill1 starsChanged 4 days agoMITView on GitHub

Platform-neutral guidance for responsive, physical, and accessible interface motion. Use when designing or reviewing direct manipulation, drag and swipe interactions, springs, velocity handoff, momentum, interruptible transitions, sheets, soft boundaries, translucent materials, interaction typography, or reduced-motion behavior on the web or in native apps.

1 other project uses a version of this.

Adopted by

Most recently taken up by

The file

Show its rules and text

We split this skill into the rules it gives an agent

24 rules. About 0 are common, 24 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈24

    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:

    Remove motion that serves none of those purposes.

    line 17
  2. Distinctive:

    Keep interactive motion interruptible and redirectable.

    line 25
  3. Distinctive:

    Start a new transition from the current rendered value, not from a stale logical target.

    line 26
  4. Distinctive:

    Use the same spatial path for entry and exit unless the change in path carries meaning.

    line 27
  5. Distinctive:

    Use an easing curve for a short, noninteractive state transition with a known duration.

    line 30
  6. Distinctive:

    Use a spring when an object can be grabbed, redirected, or handed velocity.

    line 31
  7. Distinctive:

    Use momentum projection before snapping when a flick should affect the destination.

    line 32
  8. Distinctive:

    Use progressive resistance at boundaries instead of a hard visual stop.

    line 33
  9. Distinctive:

    Keep every gesture available through another accessible input path.

    line 38
  10. Distinctive:

    Test interruption, reversal, rapid repeated input, slow drags, fast flicks, cancellation, and boundary cases.

    line 41
  11. Distinctive:

    Test on representative low-power and high-refresh-rate devices.

    line 43
  12. Distinctive:

    Keep the input-to-feedback path free of artificial delays.

    line 49
  13. Distinctive:

    Use pointer capture for drags so the interaction remains coherent outside the original bounds.

    line 50
  14. Distinctive:

    Do not disable input merely because a transition is running.

    line 61
  15. Distinctive:

    Start with critically damped motion for ordinary interface changes.

    line 67
  16. Distinctive:

    Add overshoot only when the initiating action carries physical momentum or the overshoot communicates state.

    line 68
  17. Distinctive:

    Read motion and gesture mechanics for formulas and implementation notes.

    line 72
  18. Distinctive:

    Keep the source and destination visually related throughout the transition.

    line 77
  19. Distinctive:

    Use depth, scrims, blur, and shadow to express hierarchy, not to decorate every surface.

    line 78
  20. Distinctive:

    Avoid stacking translucent layers until text and controls lose stable contrast.

    line 79
  21. Distinctive:

    Read materials, type, and accessibility for implementation constraints.

    line 87
  22. Distinctive:

    Prefer compositor-friendly properties such as transforms and opacity for continuous motion.

    line 91
  23. Distinctive:

    Prefer a motion library that exposes current values, velocity, cancellation, and retargeting for gesture-driven work.

    line 93
  24. Distinctive:

    Do not claim native haptic support on platforms or browsers that do not provide it.

    line 95

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 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

Fluid Interface Design

Build interfaces that respond immediately, preserve continuity, and remain controllable while they move. Treat motion as behavior produced by state and input, not decoration added after the interaction.

This is a platform-neutral design skill. It draws on public interaction-design research and platform guidance, but it does not ask for the visual imitation of any company or operating system.

Workflow

  1. Define the interaction contract.
    • Name the user action, the state change it causes, and the recovery path.
    • Decide whether motion communicates causality, hierarchy, spatial continuity, progress, or completion.
    • Remove motion that serves none of those purposes.
  2. Trace the input path.
    • Identify pointer, touch, keyboard, assistive-technology, and programmatic paths.
    • Respond visually on press, not only after activation.
    • For direct manipulation, update continuously and preserve the exact grab offset.
  3. Design continuity.
    • Keep interactive motion interruptible and redirectable.
    • Start a new transition from the current rendered value, not from a stale logical target.
    • Use the same spatial path for entry and exit unless the change in path carries meaning.
  4. Choose motion behavior.
    • Use an easing curve for a short, noninteractive state transition with a known duration.
    • Use a spring when an object can be grabbed, redirected, or handed velocity.
    • Use momentum projection before snapping when a flick should affect the destination.
    • Use progressive resistance at boundaries instead of a hard visual stop.
  5. Design alternatives.
    • Preserve feedback under reduced motion with short fades, color, or immediate state changes.
    • Replace translucency when reduced transparency or increased contrast is requested.
    • Keep every gesture available through another accessible input path.
  6. Verify in motion.
    • Test interruption, reversal, rapid repeated input, slow drags, fast flicks, cancellation, and boundary cases.
    • Inspect real frames or a recording; a nominal frame rate does not prove smooth visual motion.
    • Test on representative low-power and high-refresh-rate devices.

Core Rules

Response

  • Keep the input-to-feedback path free of artificial delays.
  • Use pointer capture for drags so the interaction remains coherent outside the original bounds.
  • Separate recognition thresholds from visible lag: a gesture may need hysteresis, but the interface should still acknowledge contact.

Direct manipulation

  • Map drag distance to object movement one-to-one until the interaction reaches a meaningful constraint.
  • Preserve where the user grabbed the object; do not jump its center under the pointer.
  • Track a short timestamped position history so release velocity is stable rather than based on one noisy event.

Interruptibility

  • Do not disable input merely because a transition is running.
  • Retarget from the live presentation value and carry current velocity into the new motion.
  • Model independent axes independently when their velocities or targets differ.

Springs and momentum

  • Start with critically damped motion for ordinary interface changes.
  • Add overshoot only when the initiating action carries physical momentum or the overshoot communicates state.
  • Hand release velocity into the spring so the seam between gesture and animation is not visible.
  • Project the likely resting point before selecting a snap target; do not choose only from the release position.

Read motion and gesture mechanics for formulas and implementation notes.

Space and hierarchy

  • Anchor menus, popovers, and expanding surfaces to their trigger.
  • Keep the source and destination visually related throughout the transition.
  • Use depth, scrims, blur, and shadow to express hierarchy, not to decorate every surface.
  • Avoid stacking translucent layers until text and controls lose stable contrast.

Typography and feedback

  • Tune tracking and line height by text size; a single letter-spacing value is rarely correct across a type scale.
  • Synchronize visual, audio, and haptic feedback to the same causal event.
  • Reserve multimodal feedback for meaningful state changes so it remains informative.

Read materials, type, and accessibility for implementation constraints.

Implementation Boundary

  • Prefer compositor-friendly properties such as transforms and opacity for continuous motion.
  • Measure before introducing will-change; persistent promotion can waste memory.
  • Prefer a motion library that exposes current values, velocity, cancellation, and retargeting for gesture-driven work.
  • CSS transitions remain appropriate for simple noninteractive state changes.
  • Do not claim native haptic support on platforms or browsers that do not provide it.

Review Checklist

  • Feedback begins immediately and remains continuous.
  • Direct manipulation preserves the grab point and tracks input accurately.
  • Motion can be interrupted and reversed without jumps.
  • Release velocity carries into the settling behavior.
  • Entry and exit preserve spatial logic.
  • Boundaries communicate resistance without appearing frozen.
  • Keyboard and assistive-technology paths produce equivalent outcomes.
  • Reduced motion, reduced transparency, and increased contrast have useful alternatives.
  • Motion has been reviewed with real input and representative content, not only a scripted demo.

Sources and Attribution

This skill is a substantial rewrite derived from Emil Kowalski's apple-design skill, sourced from the emilkowalski/skills GitHub repository. Labor generalized the platform framing, rewrote the workflow, and split implementation detail into references; that modification does not erase the upstream origin.

The interaction principles also draw on public sources, including Apple's Designing Fluid Interfaces session and web-platform documentation. The upstream skill is MIT-licensed, Copyright (c) 2026 Emil Kowalski; its required notice is preserved in LICENSE. Product names and trademarks belong to their respective owners. Labor is not affiliated with or endorsed by Emil Kowalski or Apple.

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.