design-taste-frontend

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

Updated Oct 7, 2022
One-click install
npx skills add https://github.com/tamagusko/linux-cfg --skill design-taste-frontend-tamagusko
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: design-taste-frontend
Source: https://github.com/tamagusko/linux-cfg/tree/main/dotfiles/claude/skills/design-taste-frontend
Command: npx skills add https://github.com/tamagusko/linux-cfg --skill design-taste-frontend-tamagusko

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? AI-generated frontend code tends to look templated: purple gradients, centered heroes, three equal cards, and the same fonts on every project. This Skill forces the agent to read the brief first, infer the right design direction, and apply strict layout, typography, color, and accessibility rules so the output does not look like generic AI 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 read 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: Selects official packages (Fluent, Material, Carbon, shadcn/ui, Tailwind v4, GOV.UK) when the brief matches a real system, and gives honest implementation guidance for aesthetics like glassmorphism, bento, and brutalism. - Hard Layout and A11y Rules: Enforces hero viewport fit, eyebrow restraint, CTA contrast checks, single-accent color locks, and a mechanical pre-flight audit before shipping. - Use Case: Ask for a redesign of a premium cookware landing page and receive a React/Tailwind implementation that avoids the banned beige-and-brass palette, uses real generated imagery, and passes the pre-flight checklist. ## Quick Start Use the design-taste-frontend skill to build a landing page for my SaaS product with a Linear-style minimalist feel.

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 writing code. Then set variance, motion, and density dials, avoid default patterns like purple gradients and centered heroes, and run a pre-flight audit of layout and contrast rules.

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, and 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 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 serif fonts 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 premium consumer brands, 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, ghost buttons over photos without scrims, and low-contrast form placeholders. The fix is a mandatory audit: every CTA must meet WCAG AA contrast (4.5:1 for body text, 3:1 for large text) before shipping.

What are the limitations of this frontend design approach?

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, pages ship with labeled placeholder slots instead of fake CSS illustrations.