design-taste-frontend

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

Updated Jun 9, 2026
One-click install
npx skills add https://github.com/timikalo7/Execute --skill design-taste-frontend-timikalo7
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: design-taste-frontend
Source: https://github.com/timikalo7/Execute/tree/main/.claude/skills/design-taste-frontend
Command: npx skills add https://github.com/timikalo7/Execute --skill design-taste-frontend-timikalo7

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 infer the right design direction from the brief before writing code, then enforces concrete layout, typography, color, and accessibility rules so the output does not look like AI slop. ## Core Features & Use Cases - Brief Inference and Design Read: Reads page kind, vibe words, references, audience, and constraints from the brief, then declares a one-line design direction before generating any code. - Three-Dial Configuration: Maps the design read to DESIGN_VARIANCE, MOTION_INTENSITY, and VISUAL_DENSITY values that gate every layout, motion, and density decision. - Design System Mapping: Selects official packages (Fluent, Material, Carbon, Polaris, shadcn/ui, Tailwind v4, govuk-frontend) when the brief matches a real system, and gives honest implementation guidance for aesthetics like glassmorphism, bento, and brutalism. - Hard Pre-Flight Rules: Enforces hero viewport fit, eyebrow restraint, CTA contrast and wrap checks, palette locks, zigzag caps, and real-image requirements before shipping. - Use Case: Ask for a premium consumer landing page and receive a React/Next.js page with a deliberate non-default palette, asymmetric layout, real generated imagery, and a passing accessibility audit instead of the usual beige-and-brass template. ## Quick Start Ask the agent to design and build a landing page or portfolio from your brief, including any vibe words, reference links, and brand assets you have.

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 reads page kind, vibe words, references, and audience before coding. Then set variance, motion, and density dials and enforce anti-default rules for fonts, colors, and layouts so the output avoids generic AI patterns.

What design system should I use for a React landing page?

Match the system to the brief: shadcn/ui or Tailwind v4 for modern SaaS, Fluent for Microsoft-style enterprise, Carbon for IBM-style B2B, govuk-frontend for UK public sector. Use one official system per project rather than recreating its CSS by hand.

Does this approach work with Next.js Server Components?

Yes, the default stack is Next.js with React Server Components for static layouts. Any component using Motion, scroll listeners, or pointer physics must be an isolated leaf with 'use client' at the top, and global state providers must be wrapped in a client component.

When should I use a serif font 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 a sans display font like Geist Display or Cabinet Grotesk instead.

Why do AI-built sites fail accessibility contrast checks?

Common failures include white text on white buttons, light placeholders on near-white forms, and ghost buttons over photos without a scrim. Audit every CTA and form against WCAG AA ratios (4.5:1 for body text, 3:1 for large text) before shipping.

What are the limitations of this frontend design approach?

It is scoped to landing pages, portfolios, editorial sites, and redesigns, not dashboards, data tables, or multi-step product UI. It also depends on available image-generation tools or real photography sources, since text-only pages are treated as incomplete work.