taste-skill

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

Updated Jun 29, 2026
One-click install
npx skills add https://github.com/thorsenk/skills --skill taste-skill-thorsenk
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: taste-skill
Source: https://github.com/thorsenk/skills/tree/main/skills/taste-skill
Command: npx skills add https://github.com/thorsenk/skills --skill taste-skill-thorsenk

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? LLM-generated frontend code tends to fall back on the same templated aesthetics: AI-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 apply concrete anti-default rules so the output does 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 Configuration Dials: Tunes DESIGN_VARIANCE, MOTION_INTENSITY, and VISUAL_DENSITY with signal-based inference tables and per-use-case presets. - Design System Mapping: Routes briefs to official packages (Fluent, Material 3, Carbon, Polaris, GOV.UK, shadcn/ui, Tailwind v4) or honest native-CSS implementations for aesthetics like bento, brutalism, and glassmorphism. - Hard Layout and Pre-Flight Rules: Enforces hero viewport fit, eyebrow restraint, CTA contrast and wrap checks, palette locks, and section-layout diversity, with audit-first handling for redesigns. - Use Case: Ask for a premium consumer cookware landing page and receive a React/Tailwind build with a non-default palette, real image assets, and a passing pre-flight audit instead of the usual beige-and-brass template. ## Quick Start Use the taste-skill to design and build a landing page for my SaaS product that does not look like a generic AI template.

Frequently Asked Questions about taste-skill

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 reads page kind, vibe words, references, and audience before writing code. Then apply anti-default rules: avoid AI-purple gradients, centered heroes, and equal feature cards, and lock one accent color and one corner-radius scale per page.

What design system should I use for a React frontend project?▼

Match the brief to an official package: Fluent for Microsoft-style enterprise, Material 3 for Google-flavored UI, Carbon for IBM-style B2B, Polaris for Shopify, and shadcn/ui or Tailwind v4 for modern SaaS. Use one system per project and never recreate official CSS by hand.

Does this skill work with Next.js and Tailwind CSS?▼

Yes, the default stack is React or Next.js with Server Components, Tailwind v4 for styling, and Motion for animation. Interactive components must be isolated client leaves, and fonts load via next/font rather than Google Fonts link tags.

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 emphasis inside headlines, use italic or bold of the same font family rather than mixing in a random serif.

What are the limitations of this frontend design skill?▼

It targets landing pages, portfolios, and redesigns only, not dashboards, data tables, or multi-step product UI. All rules are contextual and fire only after the brief is read, so it does not operate as an automatic code generator without design direction.