design-taste-frontend

Generates anti-generic frontend designs for landing pages, portfolios, and redesigns using inferred design direction.

Updated Jul 2, 2026
One-click install
npx skills add https://github.com/daxrpm/epn-tracker --skill design-taste-frontend-daxrpm
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: design-taste-frontend
Source: https://github.com/daxrpm/epn-tracker/tree/main/.claude/skills/taste-skill
Command: npx skills add https://github.com/daxrpm/epn-tracker --skill design-taste-frontend-daxrpm

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? LLM-generated frontend code tends to look templated and generic, repeating the same purple gradients, centered heroes, and default font choices. This Skill forces the agent to read the brief first, infer the right design direction, and ship interfaces that avoid recognizable AI design clichés. ## Core Features & Use Cases - Brief Inference and Design Read: Analyzes page kind, vibe words, references, audience, and constraints before writing code, then declares a one-line design read. - Three-Dial Configuration: Tunes DESIGN_VARIANCE, MOTION_INTENSITY, and VISUAL_DENSITY based on the brief, with presets for SaaS landings, portfolios, editorial sites, and public-sector services. - Design System Mapping: Selects official design systems (Fluent, Material, Carbon, Polaris, GOV.UK, shadcn/ui, Tailwind v4) when the brief matches, instead of hand-rolling CSS. - Pre-Flight Audits: Enforces hard rules on hero layout, eyebrow restraint, CTA contrast, palette consistency, and section-layout diversity before shipping. - Use Case: Ask for a redesign of a premium consumer brand landing page and receive a React/Tailwind implementation with a deliberate non-default palette, real imagery, and a passed pre-flight checklist. ## Quick Start Redesign my landing page using the design-taste-frontend skill so it does not look like a generic AI template.

Frequently Asked Questions about design-taste-frontend

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I make AI-generated landing pages not look generic?▼

Start with a brief inference step that identifies page kind, audience, and vibe before writing code. Then configure variance, motion, and density dials, avoid default palettes like AI-purple gradients, and run a pre-flight audit on hero layout, eyebrows, and CTA contrast.

What design system should I use for a SaaS landing page?▼

For modern SaaS marketing sites, Tailwind v4 utilities with shadcn/ui components is the default recommendation. For enterprise contexts, use official systems like Fluent UI for Microsoft-style products or Carbon for IBM-style B2B analytics.

Does this skill work with Next.js and React Server Components?▼

Yes, it defaults to React or Next.js with Server Components. Interactive components using Motion or scroll listeners must be isolated client components with 'use client', while server components render static layouts only.

When should I use serif fonts in web design?▼

Serif fonts are discouraged as a default and only appropriate when the brand brief explicitly names a serif or the aesthetic is genuinely editorial, luxury, or heritage. For most creative and premium briefs, sans-serif display fonts like Geist Display or Cabinet Grotesk are the correct default.

What are the limitations of this frontend design skill?▼

The skill explicitly excludes dashboards, data tables, and multi-step product UI, focusing only on landing pages, portfolios, and redesigns. It also requires real image assets or generation tools, since text-only pages are treated as incomplete work.