design-taste-frontend

Generates non-templated frontend designs for landing pages, portfolios, and redesigns using React and Tailwind.

1|Updated Feb 22, 2026
One-click install
npx skills add https://github.com/TarunTeja44/portfolio --skill design-taste-frontend-tarunteja44
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: design-taste-frontend
Source: https://github.com/TarunTeja44/portfolio/tree/main/.agents/skills/taste-skill
Command: npx skills add https://github.com/TarunTeja44/portfolio --skill design-taste-frontend-tarunteja44

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? AI-generated frontend code tends to look templated and generic, repeating the same purple gradients, centered heroes, and three-card layouts. This Skill forces the agent to infer the right design direction from the brief and apply disciplined layout, typography, color, and motion rules so the output does not look like default LLM slop. ## 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 direction. - 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 pages. - Design System Mapping: Selects official packages like Fluent UI, Carbon, Material, GOV.UK Frontend, or shadcn/ui when the brief matches a real system, and gives honest implementation guidance for aesthetics like glassmorphism, bento, and brutalism. - Pre-Flight Layout Rules: Enforces hard constraints on hero sizing, eyebrow frequency, CTA contrast, bento cell counts, zigzag alternation, and palette consistency. - Use Case: Ask for a redesign of a SaaS landing page and receive a React/Next.js + Tailwind v4 implementation with a declared design read, real image assets, and an audited layout that passes the pre-flight checklist. ## Quick Start Redesign my landing page using the taste 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 look less generic?

Start with a brief inference step that identifies page kind, audience, and vibe before coding, then set variance, motion, and density dials accordingly. Avoid default patterns like purple gradients, centered heroes, and three equal feature cards, and audit the result against a pre-flight checklist.

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. If the brief matches an established product family, use the official package such as Fluent UI, Carbon, Material 3, or Primer instead of recreating its CSS by hand.

Does this skill work with Next.js and Tailwind v4?

Yes, Next.js with React Server Components and Tailwind v4 is the default stack. For Tailwind v4 use @tailwindcss/postcss or the Vite plugin rather than the legacy postcss config, and isolate interactive Motion components as client-side leaves.

When should I use serif fonts in web design?

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

What types of projects is this skill not suited for?

It explicitly excludes dashboards, data tables, and multi-step product UI, which need different density and component patterns. It is scoped to landing pages, portfolios, editorial sites, and redesigns where visual differentiation is the primary goal.