agentleFS
Sign inStart free
mihaimurra001mihaimurra001/preConfigProject/.agents/skills/design-taste-frontend/SKILL.md

design-taste-frontend

Skill1 starsChanged 2 months agoMITView on GitHub

Anti-slop frontend skill for landing pages, web apps, and redesigns. Infers design direction, enforces real design systems, and prevents generic AI aesthetic.

182 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use stitch-design-taste, design-taste-frontend-v1 and 10 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.
  • HK-hubSkill

    stitch-design-taste

    Semantic Design System Skill for Google Stitch. Generates agent-friendly DESIGN.md files that enforce premium, anti-generic UI standards — strict typography, calibrated color, asymmetric layouts, perpetual micro-motion, and hardware-accelerated performance.

    Also in 59 projects that use this

  • HK-hubSkill

    design-taste-frontend-v1

    The original v1 taste-skill, preserved for projects depending on its exact behavior. The current default is `design-taste-frontend` (v2 experimental), which is a substantial rewrite. Use this v1 install name only if you need exact backward compatibility.

    Also in 29 projects that use this

  • UtkarshDubeyGITSkill

    firecrawl-website-design-clone

    Extract any website's design system into an agent-ready DESIGN.md using Firecrawl scrape evidence. Use when the user wants colors, fonts, spacing, components, layout patterns, or brand/UI guidance from a website so AI agents can create new websites, clone a look, or build pages inspired by that design.

    Also in 3 projects that use this

  • hjdspaceSkill

    flutter-setup-declarative-routing

    Configure `MaterialApp.router` using a package like `go_router` for advanced URL-based navigation. Use when developing web applications or mobile apps that require specific deep linking and browser history support.

    Also in 3 projects that use this

  • hjdspaceSkill

    flutter-setup-localization

    Add `flutter_localizations` and `intl` dependencies, enable "generate true" in `pubspec.yaml`, and create an `l10n.yaml` configuration file. Use when initializing localization support for a new Flutter project.

    Also in 3 projects that use this

  • LangChainSkill

    embedded-captions

    Add captions or subtitles to an existing single-subject talking-head video without editing the footage. Use for plain verbatim captions, cinematic captions embedded behind the subject, VFX captions, “炸/特效/酷炫字幕,” or a named identity from the 35-style catalog. Route by visual identity, not by backend engine. The quiet `anchor` rail is the default; embed every word only when the user explicitly wants a fully cinematic treatment. The workflow runs locally end to end, including transcription and subject matting; split multi-shot footage before applying it.

    Also in 5 projects that use this

  • +3 more from hjdspace

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 178 edited versions we read keep these.

  • 2

    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:

    Before generating UI or tweaking CSS, apply the Anti-Default Discipline:

    line 8
  2. Distinctive:

    NO Generic AI Tells: Do NOT default to AI-purple gradients, centered hero over dark mesh, 3 identical feature cards, generic glassmorphism, …

    line 11

“Common” is measured: kept by at least 6 in 10 of the 178 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: Anti-Slop Frontend Engineering

Before generating UI or tweaking CSS, apply the Anti-Default Discipline:

1. Anti-Default Rules

  • NO Generic AI Tells: Do NOT default to AI-purple gradients, centered hero over dark mesh, 3 identical feature cards, generic glassmorphism, or Inter + slate-900.
  • The Three Dials:
    • DESIGN_VARIANCE (1 = Strict Symmetry, 10 = High Editorial / Expressive)
    • MOTION_INTENSITY (1 = Static / Restrained, 10 = Fluid Physics)
    • VISUAL_DENSITY (1 = Airy / Gallery, 10 = Information-Dense Dashboard)
  • Design Read First: Declare a 1-line design read before coding: "Reading this as: [page kind] for [audience], with [vibe] language, leaning toward [design system]."

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.

Check your setup, free