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 pktikkani/agent-skills --skill design-tastegit clone --depth 1 https://github.com/pktikkani/agent-skillsWrote 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/pktikkani/agent-skills/design-taste)<a href="https://agentmods.dev/skills/pktikkani/agent-skills/design-taste"><img src="https://agentmods.dev/badge/skills/pktikkani/agent-skills/design-taste/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/pktikkani/agent-skills/design-taste"><img src="https://agentmods.dev/badge/skills/pktikkani/agent-skills/design-taste.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.00067 | $0.00865 |
| Opus 5 | $0.00034 | $0.00432 |
| Sonnet 5 | $0.00013 | $0.00173 |
| Haiku 4.5 | $0.00007 | $0.00086 |
Grade A, and why
design-taste 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 11d 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.
How it starts
The opening of the file, as written. The whole thing — 64 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Design Taste
Core rule: motion must communicate something — spatial relationship, causality, or continuity. If an animation is decorative only, delete it. A site with 3 intentional animations beats one with 30 default ones.
View transitions
Transition only meaningfully shared elements — the same logical object visible before AND after navigation:
- Card thumbnail → detail hero image (same image, same subject)
- List item title → page heading (same text, same entity)
- Persistent chrome (nav, player bar) that should feel anchored
Rules:
view-transition-namegoes on the specific shared pair only. Never sprinkle names across a page hoping it "feels dynamic".- Names must be unique per page — in lists, assign the name dynamically to the clicked item only (or use
attr()/inline style), not every row. - Elements that are NOT the same object must not morph into each other. A grid of unrelated posts cross-fades; it does not fly around.
- Default root cross-fade is fine as-is. Don't add motion to it unless navigation has real spatial direction (e.g. drill-down → slide).
- Exiting content: fade out fast (~120ms). Entering content: fade/slide in slightly slower (~200ms). Never animate both heavily.
- Wrap in
@supports (view-transition-name: none)or feature-detectdocument.startViewTransition— no polyfill jank.
Hover states
Hover communicates affordance, not spectacle.
- Default vocabulary: color shift, underline, background tint, border emphasis. Pick ONE per element type and use it consistently.
- Banned as default:
hover:scale-*on everything. Scale-up hover on every card/button/icon is the #1 AI-slop tell. - Scale is acceptable only for: pressed state (
active:scale-[0.98]), or a single hero interactive element — never sitewide. - Interactive elements of the same type must share the same hover treatment. Mixed hover effects read as unintentional.
Motion specs
- UI feedback (hover, press, toggle): 100–150ms. Small movements (dropdown, tooltip): 150–200ms. Larger (modal, page): 200–300ms. Nothing over 400ms except deliberate hero moments.
- Animate
transformandopacityonly. Neverwidth/height/top/margin(layout thrash). - Easing:
ease-outfor entering,ease-infor exiting, neverlinearfor UI. One custom curve max per project, used everywhere. - Always respect
prefers-reduced-motion: reduce— disable transitions, keep instant state changes. - No scroll-triggered fade-in-up on every section. If used at all: once, subtle (<16px travel), first viewport only.
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.
- 11d ago First seen · 64 lines · 67 tokens per session scan A a6805d20a30e
design-taste is a skill published in the GitHub repository pktikkani/agent-skills (2 stars, last pushed 3d ago), licensed MIT. It adds 67 tokens to every session and 865 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
chakra-ui-builder
Build responsive, accessible UI components and layouts using Chakra UI v3, install or configure Chakra UI in new and existing projects, and design scalable themes using tokens, semantic tokens, recipes, and slot recipes. Use this skill whenever a user asks to build, create, or generate any UI component, page, form…
visual-ralph
Visual Ralph orchestration for frontend UI from generated references, static references, or live URL targets, using $ralph with built-in visual verdict and pixel-diff evidence until the implementation matches and leaves a reproducible design system.
frontend-ui-dark-ts
Build dark-themed React applications using Tailwind CSS with custom theming, glassmorphism effects, and Framer Motion animations. Use when creating dashboards, admin panels, or data-rich interfaces with a refined dark aesthetic.
reveal-hover-effect
Build cursor-following spotlight reveals that expose a second aligned image through a soft radial mask. Use for hover-to-color, before-and-after, x-ray, material, texture, product-detail, and illustrated hero effects where a desaturated or embossed base image should remain visible while another treatment follows an…
frontend-visual-qa
Audits already-rendered web, landing-page, HTML deck/slide, browser tool/game, dashboard/admin, design-system, and desktop UIs using real-browser or native-app journeys, inspected screenshots, DOM geometry, responsive or projection viewports, and a bundled Playwright sweep. Use after UI implementation to find…
prototype-web
A clickable, high-fidelity web product prototype with navigation, a hero section, feature cards, steps, social proof, and optional pricing. It is designed to resemble a finished landing page while remaining a prototype.