design-taste-frontend

Generates landing pages, portfolios, and redesigns with brief-driven design direction and anti-default rules.

7|3|Updated Jun 19, 2026
One-click install
npx skills add https://github.com/JXW666NB/K4-ULTRA --skill design-taste-frontend-jxw666nb
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: design-taste-frontend
Source: https://github.com/JXW666NB/K4-ULTRA/tree/main/.trae/skills/design-taste-frontend
Command: npx skills add https://github.com/JXW666NB/K4-ULTRA --skill design-taste-frontend-jxw666nb

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? AI-generated frontend code tends to look templated: purple gradients, centered heroes, three equal feature cards, and generic glassmorphism. This Skill forces the agent to read the brief first, infer the right design direction, and ship interfaces that avoid recognizable LLM defaults. ## Core Features & Use Cases - Brief Inference & Design Read: Analyzes page kind, vibe words, references, audience, and constraints before writing code, then declares a one-line design read. - 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: Selects official packages (Fluent, Material, Carbon, shadcn/ui, Tailwind v4, GOV.UK) when the brief matches a real system, and gives honest implementations for aesthetics like glassmorphism, bento, and brutalism. - Pre-Flight Layout Rules: Enforces hard constraints on hero sizing, eyebrow frequency, CTA contrast, bento rhythm, and section-layout diversity. - Use Case: Ask for a redesign of a premium cookware landing page and receive a React/Tailwind implementation with a non-default palette, asymmetric layout, real image assets, and audited accessibility. ## Quick Start Ask the agent to design a landing page or portfolio from your brief, including any vibe words, reference sites, 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 identifies page kind, audience, and vibe before coding. Then configure variance, motion, and density dials, avoid default palettes like AI-purple gradients, and enforce layout rules such as asymmetric heroes and limited eyebrow labels.

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

For modern SaaS marketing, Tailwind v4 utilities with a dark variant is the default. If the brief matches an established ecosystem, use official packages like shadcn/ui, Radix Themes, Fluent, or Carbon instead of recreating their CSS by hand.

Does this approach work with Next.js Server Components?

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

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 and portfolios, sans-serif display fonts like Geist Display 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. The skill mandates WCAG AA audits of every CTA and form before shipping, requiring 4.5:1 contrast for body text.

What are the limitations of this frontend design skill?

It explicitly excludes dashboards, data tables, and multi-step product UI, focusing only on landing pages, portfolios, and redesigns. It also requires real image assets or generation tools, since text-only pages are treated as incomplete work.