agentleFS
HarambeeAIHarambeeAI/bayes-ship/skills/taste-skill/SKILL.md

taste-skill

Skill1 starsChanged 7 months agoMITView on GitHub

Premium frontend design skill: layout, typography, colors, spacing, and motion. Prevents generic AI-generated UI. Auto-invoked when building any frontend component. Source: Leonxlnx/taste-skill. Has 3 tunable settings: DESIGN_VARIANCE, MOTION_INTENSITY, VISUAL_DENSITY.

15 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use animation-vocabulary, apple-design and 6 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • attentiondotnetSkill

    animation-vocabulary

    Reverse-lookup glossary that turns a vague description of a web animation or motion effect into its exact term ("the bouncy thing when a popover opens" → Pop in; "the iOS rubber-band scroll" → Rubber-banding). Use when the user asks "what's it called when…", or describes a motion effect without knowing its name and wants the right word to prompt an AI or designer with. For naming an effect, not designing or building one.

    Also in 3 projects that use this

  • ozgureyilmazSkill

    apple-design

    Apple's approach to interface design and fluid, physical motion, translated for the web. Use when building or reviewing gesture-driven UI, spring animations, drag/swipe/sheet interactions, momentum and interruptible transitions, translucent materials and depth, typography (optical sizing, tracking, leading), reduced-motion, or the design foundations (feedback, spatial consistency, restraint) behind Apple-style interfaces.

    Also in 3 projects that use this

  • VercelSkill

    emil-design-eng

    This skill encodes Emil Kowalski's philosophy on UI polish, component design, animation decisions, and the invisible details that make software feel great.

    Also in 3 projects that use this

  • VercelSkill

    web-design-guidelines

    Review UI code for Web Interface Guidelines compliance. Use when asked to "review my UI", "check accessibility", "audit design", "review UX", or "check my site against best practices".

    Also in 4 projects that use this

  • GoogleSkill

    prototype

    Build a throwaway prototype to answer a design question. Use when the user wants to sanity-check whether a state model or logic feels right, or explore what a UI should look like.

    Also in 4 projects that use this

  • StrayDragonSkill

    ui-ux-pro-max

    UI/UX design intelligence. 50 styles, 21 palettes, 50 font pairings, 20 charts, 8 stacks (React, Next.js, Vue, Svelte, SwiftUI, React Native, Flutter, Tailwind). Actions: plan, build, create, design, implement, review, fix, improve, optimize, enhance, refactor, check UI/UX code. Projects: website, landing page, dashboard, admin panel, e-commerce, SaaS, portfolio, blog, mobile app, .html, .tsx, .vue, .svelte. Elements: button, modal, navbar, sidebar, card, table, form, chart. Styles: glassmorphism, claymorphism, minimalism, brutalism, neumorphism, bento grid, dark mode, responsive, skeuomorphism, flat design. Topics: color palette, accessibility, animation, layout, typography, font pairing, spacing, hover, shadow, gradient.

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

7 rules. 0 are common, 7 are distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 14 edited versions we read keep these.

  • 7

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Never center everything. Create visual hierarchy through asymmetry and intentional alignment.

    line 15
  2. Distinctive:

    Use a grid system (12-column or custom).

    line 16
  3. Distinctive:

    Never use font weights below 400 for body text.

    line 26
  4. Distinctive:

    Use HSL for consistency. Adjust lightness for variants, keep hue constant.

    line 32
  5. Distinctive:

    Never use pure black (#000) on pure white (#fff).

    line 34
  6. Distinctive:

    Use a spacing scale (4, 8, 12, 16, 24, 32, 48, 64, 96).

    line 38
  7. Distinctive:

    Never animate layout properties (width, height, top, left).

    line 47

“Common” is measured: kept by at least 6 in 10 of the 14 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Taste Skill — Premium Frontend Design

Settings (adjust per project)

  • DESIGN_VARIANCE: 5 — How experimental the layout is. (1-3: clean/centered | 8-10: asymmetric/modern)
  • MOTION_INTENSITY: 4 — How much animation. (1-3: simple hover | 8-10: magnetic/scroll-triggered)
  • VISUAL_DENSITY: 5 — Content per screen. (1-3: spacious/luxury | 8-10: dense dashboards)

Layout rules

  • Never center everything. Create visual hierarchy through asymmetry and intentional alignment.
  • Use a grid system (12-column or custom). No arbitrary positioning.
  • Give elements room to breathe. Minimum 24px between unrelated elements.
  • Cards and containers: consistent padding (16px minimum, 24px preferred).
  • Max content width: 1200px for reading content, wider for dashboards.

Typography

  • Maximum 2 font families per project (1 preferred).
  • Establish a type scale: use consistent sizes across the project (e.g., 14, 16, 20, 24, 32, 48).
  • Line height: 1.5 for body text, 1.2 for headings.
  • Never use font weights below 400 for body text.
  • Headings: use size AND weight to establish hierarchy (not just size).

Color

  • Define a palette of 5-7 colors maximum. Primary, secondary, accent, success, warning, error, neutral.
  • Use HSL for consistency. Adjust lightness for variants, keep hue constant.
  • Background hierarchy: use subtle shade differences (not borders) to separate sections.
  • Never use pure black (#000) on pure white (#fff). Soften both: #0f0f0f on #fafafa.

Spacing

  • Use a spacing scale (4, 8, 12, 16, 24, 32, 48, 64, 96).
  • Consistent padding within components. Consistent margins between components.
  • Section spacing: 64px+ between major sections on landing pages.

Motion and animation

  • Entrance animations: fade + slight translate (8-16px). Duration 200-400ms.
  • Hover effects: scale(1.02) or subtle shadow elevation. Duration 150-200ms.
  • Transitions: use ease-out for entrances, ease-in for exits.
  • Never animate layout properties (width, height, top, left). Use transform and opacity.
  • Respect prefers-reduced-motion media query.

Anti-patterns (what makes AI UI look like "slop")

  • Generic centered hero with gradient background — do something interesting
  • Rounded corners on everything with the same radius — vary intentionally
  • Blue/purple default palette — choose colors that match the brand
  • Stock icons with no relationship to the content
  • Equal spacing everywhere — use spacing to create hierarchy
  • "Lorem ipsum" or obviously placeholder content

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.