design-taste-frontend

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

3|Updated Apr 25, 2026
One-click install
npx skills add https://github.com/cherishwins/npsi-site --skill design-taste-frontend-cherishwins
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: design-taste-frontend
Source: https://github.com/cherishwins/npsi-site/tree/main/.agents/skills/design-taste-frontend
Command: npx skills add https://github.com/cherishwins/npsi-site --skill design-taste-frontend-cherishwins

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? LLM-generated frontend code tends to fall back on the same templated aesthetic: AI-purple gradients, centered heroes, three equal feature cards, and Inter everywhere. This Skill forces the agent to read the brief first, infer the right design direction, and ship interfaces that look deliberately designed rather than auto-generated. ## 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 to anchor all decisions. - Three-Dial Configuration: Tunes DESIGN_VARIANCE, MOTION_INTENSITY, and VISUAL_DENSITY based on the brief, mapping signals like "minimalist" or "Awwwards" to concrete layout, motion, and density values. - Design System Mapping and Bias Correction: Selects official design systems (Fluent, Material, Carbon, shadcn/ui, Tailwind v4) when appropriate, and enforces anti-slop rules covering typography, color palettes, hero layout discipline, eyebrow restraint, and CTA contrast. - Use Case: A user asks for a premium consumer cookware landing page. The Skill blocks the default beige-and-brass palette, picks an alternative family like Cobalt + Cream, sets dials to 7/6/3, and ships a Tailwind v4 page with real generated imagery and a pre-flight audit. ## Quick Start Redesign my SaaS landing page so it feels Linear-style minimalist and 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 templated?▼

Start with a brief inference step that identifies page kind, audience, and vibe before writing code. Then set variance, motion, and density dials, avoid default patterns like purple gradients and centered heroes, and run a pre-flight audit on typography, color, and layout.

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

For modern SaaS where you own the components, use shadcn/ui or Tailwind v4 utilities. For enterprise contexts, reach for official packages like Fluent UI, Carbon, or Material 3 rather than recreating their CSS by hand.

When should I use serif fonts in web design?▼

Serif is appropriate only when the brand brief names a serif font or the aesthetic is genuinely editorial, luxury, or heritage. For creative agencies, portfolios, and modern brands, default to sans-serif display fonts like Geist Display or Cabinet Grotesk.

Does this approach work with Next.js and Tailwind?▼

Yes, the default stack is React or Next.js with Server Components, Tailwind v4 for styling, and Motion for animation. Interactive components must be isolated client components, and continuous values like scroll progress use useMotionValue instead of useState.

Why do AI-generated websites all use the same beige and brass palette?▼

LLMs default to warm cream backgrounds with brass accents for premium-consumer briefs, making brands indistinguishable. The fix is rotating through alternative families like Cold Luxury, Forest, Cobalt + Cream, or monochrome with a single saturated accent.

What are the limits of this frontend design approach?▼

It targets landing pages, portfolios, and redesigns, not dashboards, data tables, or multi-step product UI. Rules are contextual rather than automatic, so the agent must infer the design read correctly before any rule fires.