Art & Design

Optimize for search engine visibility and ranking. Use when asked to "improve SEO", "optimize for search", "fix meta tags", "add structured data", "sitemap optimization", or "search engine optimization".

The original v1 taste-skill, preserved for projects depending on its exact behavior. The current default is `design-taste-frontend` (v2 experimental), which is a substantial rewrite. Use this v1 install name only if you need exact backward compatibility.

Build scalable design systems with Tailwind CSS, design tokens, component libraries, and responsive patterns. Use when creating component libraries, implementing design systems, or standardizing UI patterns.

Optimize Core Web Vitals (LCP, INP, CLS) for better page experience using field and lab evidence. Use when asked to "improve Core Web Vitals", "fix LCP", "reduce CLS", "optimize INP", "page experience optimization", or "fix layout shifts".

Elite frontend image-direction skill for generating premium, conversion-aware website design references. CRITICAL OUTPUT RULE — generate ONE separate horizontal image FOR EVERY section. A landing page with 8 sections produces 8 images. Never compress multiple sections into one image. Enforces composition variety (not always left-text / right-image), background-image freedom, varied CTAs, varied hero scales (giant / mid / mini minimalist), narrative concept spine, second-read moments, and a single consistent palette across all images. Optimized for landing pages, marketing sites, and product comps that developers or coding models can accurately recreate.

Optimize web performance for faster loading and better user experience. Use when asked to "speed up my site", "optimize performance", "reduce load time", "fix slow loading", "improve page speed", or "performance audit".

Build scalable design systems with Tailwind CSS v4, design tokens, component libraries, and responsive patterns. Use when creating component libraries, implementing design systems, or standardizing UI patterns.

Audit and improve web accessibility following WCAG 2.2 guidelines. Use when asked to "improve accessibility", "a11y audit", "WCAG compliance", "screen reader support", "keyboard navigation", or "make accessible".

Comprehensive skill for GSAP (GreenSock Animation Platform) and ScrollTrigger plugin. Use this skill when creating web animations, scroll-driven experiences, timelines, tweens, scroll-triggered animations, pinning, scrubbing, parallax effects, or animating DOM elements, SVG, Canvas, WebGL, or Three.js. Triggers on tasks involving GSAP, ScrollTrigger, smooth animations, scroll effects, or animation sequencing.

When the user needs to create, critique, or optimize a landing page for conversion -- including headline rewrites, CTA placement, layout restructuring, or full page copy drafts.

Minimal pre-launch landing with email capture, brand logo, and optional decorative layer. Reads DESIGN.md for colors, typography, and layout rules. Best for: product launches, beta signups, early access programs, indie projects.

When the user wants to optimize signup, registration, account creation, or trial activation flows. Also use when the user mentions \"signup conversions,\" \"registration friction,\" \"signup...

Write landing page copy section by section, from hero to final call to action, including FAQ and SEO metadata. Use when a founder needs copy for a new or existing landing page.

Plan a simple launch that creates a burst of sales for something you built, sized to the audience you actually have right now. Picks the launch type that fits your stage, sets a real date and a real number to aim at, and writes a day-by-day timeline plus a checklist of what you need to make. Use when the user says "I'm launching X", "plan my launch", "how do I launch this", "I built something and want to sell it", "waitlist strategy", "should I do a lifetime deal", "I want a burst of sales", or "/launch-plan".

>- Step-by-step guide to building GTM landing pages with v0 by Vercel — the AI generative UI platform. Covers prompt engineering for v0, iterating on generated UI, exporting to Next.js, deploying on Vercel, and connecting forms/analytics. Use when building a landing page, pricing page, waitlist page, event page, or marketing microsite with v0. Triggers on: "v0", "v0 by Vercel", "v0 landing page", "build landing page with AI", "v0 pricing page", "v0 tutorial".

When the user wants to create or update their startup context document. Also use when the user mentions "set up context", "tell you about my startup", or any other skill needs context that doesn't exist yet.

