Interface Design for Dashboards and Apps
holaboss-ai/holaOS
Pushes an agent past generic defaults when designing dashboards, admin panels, SaaS apps and tools, with attention to structure, type, navigation and how data is shown.
Apply an emotional resonance lens to a UI that is technically correct but flat, prescribing changes at the copy, motion, and interaction layer.
Install Interfaces That Feel
$ npx skills add Owl-Listener/designer-skills --skill interfaces-that-feel -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install Owl-Listener/designer-skills interfaces-that-feel --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/Owl-Listener/designer-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/interaction-design/skills/interfaces-that-feel .claude/skills/interfaces-that-feel && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "interfaces-that-feel" agent skill from https://github.com/Owl-Listener/designer-skills/tree/main/interaction-design/skills/interfaces-that-feel into .claude/skills/interfaces-that-feel/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "interfaces-that-feel", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/Owl-Listener/designer-skills/tree/main/interaction-design/skills/interfaces-that-feelType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add Owl-Listener/designer-skills --skill interfaces-that-feel -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install Owl-Listener/designer-skills interfaces-that-feel --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Owl-Listener/designer-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/interaction-design/skills/interfaces-that-feel .agents/skills/interfaces-that-feel && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "interfaces-that-feel" agent skill from https://github.com/Owl-Listener/designer-skills/tree/main/interaction-design/skills/interfaces-that-feel into .agents/skills/interfaces-that-feel/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "interfaces-that-feel", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add Owl-Listener/designer-skills --skill interfaces-that-feel -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install Owl-Listener/designer-skills interfaces-that-feel --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Owl-Listener/designer-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/interaction-design/skills/interfaces-that-feel .cursor/skills/interfaces-that-feel && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "interfaces-that-feel" agent skill from https://github.com/Owl-Listener/designer-skills/tree/main/interaction-design/skills/interfaces-that-feel into .cursor/skills/interfaces-that-feel/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "interfaces-that-feel", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/Owl-Listener/designer-skills.git --path interaction-design/skills/interfaces-that-feel--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add Owl-Listener/designer-skills --skill interfaces-that-feel -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install Owl-Listener/designer-skills interfaces-that-feel --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Owl-Listener/designer-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/interaction-design/skills/interfaces-that-feel .gemini/skills/interfaces-that-feel && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "interfaces-that-feel" agent skill from https://github.com/Owl-Listener/designer-skills/tree/main/interaction-design/skills/interfaces-that-feel into .gemini/skills/interfaces-that-feel/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "interfaces-that-feel", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install Owl-Listener/designer-skills interfaces-that-feelInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add Owl-Listener/designer-skills --skill interfaces-that-feel -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/Owl-Listener/designer-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/interaction-design/skills/interfaces-that-feel .github/skills/interfaces-that-feel && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "interfaces-that-feel" agent skill from https://github.com/Owl-Listener/designer-skills/tree/main/interaction-design/skills/interfaces-that-feel into .github/skills/interfaces-that-feel/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "interfaces-that-feel", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add Owl-Listener/designer-skills --skill interfaces-that-feel -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install Owl-Listener/designer-skills interfaces-that-feel --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Owl-Listener/designer-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/interaction-design/skills/interfaces-that-feel .opencode/skills/interfaces-that-feel && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "interfaces-that-feel" agent skill from https://github.com/Owl-Listener/designer-skills/tree/main/interaction-design/skills/interfaces-that-feel into .opencode/skills/interfaces-that-feel/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "interfaces-that-feel", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
interfaces-that-feel- GitHub stars
- 2.9k
- Used in
- 1 other repo
- Token cost
- ~977 tokens
- SKILL.md length
- 531 words
- Files
- 1
- Skills in repo
- 107
- Repo updated
- First seen
- Licence
- MIT
At a glance
Apply an emotional resonance lens to a UI that is technically correct but flat, prescribing changes at the copy, motion, and interaction layer.
- A design tests fine but lands cold
- SKILL.md covers What You Do, The Translation Process, Emotional Timing Principles and Copy Voice by State, plus 4 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- Tasks that involve UX design
What it does
Interfaces That Feel is an agent skill from Owl-Listener/designer-skills. 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).
Its SKILL.md is about 980 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Frontend & Design, covering UX design and UI design. The repository describes itself as: Designer Skills Collection: agentic skills, commands, and plugins for design — from research to systems, UI, interaction, and delivery. The licence is MIT.
When your agent uses it
- A design tests fine but lands cold
- Tasks that involve UX design
- Tasks that involve UI design
Example prompts
- “/interfaces-that-feel”
What it can do on your machine
Read from SKILL.md and the folder at commit 9a6930c. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Interfaces That Feel loads about 977 tokens when it runs. Until then it costs about 71 tokens; SKILL.md has 531 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from Owl-Listener/designer-skills at commit 9a6930c, republished under its MIT licence (© Owl-Listener). 531 words, ~977 tokens.
Download SKILL.mdSave it as
.claude/skills/interfaces-that-feel/SKILL.md (or your agent's skills folder).- 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 |
Show full SKILL.md (208 more words)Show less
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
© Owl-Listener, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in interaction-design/skills/interfaces-that-feel of Owl-Listener/designer-skills.
Open the folder on GitHubat commit 9a6930c
Used in 1 other repository
We found 2 copies of this SKILL.md (exact, near-identical or edited) in other folders, from 1 other GitHub owner. This page covers the copy in Owl-Listener/designer-skills, which our catalogue first saw on October 7, 2026.
Compare with similar skills
Interfaces That Feel next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Interfaces That Feel this skillOwl-Listener/designer-skills | 2.9k | 1 repos | ~977 | Automated safety check: Pass | MIT | |
| Interface Design for Dashboards and Appsholaboss-ai/holaOS | 11k | 3 repos | ~6k | Automated safety check: Pass | MIT | |
| HTML Feature Mocksimbue-ai/bouncer | 400 | — | ~677 | Automated safety check: Pass | AGPL-3.0 | |
| Ijfw DesignFerroxLabs/ijfw | 212 | — | ~2.2k | Automated safety check: Pass | MIT | |
| Edit Figma Designwarpdotdev/warp | 65k | 1 repos | ~2.4k | Automated safety check: Pass | AGPL-3.0 | |
| Super UI UX Designsyahiidkamil/Software-Engineer-AI-Agent-Atlas | 401 | — | ~9k | Automated safety check: Pass | None |
Similar skills
HTML Feature Mocks
imbue-ai/bouncer
Explores a feature idea through HTML mocks that match the project's existing UI, keeping every earlier version and logging each requested tweak in a context file.
Ijfw Design
FerroxLabs/ijfw
A skill your agent uses when the user says: 'design', 'redesign', 'UI', 'UX', 'dashboard', 'page', 'component', 'make it look better', 'polish', 'pretty', 'professional', 'user experience'…
Edit Figma Design
warpdotdev/warp
Creates or revises Figma designs from a written description using the Figma MCP authoring tools, in a new blank file or an existing one.
Super UI UX Design
syahiidkamil/Software-Engineer-AI-Agent-Atlas
Complete UI/UX design capability — a wiki-style knowledge map of design theory (UX laws, Nielsen heuristics, usability, visual hierarchy, typography, contrast/WCAG, design systems…
LobeHub UX Checklists
lobehub/lobehub
Applies LobeHub's four design values and per-module interaction checklists when building or reviewing user-facing flows, covering behavior over time rather than visual style.
More from Owl-Listener/designer-skills
All 107 skills in this repoA B Test Design
Owl-Listener/designer-skills
Design an A/B experiment — hypothesis, variants, primary metric, and sample size.
Accessibility Test Plan
Owl-Listener/designer-skills
Plan accessibility testing — assistive technologies, participant criteria, WCAG coverage, and session protocol.
Aesthetic Usability
Owl-Listener/designer-skills
Apply the Aesthetic-Usability Effect — polished, consistent interfaces are perceived as more usable and forgive minor friction.
Affinity Diagram
Owl-Listener/designer-skills
Cluster many qualitative data points into themes and insight statements.
Animation Principles
Owl-Listener/designer-skills
Apply animation principles — easing, staging, follow-through — to one specific UI motion.
Business Design
Owl-Listener/designer-skills
Read financials, map competitive landscapes, and argue design decisions in the language of value.
Related
Categories
Questions about Interfaces That Feel
What does Interfaces That Feel do?
Apply an emotional resonance lens to a UI that is technically correct but flat, prescribing changes at the copy, motion, and interaction layer. Interfaces That Feel is an agent skill from Owl-Listener/designer-skills. Apply an emotional resonance lens to a UI that is technically correct but flat, prescribing changes at the copy, motion, and interaction layer.
When should I use Interfaces That Feel?
Interfaces That Feel fits situations like: A design tests fine but lands cold; tasks that involve UX design; tasks that involve UI design.
How do I install Interfaces That Feel in Claude Code?
Run `npx skills add Owl-Listener/designer-skills --skill interfaces-that-feel -a claude-code`. Or copy the skill folder (interaction-design/skills/interfaces-that-feel in Owl-Listener/designer-skills) into .claude/skills/interfaces-that-feel in your project. Claude Code loads it when a task matches its description.
How do I install Interfaces That Feel in Codex?
Run `npx skills add Owl-Listener/designer-skills --skill interfaces-that-feel -a codex`. Or copy the skill folder (interaction-design/skills/interfaces-that-feel in Owl-Listener/designer-skills) into .agents/skills/interfaces-that-feel in your project. Codex loads it when a task matches its description.
Can I use Interfaces That Feel in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add Owl-Listener/designer-skills --skill interfaces-that-feel -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/interfaces-that-feel, .gemini/skills/interfaces-that-feel, .github/skills/interfaces-that-feel and .opencode/skills/interfaces-that-feel in your project.
What does Interfaces That Feel need to run?
SKILL.md names no scripts, command-line tools or credentials: Interfaces That Feel is instructions for the agent only.
Does Interfaces That Feel access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Interfaces That Feel safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Interfaces That Feel use?
Interfaces That Feel is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Interfaces That Feel use?
About 977 tokens (SKILL.md is roughly 3.9k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Interfaces That Feel?
Skills that share tags, products or a category with Interfaces That Feel: Interface Design for Dashboards and Apps (holaboss-ai/holaOS, 11k stars), HTML Feature Mocks (imbue-ai/bouncer, 400 stars), Ijfw Design (FerroxLabs/ijfw, 212 stars) and Edit Figma Design (warpdotdev/warp, 65k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Interfaces That Feel?
Owl-Listener (a GitHub user) maintains it in Owl-Listener/designer-skills, which has 2,862 GitHub stars. The repository holds 107 skills in this directory. The repository was last updated on September 5, 2026.
Source: Owl-Listener/designer-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.