design-taste-frontend

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

154|27|Updated Aug 3, 2026
One-click install
npx skills add https://github.com/openvetta/open-vetta --skill design-taste-frontend-openvetta
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: design-taste-frontend
Source: https://github.com/openvetta/open-vetta/tree/main/.agents/skills/design-taste-frontend
Command: npx skills add https://github.com/openvetta/open-vetta --skill design-taste-frontend-openvetta

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 card grids. This Skill forces the agent to read the brief first, infer the right design direction, 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, then declares a one-line design direction before writing any 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 Pre-Flight Audit: Selects official design systems (Fluent, Material, Carbon, shadcn/ui, Tailwind v4) when appropriate, enforces anti-default rules for typography, color, and layout, and runs a strict pre-flight check before shipping. - Use Case: Ask the agent to redesign a portfolio homepage; it infers an editorial direction, picks fonts and an accent palette, builds a React/Tailwind layout with real imagery, and audits eyebrow overuse, CTA contrast, and hero overflow before delivering. ## Quick Start Redesign my landing page using the design-taste-frontend skill so it looks custom-designed rather than templated.

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 coding, then set variance, motion, and density dials to match. This Skill bans default patterns like purple gradients, centered heroes, and repeated card grids, and audits the result before shipping.

What design systems does this frontend skill support?▼

It maps briefs to official packages including Fluent UI, Material 3, Carbon, Polaris, Atlassian, Primer, GOV.UK Frontend, USWDS, Bootstrap, Radix Themes, shadcn/ui, and Tailwind v4. Only one system is used per project, and aesthetic trends without official packages are built with native CSS.

Can I use this skill with Next.js and Tailwind CSS?▼

Yes, React and Next.js with Server Components are the default stack, paired with Tailwind v4 via @tailwindcss/postcss and Motion for animation. Interactive components must be isolated client components, and continuous values like scroll progress use useMotionValue instead of useState.

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. For dense application interfaces, a component-library-driven approach with a system like Carbon or Fluent is a better fit.

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. The skill caps hero top padding at pt-24, limits the stack to four text elements, and requires min-h-[100dvh] instead of h-screen to prevent mobile layout jumps.