Use before starting a product, feature, MVP, agent, automation, or integration build to identify the main pre-build risk and choose the smallest validation step. Trigger when the user asks whether to build, scope, validate, prioritize, or sanity-check an idea before implementation.

>- Reverse-engineer the design taste of any website. Given a URL, captures DOM data and a screenshot via real browser, then runs a 4-step analysis to produce {domain}.md + {domain}.json with practical design tokens (colors, typography, spacing, radii, shadows, grid) AND taste DNA (Trigger → Decision → Reason → Evidence trade-offs explaining WHY the design works). Use whenever the user wants to extract a site's design system, study a competitor's visual language, port an aesthetic to a new project, or generate design guidance for an AI coding agent. Triggers on '/taste <url>', 'analyze the design of X', 'what makes X's site good', 'extract design tokens from X', 'give me X's design DNA', 'build something in the style of X', 'I want my app to feel like X'. Output rejects AI slop ('clean', 'modern', 'user-friendly') in favor of concrete px/hex values and restraint trade-offs. Do NOT use for scraping data, summarizing page content, or tasks unrelated to visual design.

Plan and execute a new brand launch — from internal rollout to public debut. Use when the user says "launch the brand", "brand launch plan", "how do we introduce the brand", "brand reveal", "brand debut", "going public with the brand", "announcing the new brand", "brand launch strategy", "pre-launch brand", "brand rollout", "introducing our brand to the market", or is ready to take a new or refreshed brand from internal to external. Also use for soft launches, hard launches, and phased rollouts.

>- Lovable (formerly GPT Engineer) is a browser-based AI app builder that turns a natural-language description into a working full-stack web app with a built-in backend, authentication, database and one-click publishing. Use when the user wants to prototype or ship a web app with Lovable, write effective Lovable prompts, connect Supabase or GitHub, review generated security rules, or move a Lovable project into their own editor.

Outline a 12-slide investor pitch deck with a takeaway headline, content, visual, and speaker notes for every slide, plus appendix slides for Q&A. Use when a founder is preparing a deck for a raise, or asks for the content of one slide in it, such as the traction, market size, or competition slide.

Build a one-page "coming soon" that collects emails before the thing exists, so you find out if anyone wants it before you spend three months building it. One promise, one field, one button, an honest date, and a real place the emails land — all free, no backend. Use when the user says "build a waitlist page", "coming soon page", "collect emails before I build", "I want to see if anyone wants this", "landing page for an idea", "pre-launch page", "validate my idea", "early access signup", "should I build this first", or types /waitlist-page.

>- Interview the user about what they want to build, design the full architecture, and emit a self-contained blueprint another Claude Code instance can build from with zero prior context. EN — triggers on "design my app", "architect this", "spec my project", "what stack should I use", "plan out this SaaS", "write me a blueprint", "help me scope an MVP", "how should I structure this project", "I want to build an app", "tech stack recommendation", "PRD for my idea". ES — se activa con "diseña mi app", "arquitectura de mi proyecto", "qué stack uso", "hazme un blueprint", "planea esta app", "cómo estructuro este proyecto", "quiero construir una app", "diseña la arquitectura", "especifica mi proyecto", "plan técnico", "MVP". Also handles brownfield: "document my existing codebase", "documenta mi repo", "add a feature to this project". Does NOT write application code — it designs systems and produces blueprints.

Turns a product or startup idea into a ranked list of riskiest assumptions, the cheapest test for each, pass/kill thresholds, and a go/pivot/kill readout, before anyone builds. Use when someone says "validate my idea", "is this worth building", "what's the riskiest assumption", "design an MVP", "fake door", "smoke test", "will people pay", "pre-sell", "customer discovery plan" or "should we build this". Draws on 82 Lenny's Podcast guests incl. Mike Maples Jr., Eric Ries and Jake Knapp.