design-taste-frontend

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

Updated Aug 31, 2026
One-click install
npx skills add https://github.com/keefhub/travel-expense --skill design-taste-frontend-keefhub
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: design-taste-frontend
Source: https://github.com/keefhub/travel-expense/tree/main/.agents/skills/design-taste-frontend
Command: npx skills add https://github.com/keefhub/travel-expense --skill design-taste-frontend-keefhub

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? AI-generated frontend code tends to fall back on the same templated look: purple gradients, centered heroes, three equal feature cards, and Inter on slate. This Skill forces the agent to read the brief first, infer the right design direction, and apply explicit anti-default rules so landing pages, portfolios, and redesigns do not look machine-generated. ## Core Features & Use Cases - Brief Inference and Design Read: Analyzes page kind, vibe words, references, audience, and constraints, then declares a one-line design read before writing any code. - Three-Dial Configuration: Sets DESIGN_VARIANCE, MOTION_INTENSITY, and VISUAL_DENSITY from signal tables and use-case presets to drive layout, motion, and density decisions. - Design System Mapping: Routes briefs to official packages (Fluent, Material, Carbon, Polaris, GOV.UK, shadcn/ui, Tailwind v4) instead of hand-rolled imitations, with honesty rules for aesthetics like glassmorphism and bento. - Bias-Correction Directives: Enforces typography discipline, color calibration with palette-rotation rules, layout diversification, accessibility contrast checks, and a mechanical pre-flight audit. - Use Case: Ask the agent to redesign a premium consumer brand landing page; it will declare a design read, pick a non-default palette family, generate real image assets, and ship a page that passes the eyebrow-count, CTA-intent, and contrast pre-flight checks. ## Quick Start Ask the agent to design a landing page or portfolio from your brief and let it state its design read before generating the interface.

Frequently Asked Questions about design-taste-frontend

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I stop AI-generated landing pages from looking templated?

Start with a brief inference step that reads page kind, vibe words, audience, and constraints before writing code. Then set explicit variance, motion, and density dials and enforce anti-default rules banning purple gradients, centered heroes, and generic card grids.

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

Match the system to the brief: Fluent for Microsoft-style enterprise, Carbon for IBM-style analytics, shadcn/ui or Tailwind v4 for modern SaaS marketing. Use the official package rather than recreating its CSS by hand, and never mix two systems in one project.

Does this approach work with Next.js and Tailwind?

Yes, the default stack is React or Next.js with Server Components, Tailwind v4 via @tailwindcss/postcss, Motion for animation, and next/font for typography. Interactive components must be isolated client components using useMotionValue instead of useState for continuous values.

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, default to sans display fonts like Geist Display or Cabinet Grotesk, and use italic or bold of the same family for emphasis.

Why do AI-built sites fail accessibility contrast checks?

Common failures include white text on white buttons, ghost buttons over photos without scrims, and low-contrast form placeholders. The pre-flight audit requires WCAG AA ratios of 4.5:1 for body text and 3:1 for large text on every button and form before shipping.

What are the limitations of this design skill?

It targets landing pages, portfolios, and redesigns, not dashboards, data tables, or multi-step product UI. It also depends on available image-generation tools or real photography sources; without them it leaves labeled placeholder slots rather than fake screenshot divs.