Taste Skill · Frontend design

Taste Skill: Give Your Agent Better Taste

Read the room. Choose a direction. Build something worth looking at.

Taste Skill is Leon Lin's anti-slop frontend design Skill for landing pages, portfolios and redesigns. This focused edition keeps the source's design dials, visual guidance and preflight rules while making the path from brief to finished interface easier to follow. Independently refined by Antigravity Skills from the MIT source; not an official Leon Lin release or endorsement.

View original source

Landing pages
Portfolios
Visual redesigns

About This Skill

Taste Skill is Leon Lin's anti-slop frontend design Skill for landing pages, portfolios, and public-facing redesigns. It helps an agent read the brief, choose a visual direction, preserve required facts, and verify the finished interface. This focused edition keeps the original package intact while clarifying invocation and completion.

Built on proven foundations

Trusted Source, Professionally Refined

The original expertise stays intact. Focused refinements make it easier to start, follow the guidance, and know when the work is finished.

Original foundation

Leon Lin · commit ce26fc2

The original Skill knowledge, package structure, attribution and original license terms are preserved. Follow the source link to see where this edition began.

View the original project

Antigravity optimization

2 files, one clearer workflow

A source-faithful edition with the improvements explained below. The download includes the original attribution and everything needed to follow the Skill’s guidance.

More useful from the first prompt

What We Improved

Keep the depth you came for. Get clearer starting points, practical guidance and an explicit finish line.

Clearer invocation and scope

Taste now tells the agent when it owns a landing page, portfolio, or public-facing redesign, and when to route an out-of-scope surface elsewhere.

Visible five-phase handoffs

Read, Frame, Compose, Build, and Verify now each name the artifact or check needed before the next handoff.

A redesign branch boundary

Preserve, Overhaul, and Greenfield work now records its mode, reason, and preservation boundary before audit or visual changes.

A compact delivery handoff

The final pre-flight now asks for checked surfaces, exceptions, and missing inputs so an agent can close the loop without hiding an unchecked box.

Start with Your Brief

1Bring a landing page, portfolio, or public-facing redesign brief with assets, copy, and facts that must stay unchanged.
2State the audience, vibe, constraints, and one-line Design Read before choosing a direction.
3Choose Greenfield, Preserve, or Overhaul, then name the preservation boundary before touching code.
4Move through Read, Frame, Compose, Build, and Verify; finish with the Pre-Flight checklist and delivery handoff.

Example Command

Use Taste to redesign this landing page. Preserve the routes, content and SEO metadata; explain the design direction before building.

Core Capabilities

Brief-led frontend direction

Read the audience, vibe, references, assets, and quiet constraints before choosing an aesthetic or design system.

Visible design dials

Use design variance, motion intensity, and visual density to make the visual direction explicit before implementation.

Preservation-aware redesigns

Audit routes, copy, analytics, legal facts, accessibility, and SEO before changing an existing public-facing surface.

Pre-flight delivery

Verify responsive, accessibility, motion, content, and performance guardrails, then report exceptions and missing inputs.

Use Cases

Distinctive landing pages

Turn a fixed marketing brief into a deliberate visual direction before components and copy are assembled.

Portfolio surfaces

Choose hierarchy, type, assets, motion, and responsive behavior for a portfolio or studio surface.

Preserve-mode redesigns

Modernize the visual system while protecting routes, content, analytics, legal copy, and SEO facts.

Visual overhaul with guardrails

Start a new visual language on existing content and information architecture without silently changing protected facts.

SKILL.md

# Taste Skill

## Original package

The original distribution is Leon Lin's MIT-licensed design-taste-frontend Skill:

text:
LICENSE
skills/taste-skill/SKILL.md


The pinned SKILL.md remains the complete 1,206-line source of the design dials, contextual rules, redesign protocol, reference vocabulary, appendices, and final pre-flight matrix. The upstream tree contains no vendored blocks/ files at this revision.

## Focused edition

The optimized package keeps that one-file source and adds only four navigation contracts: scope-aware invocation, five phase handoffs, redesign branch completion, and a final delivery handoff. The source's design knowledge and out-of-scope boundaries remain the authority.

Frontend DesignA design-led frontend Skill for building interfaces from a thesis and real content.ImpeccableA UI refinement Skill for auditing and improving an existing interface.

Frequently Asked Questions

What is Taste Skill?

Taste Skill is Leon Lin's anti-slop frontend design Skill for distinctive landing pages, portfolios, and public-facing redesigns. It starts with the brief, makes design direction explicit, and ends with a source-backed pre-flight check.

Who created Taste Skill, and where is the GitHub source for design-taste-frontend?

Leon Lin is the upstream author. Taste is the page and display name, while design-taste-frontend is the upstream install identity in the MIT-licensed Leonxlnx/taste-skill repository: https://github.com/Leonxlnx/taste-skill.

How do I use Taste Skill with Claude or Antigravity?

Install the distributed design-taste-frontend Skill through the host's supported Skill mechanism, then invoke Taste for a landing page, portfolio, or public-facing redesign. Host-specific installation and invocation controls remain the authority; this page does not claim exhaustive agent compatibility.

Does Taste Skill preserve an existing site during a redesign?

Yes, when the brief selects Redesign - Preserve. The source requires an audit of routes, information architecture, copy, brand, legal facts, analytics, accessibility, and SEO before visual changes. Redesign - Overhaul preserves content and IA while changing the visual language.

How is this edition different from the original?

The edition keeps the complete original one-file knowledge body and MIT notice. It adds source-backed invocation and scope routing, five phase handoffs, a redesign branch boundary, and a delivery handoff. It is not the older shortened rewrite and does not add a blocks directory absent from the pinned source.

Discussion

0 comments

Trigger Phrases

Use these phrases to activate this skill in your AI coding assistant:

Use Taste for this landing page brief.Use Taste to redesign this public-facing page without changing its routes or metadata.Apply Taste to this portfolio direction.