菜单
Anti-slop frontend skill for landing pages, portfolios, and redesigns. The agent reads the brief, infers the right design direction, and ships interfaces that do not look templated. Real design systems when applicable, audit-first on redesigns, strict pre-flight check.
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/simstudioai/sim --skill design-taste-frontend命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
基于 SOC 职业分类
正在显示 SKILL.md
| name | design-taste-frontend |
| source | https://github.com/leonxlnx/taste-skill — skills/taste-skill/SKILL.md |
| description | Anti-slop frontend skill for landing pages, portfolios, and redesigns. The agent reads the brief, infers the right design direction, and ships interfaces that do not look templated. Real design systems when applicable, audit-first on redesigns, strict pre-flight check. |
Landing pages, portfolios, and redesigns. Not dashboards, not data tables, not multi-step product UI. Every rule below is contextual. None of it fires automatically. First read the brief, then pull only what fits.
Before touching code or tweaking dials, infer what the user actually wants. Most LLM design output is bad because the model jumps to a default aesthetic instead of reading the room.
Before any code, state in one line: "Reading this as: <page kind> for <audience>, with a <vibe> language, leaning toward <design system or aesthetic family>."
Example reads:
Ask exactly one clarifying question - never a multi-question dump - and only when the design read genuinely diverges. Example: "Should this feel closer to Linear-clean or Awwwards-experimental?"
If you can confidently infer from context, do not ask. Just declare the design read and proceed.
Do not default to: AI-purple gradients, centered hero over dark mesh, three equal feature cards, generic glassmorphism on everything, infinite-loop micro-animations everywhere, Inter + slate-900. These are the LLM defaults. Reach past them deliberately based on the design read.
After the design read, set three dials. Every layout, motion, and density decision below is gated by these.
DESIGN_VARIANCE: 8 - 1 = Perfect Symmetry, 10 = Artsy ChaosMOTION_INTENSITY: 6 - 1 = Static, 10 = Cinematic / PhysicsVISUAL_DENSITY: 4 - 1 = Art Gallery / Airy, 10 = Cockpit / Packed DataBaseline: 8 / 6 / 4. Use these unless the design read overrides them. Do not ask the user to edit this file - overrides happen conversationally.
| Signal | VARIANCE | MOTION | DENSITY |
|---|---|---|---|
| "minimalist / clean / calm / editorial / Linear-style" | 5-6 | 3-4 | 2-3 |
| "premium consumer / Apple-y / luxury / brand" | 7-8 | 5-7 | 3-4 |
| "playful / wild / Dribbble / Awwwards / experimental / agency" | 9-10 | 8-10 | 3-4 |
| "landing page / portfolio / marketing site (default)" | 7-9 | 6-8 | 3-5 |
| "trust-first / public-sector / regulated / accessibility-critical" | 3-4 | 2-3 | 4-5 |
| "redesign - preserve" | match existing | +1 | match existing |
| "redesign - overhaul" | +2 | +2 | match existing |
| Use case | VARIANCE | MOTION | DENSITY |
|---|---|---|---|
| Landing (SaaS, mainstream) | 7 | 6 | 4 |
| Landing (Agency / creative) | 9 | 8 | 3 |
| Landing (Premium consumer) | 7 | 6 | 3 |
| Portfolio (Designer / studio) | 8 | 7 | 3 |
| Portfolio (Developer) | 6 | 5 | 4 |
| Editorial / Blog | 6 | 4 | 3 |
| Public-sector service | 3 | 2 | 5 |
| Redesign - preserve | match | match+1 | match |
| Redesign - overhaul | +2 | +2 | match |
Use these (or user-overridden values) as global variables. Cross-references throughout this document refer to these exact variable names - never invent aliases like LAYOUT_VARIANCE or ANIM_LEVEL.
Once you have the design read (Section 0) and dials (Section 1), pick the right foundation. Do not invent CSS for things that have an official package. Do not pretend an aesthetic trend is an official system.
| Brief reads as… | Reach for | Why |
|---|---|---|
| Microsoft / enterprise SaaS / dashboards | @fluentui/react-components or @fluentui/web-components | Official Fluent UI, Microsoft tokens, accessibility done |
| Google-ish UI, Material-flavored product | @material/web + Material 3 tokens | Official, theme-able via Material Theming |
| IBM-style B2B / enterprise analytics | @carbon/react + @carbon/styles | Official Carbon, mature data-density patterns |
| Shopify app surfaces | polaris.js web components / Polaris React | Required for Shopify admin UI |
| Atlassian / Jira-style product | @atlaskit/* + @atlaskit/tokens | Official Atlassian DS |
| GitHub-style devtool / community page | @primer/css or @primer/react-brand | Official Primer; Brand variant for marketing |
| Public-sector UK service | govuk-frontend | Legally / regulatorily expected |
| US public-sector / trust-first | uswds | Same |
| Fast local-business / agency MVP | Bootstrap 5.3 | Boring, fast, works |
| Modern accessible React foundation | @radix-ui/themes | Primitives + polished theme |
| Modern SaaS where you own the components | shadcn/ui (npx shadcn@latest add ...) | You own the code, easy to customise; never ship default state |
| Tailwind-based modern SaaS / AI marketing | Tailwind v4 utilities + dark: variant | Default for indie + small team builds |
Honesty rule: if the brief reads as one of the systems above, install and use the official package. Do not recreate its CSS by hand. Do not import a system's tokens but then override 90% of them.
One system per project. Do not mix Fluent React with Carbon in the same tree. Do not import shadcn/ui components into a Material 3 app.
For these directions, there is no single official package. Build with native CSS + Tailwind + a maintained component library. Be honest in code comments about what is borrowed inspiration vs. official material.
| Aesthetic | Honest implementation |
|---|---|
| Glassmorphism / "frosted glass" | backdrop-filter, layered borders, highlight overlays. Provide solid-fill fallback for prefers-reduced-transparency. |
| Bento (Apple-style tile grids) | CSS Grid with mixed cell sizes. No single library owns this. |
| Brutalism | Native CSS, monospace, raw borders. No library. |
| Editorial / magazine | Serif type, asymmetric grid, generous whitespace. No library. |
| Dark tech / hacker | Mono + accent neon, terminal motifs. No library. |
| Aurora / mesh gradients | SVG or layered radial gradients. No library. |
| Kinetic typography | Native CSS animations, scroll-driven animations, GSAP for hijacks. No library. |
| Apple Liquid Glass | Apple documents this for Apple platforms only. There is no official liquid-glass.css. Web implementations are approximations using backdrop-filter + layered borders + highlights. Label clearly as approximation. |
Unless the design read picks a real design system (Section 2.A), these are the defaults:
"use client" component.'use client' at the top. Server Components render static layouts only.tailwindcss plugin in postcss.config.js. Use @tailwindcss/postcss or the Vite plugin.motion/react (import { motion } from "motion/react"). The framer-motion package still works as a legacy alias - prefer motion/react in new code.next/font (Next.js) or self-host with @font-face + font-display: swap. Never link Google Fonts via <link> in production.useState / useReducer for isolated UI.useState to track continuous values driven by user input (mouse position, scroll progress, pointer physics, magnetic hover). Use Motion's useMotionValue / useTransform / useScroll. useState re-renders the React tree on every change and collapses on mobile.@phosphor-icons/react, hugeicons-react, @radix-ui/react-icons, @tabler/icons-react.lucide-react. Acceptable only when the user explicitly asks for it or the project already depends on it.strokeWidth globally (e.g. 1.5 or 2.0).Discouraged by default in code, markup, and visible text. Replace symbols with icon-library glyphs. Override: allow emojis only when the user explicitly asks for a playful / chat-style / social-native vibe - and even then use them sparingly with intent.
sm 640, md 768, lg 1024, xl 1280, 2xl 1536).max-w-[1400px] mx-auto or max-w-7xl.h-screen for full-height Hero sections. ALWAYS use min-h-[100dvh] to prevent layout jumping on mobile (iOS Safari address bar).w-[calc(33%-1rem)]). ALWAYS use CSS Grid (grid grid-cols-1 md:grid-cols-3 gap-6).Before importing ANY 3rd-party library, check package.json. If the package is missing, output the install command first. Never assume a library exists.
LLMs default to clichés. Override these defaults proactively. Each rule has a context-aware override path.
Display / Headlines: Default text-4xl md:text-6xl tracking-tighter leading-none.
Body / Paragraphs: Default text-base text-gray-600 leading-relaxed max-w-[65ch].
Sans font choice:
Inter. Pick Geist, Outfit, Cabinet Grotesk, Satoshi, or a brand-appropriate serif first.Pairings to know: Geist + Geist Mono, Satoshi + JetBrains Mono, Cabinet Grotesk + Inter Tight, GT America + IBM Plex Mono.
SERIF DISCIPLINE (VERY DISCOURAGED AS DEFAULT):
spatial design" type move), use italic or bold of the SAME font. Do NOT inject a random serif word into a sans headline (or vice versa) just to add visual interest. Mixed-family emphasis is amateur. Italic/bold emphasis in the same family is the right move.Max 1 accent color. Saturation < 80% by default.
THE LILA RULE: The "AI Purple / Blue glow" aesthetic is discouraged as a default. No automatic purple button glows, no random neon gradients. Use neutral bases (Zinc / Slate / Stone) with high-contrast singular accents (Emerald, Electric Blue, Deep Rose, Burnt Orange, etc.).
Override: if the brand or brief explicitly asks for purple / violet / lila, embrace it. But execute with intent: consistent palette, harmonised neutrals, restrained gradients. Not generic AI gradient slop.
One palette per project. Do not fluctuate between warm and cool grays within the same project.
COLOR CONSISTENCY LOCK (mandatory): Once an accent color is chosen for a page, it is used on the WHOLE page. A warm-grey site does not suddenly get a blue CTA in section 7. A rose-accented site does not get a teal status badge in the footer. Pick one accent, lock it, audit every component before shipping.
PREMIUM-CONSUMER PALETTE BAN (mandatory, second-most-recurring AI-tell):
#f5f1ea, #f7f5f1, #fbf8f1, #efeae0, #ece6db, #faf7f1, #e8dfcb (all "warm paper / cream / chalk / bone")#b08947, #b6553a, #9a2436, #9c6e2a, #bc7c3a, #7d5621 (all "brass / clay / oxblood / ochre")#1a1714, #1a1814, #1b1814 (all "espresso / warm near-black")DESIGN_VARIANCE > 4. Force "Split Screen" (50/50), "Left-aligned content / right-aligned asset", "Asymmetric white-space", or scroll-pinned structures.border-t, divide-y, or negative space.VISUAL_DENSITY > 7: generic card containers are banned. Data metrics breathe in plain layout.LLMs default to "static successful state only." Always implement full cycles:
:active, use -translate-y-[1px] or scale-[0.98] to simulate a physical push.bg-white CTA with text-white label, transparent button against the page background with no border → all banned. Audit every CTA: contrast ratio WCAG AA min (4.5:1 for body, 3:1 for large text 18px+). Same rule applies to ghost buttons over photographic backgrounds (use a backdrop, scrim, or stroke).max-width on CTAs). Wrapped CTAs at desktop are a Pre-Flight Fail.gap-2 for input blocks.text-7xl/text-8xl. Default sensible range: text-4xl md:text-5xl lg:text-6xl for most heroes; text-6xl md:text-7xl only when the headline is 3-5 words. A 4-line hero headline is always a font-size error, never a copy-length error.pt-24 (≈6rem) at desktop. More than that means the hero content floats halfway down the viewport and reads as a layout bug, not as intentional space. If your hero needs more breathing room, increase font scale or asset size, not top padding.lg (1024px), condense labels, drop secondary items, or move to a hamburger. A two-line nav at desktop is broken design.Landing pages and portfolios are visual products. Text-only pages with fake-screenshot divs are slop.
Priority order for visual assets:
generate_image, MCP image tool, IDE-integrated gen, OpenAI image tools, etc.) you MUST use it to create section-specific assets: hero photography, product shots, texture backgrounds, mood images. Generate at the right aspect ratio for the section. Do not skip this step because hand-rolled CSS feels faster.https://picsum.photos/seed/{descriptive-seed}/{w}/{h} for placeholder photography (seed should describe the section, e.g. marrow-cookware-kitchen)<!-- TODO: hero product photo, 1600x1200 -->) and at the end of the response say: "This page needs real images at: [list of placements]. Please generate or provide them."Even minimalist sites need real images. A pure-text page is not minimalism. It is incomplete work. Even an editorial Linear-style site needs at least 2-3 real images (hero, one product/lifestyle shot, one supporting image). Generate B&W minimalist photography if the brief is restrained; do not skip images entirely because the dial is low.
Real company logos for social proof. When the brief calls for a "Trusted by / Used by / Customers" logo wall, do NOT default to plain text wordmarks (<span>Acme Co</span> styled in a row). Use real SVG logos:
https://cdn.simpleicons.org/{slug}/ffffff for any color, or simple-icons npm package). Covers most known brands.@svgr/cli or CDN).<svg> matching the page style. Plain text wordmarks for invented brand names look generic.Vercel + hosting underneath, no Stripe + payments, no Cloudflare + infra). The logo is the credibility, the label adds nothing the user does not already know. Optional: brand name as alt-text for screen readers, optional link to the brand's site. That is it.Hand-rolled illustrations:
Div-based fake screenshots are banned. A "hand-built product preview" rendered with <div> rectangles, fake task lists, fake dashboards, fake terminal windows is a Tell. If you need to show a product:
Hero needs a real visual. Text + gradient blob is not a hero - it's a placeholder.
Landing pages live on the first impression, not the full read. Cut ruthlessly.
Default content shape per section: short headline (≤ 8 words) + short sub-paragraph (≤ 25 words) + one visual asset OR one CTA. Anything more must be justified by the section's job.
No data-dump sections. A 20-row publication table, a 30-row award list, a giant pricing matrix on a marketing page = wrong layout. Use:
Long lists need a different UI component, not a longer list. Default <ul> with bullets / divide-y rows is the lazy choice. If you have > 5 items, reach for one of these instead:
Spec sheets specifically (the Marrow-cookware pattern). A long product specification table with border-b on every row is the AI default for cookware / hardware / apparel / artisan-goods briefs. Banned. Concrete alternatives:
COPY SELF-AUDIT (mandatory before ship): Before declaring any task done, re-read every visible string on the page (headlines, subheads, eyebrows, button labels, body copy, captions, alt text, footer text, error messages). Flag any string that is:
The page has ONE theme. Sections do not invert.
prefers-color-scheme) at the page level and lock it. Section-level background tints within the same theme family are fine (bg-zinc-950 next to bg-zinc-900); flipping to bg-amber-50 in the middle of a bg-zinc-950 page is broken.<Theme>), set the theme ONCE in layout.tsx or the page root. Do not let individual sections override.These are tools, not defaults. Use them when the design read calls for them. None of these fire automatically.
backdrop-blur: add a 1px inner border (border-white/10) and a subtle inner shadow (shadow-[inset_0_1px_0_rgba(255,255,255,0.1)]) for physical edge refraction. Provide a solid-fill fallback under prefers-reduced-transparency.MOTION_INTENSITY > 5 AND the brief reads premium / playful / agency. Implement EXCLUSIVELY with Motion's useMotionValue / useTransform outside the React render cycle. Never useState. See Section 3.B.MOTION_INTENSITY > 5 AND the section actively benefits from motion (status indicators, live feeds, AI-feel). Not every card needs an infinite loop. If a section is informational, leave it still. Apply Spring Physics (type: "spring", stiffness: 100, damping: 20) - no linear easing.MOTION_INTENSITY > 4, the page must actually move: entry transitions on hero, scroll-reveal on key sections, hover physics on CTAs, at minimum. A static page that claims MOTION_INTENSITY: 7 is broken. Conversely, if you cannot ship working motion in the available scope, drop the dial to 3 and ship a clean static page. Never half-build motion that breaks (cut-off ScrollTriggers, jumpy enters, missing cleanups)."use client";
import { useRef, useEffect } from "react";
import { gsap } from "gsap";
import { ScrollTrigger } from "gsap/ScrollTrigger";
import { useReducedMotion } from "motion/react";
gsap.registerPlugin(ScrollTrigger);
export function StickyStack({ cards }: { cards: React.ReactNode[] }) {
const ref = useRef<HTMLDivElement>(null);
const reduce = useReducedMotion();
useEffect(() => {
if (reduce || !ref.current) return;
const ctx = gsap.context(() => {
const cardEls = gsap.utils.toArray<HTMLElement>(".stack-card");
cardEls.forEach((card, i) => {
if (i === cardEls.length - 1) return;
ScrollTrigger.create({
trigger: card,
start: "top top",
: cardEls[cardEls. - ],
: ,
: ,
: ,
});
gsap.(card, {
: ,
: ,
: ,
: {
: cardEls[i + ],
: ,
: ,
: ,
},
});
});
}, ref);
ctx.();
}, [reduce]);
(
);
}
Critical points: start: "top top", pin: true, every card except the last is pinned, the scale/opacity transform is driven by the NEXT card's scroll trigger (so previous card shrinks as next one arrives).
"use client";
import { useRef, useEffect } from "react";
import { gsap } from "gsap";
import { ScrollTrigger } from "gsap/ScrollTrigger";
import { useReducedMotion } from "motion/react";
gsap.registerPlugin(ScrollTrigger);
export function HorizontalPan({ children }: { children: React.ReactNode }) {
const wrap = useRef<HTMLDivElement>(null);
const track = useRef<HTMLDivElement>(null);
const reduce = useReducedMotion();
useEffect(() => {
if (reduce || !wrap.current || !track.current) return;
const ctx = gsap.context(() => {
const distance = track.current!.scrollWidth - window.innerWidth;
gsap.to(track.current, {
x: -distance,
ease: "none",
scrollTrigger: {
trigger: wrap.,
: ,
: ,
: ,
: ,
: ,
},
});
}, wrap);
ctx.();
}, [reduce]);
(
);
}
Critical points: start: "top top", pin: true, end: "+=${distance}" (scroll length = horizontal travel needed), scrub: 1. The wrapper is pinned, the inner track slides horizontally as the user scrolls vertically.
For simple "items appear as they enter viewport" (no pinning), prefer Motion's whileInView over GSAP - lighter, no ScrollTrigger needed:
"use client";
import { motion, useReducedMotion } from "motion/react";
export function RevealStagger({ items }: { items: string[] }) {
const reduce = useReducedMotion();
return (
<ul className="grid gap-6">
{items.map((item, i) => (
<motion.li
key={item}
initial={reduce ? false : { opacity: 0, y: 24 }}
whileInView={{ opacity: 1, y: 0 }}
viewport={{ once: true, amount: 0.3 }}
transition={{
duration: 0.6,
delay: i * 0.06,
ease: [0.16, 1, 0.3, 1],
}}
>
{item}
</motion.li>
))}
</>
);
}
Use this for: feature lists, testimonial grids, logo walls, anything that just needs "enter on scroll." Save GSAP for actual pin/scrub work.
window.addEventListener("scroll", ...) is banned. It runs on every scroll frame, jank-prone, no batching. Use Motion's useScroll(), GSAP's ScrollTrigger, IntersectionObserver, or CSS scroll-driven animations (animation-timeline: view()).window.scrollY in React state. Same reason. Re-renders on every frame.requestAnimationFrame loops that touch React state. Use motion values (useMotionValue + useTransform) instead.layout and layoutId props for visible state changes (re-ordering lists, expanding modals, shared elements between routes). Do not wrap static content in layout props "for safety" - it costs measurement work.staggerChildren (Motion) or CSS cascade (animation-delay: calc(var(--index) * 100ms)) for reveal moments where sequence matters. For staggerChildren, parent (variants) and children MUST share the same Client Component tree.transform and opacity. Never animate top, left, width, height.will-change: transform sparingly - only on elements that will actually animate.MOTION_INTENSITY > 3 MUST honor prefers-reduced-motion. This is non-negotiable.useReducedMotion() and degrade to static.@media (prefers-reduced-motion: no-preference) or provide an override block under @media (prefers-reduced-motion: reduce) that disables.dark: variant OR CSS variables for tokens. Pick one strategy per project.prefers-color-scheme: dark. Default to system preference unless the brand insists on one mode.next/image priority or preloaded.pointer-events-none pseudo-elements (e.g., fixed inset-0 z-[60] pointer-events-none). NEVER on scrolling containers - continuous GPU repaints destroy mobile FPS.NEVER spam arbitrary z-50 or z-10. Use z-index strictly for systemic layer contexts (sticky navbars, modals, overlays, grain). Document the z-index scale in a project constants file.
margin-top: -2rem overlaps, varied image aspect ratios (4:3 next to 16:9), left-aligned headers over center-aligned data.grid-template-columns: 2fr 1fr 1fr), massive empty zones (padding-left: 20vw).md: MUST collapse to strict single-column (w-full, px-4, py-8) on viewports < 768px.:hover and :active states only. prefers-reduced-motion is the default mode anyway.transition: all 0.3s cubic-bezier(0.16, 1, 0.3, 1). animation-delay cascades for load-ins. Focus on transform and opacity.animation-timeline or GSAP ScrollTrigger). Use Motion hooks. NEVER use window.addEventListener('scroll') - it is a hard ban, not a "prefer-not." See Section 5.D for the allowed alternatives.py-32 to py-48). Expensive, clean.py-16 to py-24).font-mono for all numbers.Dual-mode by default. Never assume light-only unless the brief is print-emulating editorial.
dark: variant (default for utility-first projects): every color utility paired with its dark variant (bg-white dark:bg-zinc-950, text-gray-900 dark:text-gray-100).--surface, --surface-elevated, --text-primary, --accent) and swap values under [data-theme="dark"] or @media (prefers-color-scheme: dark).The brief and brand decide. This skill enforces only:
#000000 and no pure #ffffff - use off-black (zinc-950, near-black warm gray) and off-white. Pure values kill depth.Respect prefers-color-scheme unless the brand insists. Add a manual toggle if either mode would lose key brand expression.
Open the page in both modes during development. Do not ship a page you've only seen in one mode.
Avoid these signatures unless the brief explicitly asks for them.
#000000). Off-black, zinc-950, or charcoal.99.99%, 50%, 1234567. Use organic, messy data (47.2%, +1 (312) 847-1928).<div> rectangles to simulate a screenshot. Use real images, generated images, or skip the preview.https://picsum.photos/seed/{descriptive-string}/{w}/{h}, or generated photo placeholders, or actual assets.These patterns came out of real LLM-generated landing-page tests. They are the signatures the model defaults to when it tries to "look designed." Treat them as hard bans unless the brief explicitly calls for one.
Hero & top-of-page
V0.6, v2.0, BETA, INVITE-ONLY PREVIEW, EARLY ACCESS, ALPHA - banned as default eyebrows. Only acceptable when the brief is explicitly about a product launch / preview status.Section numbering & micro-labels
00 / INDEX, 001 · Capabilities, 002 · Featured commission, 06 · how it works, 05 · The honest table - banned. Eyebrows should name the topic in plain language, not enumerate.01 / 4-style pagination on images or bento tiles. If the user can count, they don't need the label.Scroll · 001 Capabilities-style scroll cues. A simple arrow or "Scroll" is enough; no section-number prefix.Separators & dots
·) is rationed. Maximum 1 per line in metadata strips. Do NOT use it as the default separator for everything ("foo · bar · baz · qux · quux"). If you need a separator family, prefer line breaks, hairlines, or columns.Em-dashes & typography flourishes
—) as a design element OR anywhere else. See Section 9.G below for the complete, non-negotiable ban. The em-dash character is forbidden in headlines, eyebrows, pills, body copy, quotes, attribution, captions, button text, and alt text. Use the regular hyphen (-).<br>-broken-and-italicized headlines as a default "design move." "for thirty<br>years." type splits. Headlines should read naturally first, get clever only when the brief demands it.Fake product previews
Marketing-copy Tells
Pills, labels and version stamps
<span> overlays on photos with tags like Brand · 02, PLATE · BRAND, Field notes - journal. Either let the image speak alone, or add a caption directly below (outside the image).Field study no. 12 · Ines Caetano, Plate 03 · House archive, Frame XII · 35mm under stock/picsum images are pretentious. Photo credit is allowed ONLY when there is a real photographer being credited for a real photo (with permission). Otherwise: skip the caption or use a one-line functional caption ("The 6-quart, in Sage.").v1.4.2, Build 0048, last sync 4s ago · main are CLI / devtool fixtures, not landing-page content. Banned on marketing/landing/portfolio pages.Decoration text strips
BRAND. MOTION. SPATIAL., TYPE / FORM / MOTION, DESIGN · BUILD · SHIP, ESTD. 2018 · LISBON · BRAND. MOTION. SPATIAL. as a small mono-caps strip across the bottom of the hero are an agency-portfolio cliché. Banned by default. Only acceptable when the strip carries real, navigable links (sticky bottom nav) or real status info (cookie banner, build info on a docs site).Lists, dividers and scoring
border-t + border-b on every row of a long list / spec table. Pick one (bottom-border between rows OR top-border above the group) and use it sparsely. A 10-row spec table with hairlines under each row is the laziest layout - see Section 4.9 for alternative UI components.bg-zinc-200 tracks with a partial fill on top are dashboard-UI clutter on a landing page.Locale, time, scroll cues
Scroll, ↓ scroll, Scroll to explore, Scroll to walk through it, animated mouse-wheel icons. If the user has not scrolled yet, they are looking at the hero. They know what scroll is. The bottom of the viewport does not need a label.Em-dash (—) is COMPLETELY banned. It is the LLM's signature stylistic crutch and it is the #1 visual Tell in production tests. There is no "limited use" allowance, no "natural language frequency" allowance, no "in body copy is fine" allowance. None.
-) or a line break + smaller-weight name.–) when used as a separator. Date ranges (2018-2026) use a hyphen. Number ranges (€40-80k) use a hyphen.The ONLY permitted dash characters on the page are:
- (for compound words, ranges, line dividers in markup)-5°C)If your output contains a single — or – anywhere visible to the user, the output fails the Pre-Flight Check and must be rewritten.
This rule is non-negotiable. The agent has historically ignored em-dash limits when phrased as "use sparingly." The phrasing here is binary: zero em-dashes.
This is a vocabulary, not a library. The agent should KNOW these pattern names to communicate about them, design with them in mind, and reach for them when the design read calls for them. Implementations and code sketches live in the Block Library (Section 12), which is populated iteratively.
motion/react) - default for UI / Bento / state-change motion.useEffect cleanup.This skill handles greenfield builds AND redesigns. Misclassifying the mode is the single biggest source of bad redesign output.
If ambiguous, ask once: "Should this redesign preserve the existing brand, or are we starting visually from scratch?"
Document the current state before proposing changes:
DESIGN_VARIANCE / MOTION_INTENSITY / VISUAL_DENSITY. That's your starting point, not the baseline.Apply in order - stop when the brief is satisfied:
MOTION_INTENSITY-appropriate micro-interactions to existing components.Never modify without explicit user approval:
The Reference Vocabulary (Section 10) names patterns. The Block Library implements them with real props, real motion specs, and real code sketches.
Status: schema defined here. Blocks will be added iteratively. Do not freelance new blocks without following this schema.
skills/taste-skill/blocks/
hero/
asymmetric-split.md
editorial-manifesto.md
kinetic-type.md
...
feature/
bento-grid.md
sticky-scroll-stack.md
zig-zag.md
...
social-proof/
pricing/
cta/
footer/
navigation/
portfolio/
transition/
---
name: asymmetric-split-hero
category: hero
dial_compatibility:
variance: [6, 10]
motion: [3, 10]
density: [2, 5]
when_to_use: "Landing pages with one strong asset and one strong message. Default hero for SaaS, agency, premium consumer."
not_for: "Editorial / manifesto launches where the message IS the design."
stack: ["react", "next", "tailwind", "motion"]
---
< 768px.MOTION_INTENSITY band (1-3, 4-7, 8-10). Reduced-motion fallback explicit.blocks/<category>/<name>--<system>.md (e.g. feature/bento-grid--material.md).This skill is NOT for:
If the brief is one of the above, say so explicitly, point to the right tool, and only apply this skill's marketing-page / about-page / landing-page parts to the surfaces where they apply.
Run this matrix before outputting code. This is the last filter.
THIS IS NOT OPTIONAL. Run every box. If any box fails, the output is not done.
—) anywhere on the page. Headlines, eyebrows, pills, body, quotes, attribution, captions, buttons, alt text. Zero. (Section 9.G - non-negotiable.)y g j p q has leading-[1.1] min + reserve?If a single checkbox cannot be honestly ticked, the page is not done. Fix it before delivering.
The sections below are vendored reference content. They give the agent real install commands, real canonical doc links, and real working starter snippets for each design system named in Section 2. Use them to ground decisions in production reality, not training-data fiction.
# Material Web (Material 3)
npm install @material/web
# Fluent UI React (v9)
npm install @fluentui/react-components
# Fluent UI Web Components (framework-free)
npm install @fluentui/web-components @fluentui/tokens
# IBM Carbon
npm install @carbon/react @carbon/styles
# Radix Themes
npm install @radix-ui/themes
Fraunces and Instrument_Serif (the two LLM-favorite display serifs).ITALIC DESCENDER CLEARANCE (mandatory): When italic is used in display type and the word contains a descender letter (y g j p q), leading-[1] or leading-none will clip the descender. Use leading-[1.1] minimum and add pb-1 or mb-1 reserve on the wrapping element. Audit every italic word in display headlines before shipping.
FOUR COLORWAYS, SELECTED WORK, THE HARDWARE, Git-native task management). Typical CSS signature: text-[11px] uppercase tracking-[0.18em], font-mono text-[10.5px] uppercase tracking-[0.22em]. Every AI-built site puts an eyebrow above EVERY section header, producing the same templated rhythm. Hard rule:
uppercase tracking (or similar small-caps mono labels above headlines) across all section components. If count > ceil(sectionCount / 3), the output fails.< 768px fallback in the same component. No "it'll work, Tailwind handles it" assumptions.Fake-precise numbers are flagged. Numbers like 92%, 4.1×, 48k, 5.8 mm, 13.4 lb either:
<!-- mock -->, "example", "sample data") - fineOne copy register per page. Don't mix technical mono ("47 tasks · 0.6 ctx-switches/day"), editorial prose, and marketing punch in the same composition unless the brand voice explicitly calls for it.
start: "top top"start: "top center""top 80%"start: "top top", pin the wrapper, scrub the inner track.pb-1pt-24 at desktop, hero content does not float halfway down the viewport?uppercase tracking micro-labels above section headlines across all components. Count ≤ ceil(sectionCount / 3)? Hero counts as 1.<ul> with divide-y for > 5 items - see Section 4.9 alternatives)?Plate · Brand, no Field notes - journal)?Field study no. 12 · Ines Caetano)?v1.4.2, Build 0048) on marketing pages?BRAND. MOTION. SPATIAL.)?Scroll, ↓ scroll, Scroll to explore)?00 / INDEX, 001 · Capabilities, 06 · how it works)?border-t + border-b on every row of long lists / spec tables?MOTION_INTENSITY > 4, page actually animates, not just claimed?start: "top top", pin: true, correct scrub)?window.addEventListener('scroll') - using Motion useScroll() / ScrollTrigger / IntersectionObserver / CSS scroll-driven animations only?MOTION_INTENSITY > 3?w-full, px-4, max-w-7xl mx-auto) for high-variance layouts?min-h-[100dvh], never h-screen?useEffect animations have strict cleanup functions?'use client' at the top, memoized?