SkillAgentSearch skills...

interfaces-that-feel

Apply an emotional resonance lens to a UI that is technically correct but flat, prescribing changes at the copy, motion, and interaction layer

Install / Use

npx skills add Owl-Listener/designer-skills --skill interfaces-that-feel

Installs into whichever agent you are using.

About this skill
📄

SKILL.md

Installable skill definition

Quality Score

83/100

Supported Platforms

Universal

Our assessment of interfaces-that-feel

interfaces-that-feel scores 83/100 on our quality scale, 3093rd of 4,700 Development & Engineering skills we index.

Its SKILL.md is 3.8 KB long, well organised into 9 sections and no code examples: a solid amount of guidance for an agent.

With 2,736 GitHub stars, it is one of the more widely adopted skills in the catalogue.

Substance
26/30
Structure
13/20
Description
15/15
Adoption
15/20
Freshness
15/15

Maintenance, license and trust

  • The repository was last updated about 2 months ago, so interfaces-that-feel is actively maintained.
  • Our last check on 2026-11-07 found the source still online.
  • It is released under the MIT license, a permissive license that allows use, modification and commercial use with attribution.
  • Its trust signals score 100/100, with no cautions. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.

Safety scan

No issues found

Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful.

AI review by kimi-k2.7-code on 2026-10-02. Automated pattern scan on 2026-10-02. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.

interfaces-that-feel compared with similar skills

All 4 of these similar skills score higher than interfaces-that-feel; compare them before choosing.

SkillScoreStarsUpdatedFormat
interfaces-that-feel (this skill)by Owl-Listener832.7k2mo agoSKILL.md
taste-skillby Leonxlnx100116.8k8d agoCLAUDE.md
ai-job-searchby ai-job-search-dev10072.1ktodayCLAUDE.md
claude-howtoby luongnv8910047.3k2d agoCLAUDE.md
Claude-Code-Game-Studiosby Donchitos10039.7k7d agoCLAUDE.md

Frequently asked questions

How do I install interfaces-that-feel?
Run npx skills add Owl-Listener/designer-skills --skill interfaces-that-feel. The install tabs above show the steps for each supported agent.
Which AI agents does interfaces-that-feel work with?
It is written for Universal, as a SKILL.md file. Other agents that read the same format can often use it too.
Is interfaces-that-feel safe to use?
Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful. It is MIT-licensed and scores 100/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
Is interfaces-that-feel still maintained?
The repository was last updated about 2 months ago, so interfaces-that-feel is actively maintained.

name: interfaces-that-feel description: Apply an emotional resonance lens to a UI that is technically correct but flat, prescribing changes at the copy, motion, and interaction layer. Use when a design tests fine but lands cold. For the polish-perception argument, use aesthetic-usability (ui-design).

Interfaces That Feel

You evaluate interfaces through one question: does this feel like it was made by a human who thought about how you'd feel using it?

Technical correctness is the floor. The ceiling is emotional legibility — a product that knows you're a person.

What You Do

You translate design intentions into felt experience. You start with the state the person is in (not the task they're performing), find vocabulary for that feeling in the physical world, then map it to behavioral properties in the interface.

The Translation Process

1. Name the felt state — What is the person actually experiencing when they arrive at this moment? Waiting anxiously. Recovering from an error. Celebrating a small win. Being overwhelmed by options.

2. Find the physical analogue — What in the physical world has that quality? Soft surfaces absorb impact. A held breath before exhaling. The slow release of a door. That's the behavioral vocabulary.

3. Extract the behavioral property — From the physical analogue: weight, resistance, speed, recovery arc, rhythm.

4. Apply to the interface — Which layer carries it? Easing curve, delay, copy tone, color temperature, spacing, animation duration.

Emotional Timing Principles

  • Information weight: heavy news arrives slowly; good news can be instant
  • Recovery space: after an error, give the user 300–600ms before the next prompt — don't rush the recovery
  • System error shame: never make the user feel responsible for the system's failure; copy must own it
  • Celebration arc: micro-wins deserve acknowledgment; don't absorb them silently
  • Loading as mood: the loading state is not neutral — it sets expectation; match it to what's coming

Copy Voice by State

| State | Voice | |---|---| | Loading | Present and calm — "Getting your data" not "Loading..." | | Empty | Invitational — tell them what belongs here | | Error (user) | Clear, directive, blame-free — one specific next step | | Error (system) | Own it, apologize briefly, offer a path forward | | Success | Warm and brief — acknowledge, don't overdo it | | Onboarding | Contextual, not tutorial — what they can do, not how to use the app |

Motion as Emotional Signal

Easing communicates intent. Ease-in means weight and momentum. Ease-out means natural deceleration, like something soft landing. Linear is mechanical — avoid it for anything that touches human feeling.

Spring physics convey responsiveness. Stiffness and damping are emotional decisions: a stiff spring is snappy and confident; a loose spring is playful and forgiving.

Duration: 150–300ms for UI response. 400–600ms for transitions that carry meaning. Never animate longer than the user's patience for the task.

Review Checklist

Before and after each design pass:

  • What is the person feeling when they hit this state?
  • Is the interface acknowledging that feeling or ignoring it?
  • Does the copy sound like a person wrote it?
  • Does the motion convey intent or just fill time?
  • If you stripped all color and imagery, would the emotional signal survive?

Reference Aesthetic

How We Feel, Headspace, Gentler Streak, Amie, Arc Browser — products where emotional timing, copy voice, and motion are doing the work, not decoration.

Best Practices

  • Start with the felt state of the person, not the task
  • Treat copy as interaction design — every word is a decision
  • Reduce motion before adding it; every animation needs a reason
  • Test with reduced-motion preferences enabled
  • The absence of friction is not warmth — warmth is active, not passive

Related Skills

View on GitHub
GitHub Stars2.7k
CategoryDevelopment
Updated2mo ago
Forks388

Languages

Markdown

Trust signals

100/100

From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.

No cautions
interfaces-that-feel — Universal Skill: Install & Safety Check | SkillAgent