Borrowing it
Nothing to install: this file belongs to tutur3u/platform. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/tutur3u/platform/main/.agents/skills/design-taste-frontend/SKILL.mdgit clone --depth 1 https://github.com/tutur3u/platformWrote 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/tutur3u/platform/design-taste-frontend)<a href="https://agentmods.dev/skills/tutur3u/platform/design-taste-frontend"><img src="https://agentmods.dev/badge/skills/tutur3u/platform/design-taste-frontend/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/tutur3u/platform/design-taste-frontend"><img src="https://agentmods.dev/badge/skills/tutur3u/platform/design-taste-frontend.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.00019 | $0.00333 |
| Opus 5 | $0.00010 | $0.00167 |
| Sonnet 5 | $0.00004 | $0.00067 |
| Haiku 4.5 | $0.00002 | $0.00033 |
Grade A, and why
design-taste-frontend 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 4d 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 design-taste-frontend-v1 — 243 lines 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.
What it actually says
Expressive Frontend Design
Start from the product's audience, primary task, existing visual system, and the requested degree of change. Choose density, composition, and motion to serve that context. A routine component fix does not call for a new design system.
- Establish clear hierarchy with type, spacing, and grouping. Use cards where they communicate a unit of content or action; use open layouts elsewhere.
- Preserve the existing framework, theme tokens, icon package, and fonts unless changing them is part of the brief. Confirm dependencies before importing them.
- Keep interactive state in the appropriate client boundary. Server components can fetch and compose data; they need not be reduced to static markup.
- Design loading, empty, error, disabled, focus, and success states for the actual interactions. Never fabricate customer claims, testimonials, or production metrics.
- Use responsive grids and content-driven breakpoints. Preserve reading and tab order, allow text scaling, and verify localized copy at phone and laptop widths.
- Motion should clarify state or support the visual concept. CSS is sufficient for many interactions; use an existing animation library for complex choreography. Clean up effects, respect reduced motion, and keep content usable without animation.
Prefer one coherent visual direction over combining conflicting taste presets. Use source assets, generated artwork when useful, or clearly marked placeholders. Stop iterating when the requested surface is implemented and its material usability and visual issues are resolved; report any unavailable runtime checks honestly.
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.
- 4d ago Changed · -198 lines · -21 tokens per session 0974b46ce3fc
- 11d ago First seen · 228 lines · 40 tokens per session scan A b1899fd7d721
design-taste-frontend is a skill published in the GitHub repository tutur3u/platform (53 stars, last pushed today), licensed Apache-2.0. It adds 19 tokens to every session and 333 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 97% identical to design-taste-frontend-v1, differing in 243 lines, and is treated as a copy.
Other skills, from other repositories
magic-ui
Use this skill when users want to add, customize, or troubleshoot Magic UI components in React/Next.js projects. It covers component selection, shadcn registry installation (@magicui/), integration patterns, and practical quality checks for accessibility and maintainability.
frontend-engineer
!cat skills/shared/protocols/ux-protocol.md 2>/dev/null || true !cat skills/shared/protocols/input-validation.md 2>/dev/null || true !cat skills/shared/protocols/tool-efficiency.md 2>/dev/null || true !cat .production-grade.yaml 2>/dev/null || echo "No config — using defaults" !cat .forgewright/codebase-context.md…
shadcn
Manages shadcn components and projects — adding, searching, fixing, debugging, styling, and composing UI, including chat interfaces. 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…
ui-beats
Use this skill when users want to add, customize, or troubleshoot UI Beats components in React/Next.js projects. It covers component selection, shadcn registry installation from uibeats.com, the UI Beats MCP server, motion and reduced-motion handling, and integration patterns for animated sections.
a11y-component-audit
Audit UI components for WCAG 2.1/2.2 AA conformance: ARIA patterns, keyboard navigation, color contrast, and accessibility evidence block.
a11y-aria-patterns
Reference for ARIA roles, patterns, and forbidden anti-patterns for common UI primitives (button, modal, tabs, combobox, etc.).