design-taste-frontend

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

Updated Aug 10, 2026
One-click install
npx skills add https://github.com/KryptaMedina7/quero-s-home --skill design-taste-frontend-kryptamedina7
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: design-taste-frontend
Source: https://github.com/KryptaMedina7/quero-s-home/tree/main/.agents/skills/taste-skill
Command: npx skills add https://github.com/KryptaMedina7/quero-s-home --skill design-taste-frontend-kryptamedina7

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 deliberate design decisions by inferring the right aesthetic from the brief before writing any code. ## Core Features & Use Cases - Brief Inference: Reads page kind, vibe words, references, audience, and constraints to declare a one-line design read before generating code. - Three Design Dials: Configures variance, motion intensity, and visual density to drive every layout and animation decision. - Design System Mapping: Selects official packages (Fluent, Material, Carbon, shadcn/ui, Tailwind) or honest custom implementations for aesthetic directions like glassmorphism or brutalism. - Pre-Flight Audits: Enforces hard rules on hero layout, eyebrow restraint, CTA contrast, palette consistency, and section-layout diversity. - Use Case: Ask for a redesign of a real estate landing page and receive a React/Tailwind implementation with a declared design read, a locked accent palette, real image assets, and no AI-default clichés. ## Quick Start Redesign my landing page using the design-taste-frontend skill and state your design read before writing code.

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 explicit dials for design variance, motion intensity, and visual density, and enforce rules against defaults like purple gradients, centered heroes, and repeated card grids.

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

Match the system to the brief: Fluent for Microsoft-style enterprise, Material 3 for Google-flavored UI, Carbon for IBM-style B2B, shadcn/ui or Tailwind v4 for modern SaaS. Use one official system per project rather than hand-rolling its CSS.

Does this approach work with Next.js Server Components?

Yes. Static layouts render as Server Components, while any component using Motion, scroll listeners, or pointer physics must be an isolated client leaf with 'use client'. Global state providers also require a client wrapper.

When should serif fonts be used in web design?

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

Why do AI-built sites fail accessibility contrast checks?

Common failures include white text on white buttons, low-contrast form placeholders, and ghost buttons over photos without scrims. Every CTA and form element must pass WCAG AA ratios of 4.5:1 for body text and 3:1 for large text before shipping.