design-taste-frontend

Generates non-templated frontend designs for landing pages, portfolios, and redesigns using brief inference and design dials.

3|1|Updated Apr 29, 2026
One-click install
npx skills add https://github.com/firstsun-dev/skills --skill design-taste-frontend-firstsun-dev
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: design-taste-frontend
Source: https://github.com/firstsun-dev/skills/tree/main/plugins/frontend-product-design/skills/design-taste-frontend
Command: npx skills add https://github.com/firstsun-dev/skills --skill design-taste-frontend-firstsun-dev

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? AI-generated frontend code tends to look templated and generic, repeating the same gradients, centered heroes, and card grids. This Skill forces the agent to read the brief first, infer the right design direction, and apply disciplined layout, typography, and color rules so landing pages, portfolios, and redesigns do not look like default LLM output. ## Core Features & Use Cases - Brief Inference and Design Read: Analyzes page kind, vibe words, references, audience, and constraints, then declares a one-line design direction before writing code. - 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 and Anti-Slop Rules: Selects official design systems (Fluent, Material, Carbon, shadcn/ui, Tailwind v4) when appropriate and enforces hard pre-flight checks on hero layout, eyebrows, CTAs, contrast, and palette consistency. - Use Case: Ask the agent to redesign a B2B SaaS landing page; it declares a Linear-style minimalist read, sets dials to 5/3/3, builds with Tailwind v4 and Geist, and passes a mechanical pre-flight audit before shipping. ## Quick Start Redesign my SaaS landing page so it looks like a deliberate Linear-style design instead of 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 templated?▼

Start by inferring the design direction from the brief: page kind, vibe words, audience, and references. Then set variance, motion, and density dials and enforce anti-default rules that ban AI-purple gradients, centered heroes, and repetitive card grids.

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

For modern SaaS marketing sites, Tailwind v4 utilities with shadcn/ui components are the default. Enterprise briefs map to official systems like Fluent, Carbon, or Material, and public-sector sites should use GOV.UK Frontend or USWDS.

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

Yes. The default stack is React or Next.js with Server Components for static layouts. Any component using Motion, scroll listeners, or pointer physics must be an isolated client component with 'use client' at the top.

When should I not use this frontend design skill?▼

It is scoped to landing pages, portfolios, and redesigns, not dashboards, data tables, or multi-step product UI. Dense application interfaces need different patterns than the marketing-site rules defined here.

Why does my AI-generated hero section overflow the viewport?▼

Hero overflow happens when headlines exceed two lines or subtext exceeds 20 words at large font scales. Fix it by reducing font scale to text-4xl through text-6xl, cutting copy, and capping hero top padding at pt-24.