design-taste-frontend

Concise, distinctive landing pages and portfolios that avoid templated AI aesthetics.

leonxlnx ↓ 280k
Claude Code
View source ↗

What it does

  • "Reading this as: redesign of a public-sector service site, with a trust-first language, leaning toward GOV.UK Frontend or USWDS."
  • DESIGNVARIANCE: 8 - 1 = Perfect Symmetry, 10 = Artsy Chaos
  • MOTIONINTENSITY: 6 - 1 = Static, 10 = Cinematic / Physics
  • VISUALDENSITY: 4 - 1 = Art Gallery / Airy, 10 = Cockpit / Packed Data
  • Framework: React or Next.js. Default to Server Components (RSC).
  • RSC SAFETY: Global state works ONLY in Client Components. In Next.js, wrap providers in a "use client" component.
  • Styling: Tailwind v4 (default). Tailwind v3 only if the existing project demands it.

Requirements & configuration

  • Discouraged: lucide-react. Acceptable only when the user explicitly asks for it or the project already depends on it.
  • What to do instead of an eyebrow: drop it entirely. The headline alone is enough. If you need to categorize a section, the section's location on the page already categorizes it; no label needed.
  • Div-based fake screenshots are banned. A "hand-built product preview" rendered with <div> rectangles, fake task lists, fake dashboards, fake terminal windows is a Tell. If you need to show a product:
  • Hero needs a real visual. Text + gradient blob is not a hero - it's a placeholder.
  • Long lists need a different UI component, not a longer list. Default <ul> with bullets / divide-y rows is the lazy choice. If you have > 5 items, reach for one of these instead:

Configuration: DESIGN_VARIANCEMOTION_INTENSITYVISUAL_DENSITYLAYOUT_VARIANCEANIM_LEVELFOURSELECTEDBETA

Derived from the skill's own SKILL.md documentation · extracted 2026-07-23

Concise, distinctive landing pages and portfolios that avoid templated AI aesthetics.

Source

Repository: https://github.com/leonxlnx/taste-skill

design-taste-frontend FAQ

What does the design-taste-frontend skill do?

Anti-slop frontend skill for landing pages, portfolios, and redesigns. The agent reads the brief, infers the right design direction, and ships interfaces that do not look templated. Real design systems when applicable, audit-first on redesigns, strict pre-flight check. "Reading this as: redesign of a public-sector service site, with a trust-first language, leaning toward GOV.UK Frontend or USWDS." DESIGNVARIANCE: 8 - 1 = Perfect Symmetry, 10 = Artsy Chaos

What does design-taste-frontend require?

Discouraged: lucide-react. Acceptable only when the user explicitly asks for it or the project already depends on it. What to do instead of an eyebrow: drop it entirely. The headline alone is enough. If you need to categorize a section, the section's location on the page already categorizes it; no label needed. Div-based fake screenshots are banned. A "hand-built product preview" rendered with <div> rectangles, fake task lists, fake dashboards, fake terminal windows is a Tell. If you need to show a product: Hero needs a real visual. Text + gradient blob is not a hero - it's a placeholder. Long lists need a different UI component, not a longer list. Default <ul> with bullets / divide-y rows is the lazy choice. If you have > 5 items, reach for one of these instead: Configuration keys: DESIGN_VARIANCE, MOTION_INTENSITY, VISUAL_DENSITY, LAYOUT_VARIANCE, ANIM_LEVEL, FOUR, SELECTED, BETA.

How do I install design-taste-frontend?

Run: npx -y skills add https://github.com/leonxlnx/taste-skill --skill design-taste-frontend --agent claude-code — the source lives at github.com/leonxlnx/taste-skill.

Maintain design-taste-frontend?

Let people know it's listed here — add the badge (live metrics, light/dark aware) or a plain link to your README or docs.

design-taste-frontend on getagentictools
[![design-taste-frontend on getagentictools](https://getagentictools.com/badge/skills/leonxlnx-taste-skill-design-taste-frontend.svg)](https://getagentictools.com/skills/leonxlnx-taste-skill-design-taste-frontend?ref=badge)
npx agentictools info skills/leonxlnx-taste-skill-design-taste-frontend

The second line is the CLI lookup for this page — handy in READMEs and docs.