Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx skills add stvlynn/dsh.fish --skill make-interfaces-feel-bettergit clone --depth 1 https://github.com/stvlynn/dsh.fishWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/stvlynn/dsh.fish/make-interfaces-feel-better)<a href="https://agentmods.dev/skills/stvlynn/dsh.fish/make-interfaces-feel-better"><img src="https://agentmods.dev/badge/skills/stvlynn/dsh.fish/make-interfaces-feel-better/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/stvlynn/dsh.fish/make-interfaces-feel-better"><img src="https://agentmods.dev/badge/skills/stvlynn/dsh.fish/make-interfaces-feel-better.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00117 | $0.02753 |
| Opus 5.5 | $0.00047 | $0.01101 |
| Sonnet 5.5 | $0.00023 | $0.00551 |
| Haiku 4.5 | $0.00012 | $0.00275 |
Grade A, and why
make-interfaces-feel-better scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 1mo ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
This is a copy
97% identical to polish — 1 line differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 188 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Details that make interfaces feel better
Great interfaces rarely come from a single thing. It's usually a collection of small details that compound into a great experience. Apply these principles when building or reviewing UI code. Before suggesting or writing a fix, identify the project's existing styling system and express the change in that system: Tailwind in a Tailwind project, plain CSS in a CSS project, or the established CSS-in-JS approach. Never introduce a second styling system just to apply a polish fix.
When reviewing, slow the interface down: replay motion at 10% speed in the browser's Animations panel and walk every state: hover, focus, active, loading, empty. What feels off at 10% speed is what's subtly wrong at full speed.
Quick Reference
| Category | When to Use |
|---|---|
| Typography | Text wrapping, font smoothing, tabular numbers |
| Surfaces | Border radius, optical alignment, shadows, image outlines, hit areas |
| Animations | Interruptible animations, enter/exit transitions, icon animations, scale on press, motion restraint |
| Icons | Icon stroke weight, states via currentColor, outline vs fill, sizing, RTL flipping |
| Performance | Transition specificity, will-change usage |
Core Principles
1. Concentric Border Radius
Outer radius = inner radius + padding. Mismatched radii on nested elements is the most common thing that makes interfaces feel off.
2. Optical Over Geometric Alignment
When geometric centering looks off, align optically. Buttons with icons, play triangles, and asymmetric icons all need manual adjustment.
3. Shadows for Elevation, Borders for Structure
For buttons, cards, and containers whose border exists only to create depth, prefer layered transparent box-shadow values. Keep borders that communicate structure or state: dividers, layout separators, and selected or focus states.
4. Interruptible Animations
What ships with it
6 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 1mo ago First seen · 188 lines · 117 tokens per session scan A c1d508fa7bef
make-interfaces-feel-better is a skill published in the GitHub repository stvlynn/dsh.fish (2 stars, last pushed yesterday), licensed MIT. It adds 117 tokens to every session and 2,753 once invoked, about $0.0005 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 97% identical to polish, differing in 1 line, and is treated as a copy.
Other skills, from other repositories
frontend-design
Guidance for distinctive, intentional visual design when building new UI or reshaping an existing one. Helps with aesthetic direction, typography, and making choices that don't read as templated defaults.
figma-implement-motion
Translates Figma motion and animations into production-ready application code. Use when implementing animation/motion from a Figma design — user mentions "implement this motion", "add animation from Figma", "animate this component", provides a Figma URL whose node is animated, or when getdesigncontext returns motion…
shadcn
Manages shadcn components and projects — adding, searching, fixing, debugging, styling, and composing UI. Provides project context, component docs, and usage examples. Applies when working with shadcn/ui, component registries, presets, --preset codes, or any project with a components.json file. Also triggers for…
ipollowork-plugin-ui
A set of instructions for building iPolloWork plug-in interfaces with shared components, colours, fonts, and interaction rules. It covers both React plug-ins and standalone HTML or iframe plug-ins.
emil-design-eng
Create, implement, or review design engineering craft work with format, accessibility, performance, and visual-verification controls. Use when the requested deliverable depends on design engineering craft.
tailwind-design-system
Create, implement, or review tailwind design system work with format, accessibility, performance, and visual-verification controls. Use when the requested deliverable depends on tailwind design system.