design-taste-frontend

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

1|Updated Jul 2, 2026
One-click install
npx skills add https://github.com/filippolmt/skills --skill design-taste-frontend-filippolmt
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: design-taste-frontend
Source: https://github.com/filippolmt/skills/tree/main/skills/design-taste-frontend
Command: npx skills add https://github.com/filippolmt/skills --skill design-taste-frontend-filippolmt

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? LLM-generated frontend code tends to fall back on the same templated aesthetic: AI-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 ship landing pages, portfolios, and redesigns that do not look like default AI output. ## 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 and Anti-Slop Rules: Selects official design systems (Fluent, Material, Carbon, shadcn/ui, Tailwind v4) when appropriate, and enforces hard pre-flight rules on typography, color, layout, CTAs, eyebrows, and accessibility contrast. - Use Case: Ask for a premium consumer cookware landing page and get a React/Next.js + Tailwind build with a deliberate palette, asymmetric layout, real image assets, and a passing pre-flight audit instead of the default beige-and-brass template. ## Quick Start Ask the agent to design and build a landing page or portfolio from your brief, for example: "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 stop AI-generated landing pages from looking templated?

Use a brief-inference workflow that declares a design read before coding, then tunes variance, motion, and density dials to the brief. This Skill also bans default patterns like AI-purple gradients, centered heroes, and eyebrow labels on every section.

What stack does this frontend design skill use?

The default stack is React or Next.js with Server Components, Tailwind v4 for styling, Motion (imported from motion/react) for animation, and next/font or self-hosted fonts. Official design systems like Fluent, Carbon, or shadcn/ui are used when the brief calls for them.

When should I use a real design system instead of custom CSS?

Reach for an official package when the brief maps to one: Fluent for Microsoft-style enterprise, Material 3 for Google-flavored UI, Carbon for IBM-style B2B, govuk-frontend or USWDS for public sector. Never recreate a system's CSS by hand or mix two systems in one project.

Does this skill work for dashboards or data-heavy product UI?

No. The skill explicitly scopes itself to landing pages, portfolios, editorial sites, and redesigns. Dashboards, data tables, and multi-step product UI are out of scope and need a different approach.

What does the pre-flight check catch before shipping?

It mechanically audits eyebrow overuse (max one per three sections), CTA contrast and wrapping, duplicate CTA intent, hero overflow and padding, zigzag layout repetition, italic descender clipping, and color or shape consistency violations.

How are images and logos handled in generated pages?

Image-generation tools are used first for section-specific assets, with real photography sources as fallback. Logo walls use real SVG marks from Simple Icons or generated monograms, never plain text wordmarks.