agentleFS
VinayKhandiaVinayKhandia/no-slop/skills/design-taste/SKILL.md

design-taste

Skill1 starsChanged 12 days agoMITView on GitHub

Use before building any website, landing page, portfolio or UI. Chooses a concept, a design style that fits the product, palette, type and layout. Prevents generic template output.

21 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use slides and design-review.

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.
  • JetBrainsSkill

    slides

    Create and edit presentation slide decks (`.pptx`) with PptxGenJS and render/validation utilities. Use when tasks involve building a new PowerPoint deck, recreating slides from screenshots/PDFs/reference decks, modifying slide content while preserving editable output, adding charts/diagrams/visuals, or diagnosing layout issues such as overflow, overlaps, and font substitution.

    Also in 3 projects that use this

  • dillonluiSkill

    design-review

    Review a view or flow for UX and UI issues. Provides severity-ranked, actionable findings grounded in established design heuristics. Use when the user asks for design feedback, UX review, or UI critique.

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 18 edited versions we read keep these.

  • 5

    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:

    Run first for any UI task.

    line 8
  2. Distinctive:

    If the concept fits any other business, rewrite it.

    line 12
  3. Distinctive:

    Write 2 lines in DESIGN.md on why this style fits the audience and product.

    line 16
  4. Distinctive:

    Start from the palette family in the style recipe, then adapt it to the product's real materials.

    line 43
  5. Distinctive:

    Never repeat a three-equal-cards row.

    line 59

“Common” is measured: kept by at least 6 in 10 of the 18 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

Design Taste

Run first for any UI task. Output goes to DESIGN.md (max 70 lines). Then load motion-craft, and scene-3d if 3D applies.

1. Concept

  • One sentence: the central metaphor plus one signature moment only this product could have.
  • If the concept fits any other business, rewrite it.

2. Commit to a style (required)

  • Pick ONE primary style from the table. A second style may add ONE trait only (example: Editorial with a Swiss grid). The primary must be visibly dominant in the first screenshot.
  • Write 2 lines in DESIGN.md on why this style fits the audience and product.
  • Open references/styles/<style>.md and follow that recipe literally for palette family, type, layout, motion, 3D environment, cursor and copy tone. Load only that one file.
  • Choose the background mode on purpose: light, mid-tone or dark. Dark is right only for Dark luxe, nightlife, cinema and some dev tools. Food, hospitality, wellness, kids, fashion and culture default to light or mid-tone.
  • Copy tone follows the style (editorial reads like a magazine, swiss is terse and factual). No lab, telemetry or HUD jargon unless the product is technical.
StyleBest forSignature traits
Editorialcafes, fashion, magazines, portfolioshuge serif/grotesk headlines, image-text overlap, captions, numbered sections
Swiss / Internationalagencies, tools, architecturestrict grid, flush-left type, 2 colors, big numerals, lots of white
Minimalismpremium products, SaaSone idea per screen, tiny palette, massive spacing, slow motion
Maximalismfestivals, music, creative studioslayered textures, clashing type, dense collage, loud color
Surrealart, experiences, perfume, gamesimpossible scale, floating objects, dreamy gradients, distorted perspective
Y2K / Retro-futureyouth brands, music, fashionchrome, bubbles, gradients, pixel/techno type, sticker shapes
Glassmorphismfintech, dashboards, weather, appsfrosted panels over rich color, soft borders, depth (use sparingly, blur is costly)
Neo-brutalismstartups, indie tools, edgy brandsthick borders, flat hard shadows, raw type, bold flat color
Organic / Tactilefood, wellness, craft, kidssoft shapes, grain, warm tones, clay-like 3D, hand-made feel
Dark luxewatches, cars, spirits, nightlifenear-black base, one metallic accent, cinematic lighting, slow reveals
Retro-print / Vintagebakeries, barbers, breweriespaper texture, stamps, limited ink colors, badges

Selection rules:

  • Match the audience first, trend second.
  • Food/drink/hospitality: lean Editorial, Organic/Tactile, Retro-print or Surreal.
  • Dev tools/data: Swiss, Minimalism, Neo-brutalism.
  • Entertainment/youth: Maximalism, Y2K, Surreal.
  • Luxury: Dark luxe, Minimalism.

3. Palette

  • Start from the palette family in the style recipe, then adapt it to the product's real materials. Max 5 colors with hex and role: background, surface, text, accent, object-contrast.
  • The first palette that comes to mind for the industry is banned (coffee: dark brown + orange + cream, fintech: navy + teal, fitness: black + neon). Use the second or third idea.
  • The 3D hero is the brightest or most saturated thing against the background. Environment colors come from the same palette.
  • About 60% background, 30% surface and text, 10% accent.
  • Banned: black background + single orange or blue accent, purple-blue gradients, pure #000 and #fff.
  • Text contrast at least 4.5:1. Squint test: you should still see three distinct zones (background, object, text).

Names are not palette briefs. A brand or product name (Noir, Sunrise, Ember, Forest) suggests a color; that is the first idea and is never the default. Gates 1 and 2 always offer three palettes, labeled: Literal (what the name suggests), Opposite (a contrasting mode or hue family), and Unexpected (derived from the product's real materials or setting). At least one of the three must have a light or mid-tone background unless the user asked for dark. Never mark the Literal one as recommended. At Gate 1 also ask the darkness dial in one line (1 light to 5 dark).

4. Typography

  • One display font and one body font from Google Fonts. Name both.
  • Banned as display: Inter, Roboto, Arial, system-ui.
  • Display size fluid with clamp(), hero at least 8vw on desktop. Mix scale boldly (tiny labels next to giant headlines).

5. Layout

  • Asymmetry, overlap, big whitespace or deliberate density (per style).
  • Never repeat a three-equal-cards row. Each section uses a different layout idea.
  • Content sits over the 3D scene, never in a separate boring block.

6. DESIGN.md format

Concept / Signature moment / Style (primary, secondary, why) / Palette table / Fonts / Section list with layout + motion idea per section / zones per section (object side, text side).

7. Final check

  • Style chosen with a reason, max two.
  • Palette has no banned defaults.
  • Concept is specific.
  • motion-craft and scene-3d checks also pass (if applicable).
  • Style recipe file was loaded and followed
  • Background mode chosen on purpose

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.