design-taste-frontend

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

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? LLM-generated frontend code tends to look templated and generic, with default purple gradients, centered heroes, and repetitive card layouts. This Skill forces the agent to read the brief first, infer the right design direction, and apply strict anti-default rules before writing any code. ## Core Features & Use Cases - Brief Inference and Design Read: Analyzes page kind, vibe words, references, audience, and constraints, then declares a one-line design direction before generating 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: Routes briefs to official packages like Fluent UI, Material 3, Carbon, GOV.UK Frontend, shadcn/ui, or Tailwind v4 instead of hand-rolled imitations. - Pre-Flight Audits: Enforces hard rules on hero layout, eyebrow restraint, CTA contrast, palette consistency, and section-layout diversity before shipping. - Use Case: Ask for a redesign of a premium cookware landing page and receive a React/Tailwind implementation with a deliberate non-default palette, real image assets, and a layout that passes the audit checklist. ## Quick Start Use the design-taste-frontend skill to build a landing page for my B2B 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 by inferring the design direction from the brief: page kind, vibe words, audience, and references. Then set variance, motion, and density dials and enforce anti-default rules that ban purple gradients, centered heroes, and repetitive card grids.

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

For modern SaaS marketing sites, Tailwind v4 utilities with shadcn/ui components are the default. Enterprise briefs map to official systems like Fluent UI, Carbon, or Material 3, and public-sector sites use GOV.UK Frontend or USWDS.

Does this skill work with Next.js and React Server Components?

Yes, it defaults to React or Next.js with Server Components. Interactive components using Motion, scroll listeners, or pointer physics must be isolated client components with 'use client', and continuous values use useMotionValue instead of useState.

When should I not use this frontend design skill?

It is scoped to landing pages, portfolios, and redesigns, not dashboards, data tables, or multi-step product UI. For dense application interfaces, use a component-driven design system workflow instead.

Why does my AI-generated hero section look broken on mobile?

Common causes are using h-screen instead of min-h-[100dvh], oversized headline fonts, and excessive top padding. The skill caps hero top padding at pt-24, limits headlines to two lines, and requires explicit mobile collapse rules per section.