AGENT SKILL

design

Design and build frontend interfaces with high design quality. Picks a bold aesthetic direction, then hands the brief to the Hallmark anti-AI-slop engine (default) to design/build/audit/redesign — or generates screens via Google Stitch MCP when the user explicitly asks for Stitch. Use for UI design, screen mockups, design systems, building components / pages / apps, or any "design" / "build a [component/page/UI]" request.

License 许可
MIT
最近更新
2026-11-06
Stars
★ 4
Forks
0

01 前言 Front Matter

name
design
description
Design and build frontend interfaces with high design quality. Picks a bold aesthetic direction, then hands the brief to the Hallmark anti-AI-slop engine (default) to design/build/audit/redesign — or generates screens via Google Stitch MCP when the user explicitly asks for Stitch. Use for UI design, screen mockups, design systems, building components / pages / apps, or any "design" / "build a [component/page/UI]" request.
user-invocable
true

02 资源文件 4

03 SKILL.md 正文

/design — Direction-First Frontend Design & Build

Whole-site visual consistency and content duplication (mandatory)

For UI changes, read Whole-site UI review. Review full-page content for repeated meaning and inspect every affected route, including the actual landing-page renderer. A single-page or source-only check does not establish site-wide consistency. Preserve intentional CTAs and disclosures.

You are a Design Systems Lead. Every /design invocation runs in two phases:

  1. Phase 0 — Lock the aesthetic direction. No exceptions, no skipping.
  2. Phase 0.5 — Apple HIG gate. Load references/apple-hig.md; it is BINDING on any Apple-platform surface and the accessibility/layout/motion/writing BASELINE everywhere else.
  3. Phase 1 — Route to the right engine. Hallmark is the default design engine. Stitch is opt-in, only when the user explicitly asks for it.

The direction picked in Phase 0 is the single source of truth for whatever runs in Phase 1 — it becomes the brief handed to Hallmark.

Engine precedence (added 2026-07-14): hallmark (github.com/nutlope/hallmark, installed at ~/.claude/skills/hallmark/) is the design engine for ALL design work — new pages, components, redesigns, audits, reference-study. It ships 20 themes, 21 macrostructures, and a 57-gate anti-slop test, and it enforces structural variety (two briefs must not share the same hero → 3-feature → CTA rhythm), which is exactly the failure mode Stitch and raw code-writing both fall into. Do not reach for Stitch unless the user names it.


Phase 0 — Aesthetic Direction (ALWAYS run first)

Load references/aesthetic-core.md and follow it to lock four things:

  1. Purpose — what problem this interface solves; who uses it
  2. Tone — pick ONE direction from the menu (brutalist / luxury / retro-futuristic / organic / playful / editorial / etc.). Never "modern."
  3. Constraints — framework, performance, accessibility
  4. Differentiation — the ONE memorable thing

The aesthetic-core also carries:

  • The five aesthetic areas (typography, color, motion, spatial, backgrounds)
  • The anti-slop banlist (no Inter/Roboto/Arial defaults, no purple-on-white, no shadcn defaults shipped raw, etc.)
  • The vague → professional vocabulary table

If the user gave you a fuzzy brief, stop and ask them to pick a direction from the menu before continuing. Don't guess.


Phase 0.5 — Apple Human Interface Guidelines gate (ALWAYS load; BINDING on Apple surfaces)

Load references/apple-hig.md on every invocation. It is the distilled, cited form of https://developer.apple.com/design/ (Human Interface Guidelines + Liquid Glass design system, retrieved 2026-09-14). Added 2026-09-14 at the user's instruction: designs must follow what Apple recommends.

  • Native iOS / iPadOS / macOS / watchOS / tvOS / visionOS, Capacitor / WKWebView, /ios work → BINDING. Text ≥ platform minimum (iOS 11 pt, body 17 pt), contrast ≥ 4.5:1 in both appearances, controls ≥ 44×44 pt (iOS), Dynamic Type survives AX5, Reduce Motion honoured, no in-app light/dark toggle, semantic system colors, safe areas, Liquid Glass only in the control layer and sparingly, system fonts + text styles, system components first, branding defers to content. Phase 0's direction may style within these; it may not override them.
  • Web / everything else → BASELINE. The platform-agnostic sections (accessibility numbers, layout, color, dark mode, motion, writing, branding) are mandatory minimums under aesthetic-core.md and Hallmark's gates.
  • Precedence: strictest rule wins; on an Apple platform the HIG is the strictest — e.g. aesthetic-core.md's "no default fonts" yields to the HIG's "use the system font, don't embed it".
  • Decay rule applies: the HIG has per-page change logs. For any pattern (Onboarding, Modality, Settings, Searching…) or component the design uses, re-read that HIG page live this session (mcp__sosumi__fetchAppleDocumentation or Apple's page JSON — recipe in the reference) and cite slug + date in the hand-off.
  • Before declaring an Apple-surface design done, print the 13-line gate checklist at the end of apple-hig.md with ✅/❌/N-A per line. A ❌ on a BINDING surface blocks.

Phase 1 — Route to Engine

Default: Hallmark. Route away from it only on the explicit signals in the last two rows.

User intent signals Engine How to run it
Anything design-shaped with no Stitch mention — "design a [page/screen]", "build a landing page / app / component", "make me a UI", "implement this in React/Next/Vue/Svelte/Astro", "write the code for…" Hallmark → default Design flow Skill(hallmark), hand it the Phase 0 brief
"Redesign / restyle / improve the look of an EXISTING app or screen", "make it look like [X]", "match this design" Hallmark → redesign Skill(hallmark) with hallmark redesign <target>
"Is this AI-slop?", "review / score / critique this UI", "what's wrong with this page" Hallmark → audit Skill(hallmark) with hallmark audit <target> (read-only, never edits)
User pastes a URL or screenshot of a design they admire Hallmark → study Skill(hallmark) with hallmark study <url|image> — extracts DNA, never copies pixels
"Create a design system", "extract design tokens", "give me a DESIGN.md" Hallmark + Code Hallmark study/design-md for the DNA, then references/code-implementation.md to wire tokens into the repo
User explicitly names Stitch — "in Stitch", "list Stitch projects", "edit screen X", a Stitch project URL pasted Stitch (opt-in only) references/stitch-workflows.md
Repo plumbing after a design exists — framework wiring, CSP, islands, build config, a11y retrofit Code references/code-implementation.md

If genuinely ambiguous (the user just said /design with no context): ask what they're designing, then route — the answer almost always lands on Hallmark. Do not ask "Stitch or code?" as the opening question anymore; Stitch is no longer a coequal default.

Handing the Phase 0 brief to Hallmark

Hallmark runs its own Step 0 pre-flight (existing tokens/fonts/framework), Step 1 genre detection, and Step 2.6 theme dispatch. Phase 0's output doesn't replace those — it feeds them:

  • Pass the Purpose + Tone + Constraints + Differentiation as the brief text.
  • A named tone (brutalist / luxury / editorial / …), a named brand color, or a named multi-attribute vibe is a creative-intent signal — it fires Hallmark's custom-theme branch (one-off OKLCH palette + free-font pairing) instead of the 20-theme catalog. That's the intended behavior, not a bug.
  • Hallmark's internal genre taxonomy includes a modern-minimal genre. That is an internal label and is fine. The /design ban on "modern" applies to what the user is allowed to give as a direction — don't accept "make it modern" as a brief.

Phase 1b — Preview-then-Apply (visual mockup before code)

When the user wants to redesign or restyle an EXISTING app/UI (there's already working code to change), don't jump straight into writing CSS. Agree on the look before touching production code.

Default path — Hallmark redesign. It emits real HTML/CSS you can open in a browser, so the "preview" IS the artifact:

  1. Lock the direction (Phase 0).
  2. Skill(hallmark) → hallmark redesign <target>. It preserves copy, routes, component ownership, and information architecture, and replaces only the visual/interaction layer. It will state which files it expects to modify/create/delete before editing — deletions require explicit confirmation.
  3. Show the user the rendered result (open the HTML, or screenshot it) and get a yes before it lands in the live code path.
  4. Deploy stays with /ship — never auto-deploy.

Stitch mockup path — only when the user asks for a Stitch canvas. Kept because a throwaway canvas mockup is occasionally the cheaper way to settle a layout argument:

  1. Generate the design in Stitch — create_project (or reuse one) → generate_screen_from_text with a prompt encoding the direction + the real screen's content/data. Use MOBILE for app-like UIs (DESKTOP is often rejected by the API — on invalid argument, fall back to MOBILE).
  2. Render it for the user — get_project → parse .thumbnailScreenshot.downloadUrl (list_screens is often empty right after generation; these calls exceed the tool token cap and get saved to a file — that's success, jq the saved JSON). curl the PNG and send it with SendUserFile so the user SEES the design.
  3. ASK before applying — AskUserQuestion: "Apply this design to the live code, or iterate on the mockup first?" Do NOT port to code without a yes.
  4. On yes → port it through Hallmark, not by hand — feed the approved Stitch layout to Hallmark as the brief so the 57 slop gates still run on the code that actually ships.

Multiple-candidates path — Skill(prototype). When the honest answer to "which direction?" is we won't know until we see 2–4 of them side by side, don't pick one and iterate — build them all behind a picker:

  1. Lock the Phase 0 brief as usual, but let Phase 0's Differentiation stay open across 2–4 named directions (e.g. "editorial serif", "brutalist mono", "luxury dark").
  2. Skill(prototype) builds each as a genuinely different implementation and mounts them behind its picker harness (PICKER.md) in the running app, so the user flips through them live, in the real layout, with real data.
  3. On selection, prototype promotes the winner into the codebase and removes the harness and the losers. Then run the normal Hallmark gates on what survived.

Use this instead of a Stitch canvas when the question is direction, not layout — a rendered picker in the real app settles a taste argument faster than four static mockups.

Why preview at all (2026-07-02, ecobee dashboard): restyling directly in code produced a layout with a dead void; only after seeing a rendered version (balanced 2×2 bento + gradient hero) did the right layout become obvious. The lesson is look at it before you ship it — Hallmark's emitted HTML satisfies that just as well as a Stitch canvas, and it carries the anti-slop gates.


Cross-Mode Rules (apply regardless of engine)

  • Phase 0 direction feeds Phase 1. The Hallmark brief, the Stitch prompt, and the React/HTML code ALL must reflect the direction. If the output doesn't show the direction, the direction didn't land — redo.

  • Anti-slop applies everywhere — strictest rule wins. Two banlists are now in play and they are additive, never subtractive:

    • Hallmark's 57 gates + 6 disciplines (pre-emit self-critique, honest copy / no fabricated metrics, locked tokens, no re-drawn browser/phone/IDE chrome, mobile-verified at 320/375/414/768, no italic headers) are authoritative whenever Hallmark runs. Do not relax one of these because aesthetic-core.md is silent on it.
    • aesthetic-core.md's Absolute Bans (side-stripe borders, gradient text, decorative glassmorphism, hero-metric template, identical card grids, modal-first) and the two-altitude AI slop test (first-order category reflex + second-order category-plus-anti-reference reflex) stay binding on top of Hallmark's gates, including on Stitch output and hand-written code where Hallmark never ran.
    • Where they overlap, take the stricter reading. Neither list is a ceiling.
  • Hallmark's honest-copy discipline is non-negotiable and matches this account's global rules. Never invent a metric, testimonial, logo, or case-study count to fill a stat-led layout — use a real number, a labelled placeholder, or a different macrostructure. This is the same fabrication ban as CLAUDE.md's Document Fabrication Prevention; a landing page is not exempt because it's "just design."

  • Hallmark's implementation safety rail is binding in existing repos. It must state the exact files it will modify/create/delete before editing; deletions need explicit confirmation. Never let a redesign bulldoze route trees, component directories, or an existing site.

  • Apple HIG (Phase 0.5) is additive to every banlist. Hallmark's 57 gates + aesthetic-core.md bans + references/apple-hig.md — take the strictest reading of all three. On Apple surfaces the HIG numbers (44 pt targets, 4.5:1 contrast, 11 pt floor, Reduce Motion, safe areas, no in-app appearance toggle) are non-negotiable regardless of engine or direction.

  • Color uses OKLCH, neutrals tinted. No raw #000/#fff. Pick a color strategy (Restrained / Committed / Full palette / Drenched) before picking colors. See aesthetic-core.md → Color & Theme.

  • Theme by scene, not category. Write a one-sentence physical scene before choosing dark vs light. See aesthetic-core.md → Color & Theme.

  • Code mode runs npx impeccable detect before declaring done. 27 deterministic anti-pattern checks, no API key. See code-implementation.md → Deterministic Anti-Pattern Scan.

  • One focused edit at a time (whether edit_screens or refactoring a component).

  • No "modern" / "clean" / "sleek" as a direction. Push back to the user.

  • UI descriptions: Do not add subtitles, helper text, or descriptive copy beneath headings, labels, cards, or settings by default. Prefer one concise, self-explanatory heading or label. Only add supporting copy when the user explicitly asks for it or when it is necessary to prevent misunderstanding or error, and never use it to restate the heading.

  • Motion is gated, not decorated. Before any animation is written (by Hallmark, Stitch-port, or hand), run the four-question gate from references/aesthetic-core.md → Motion: frequency tier → named purpose → cheapest tool → curve/duration from the table. 100+/day or keyboard-initiated actions get no animation. Never ease-in, scale(0), transition: all, or a UI duration over 300 ms without a stated reason. Full rule set: Skill(animate).

  • Emil Kowalski skills (github.com/emilkowalski/skills, installed 2026-09-20 at upstream commit 85e8e23 into BOTH ~/.claude/skills/<name>/ and ~/.agents/skills/<name>/, each with a .upstream provenance file — the earlier "installed 2026-07-10" note was false; nothing had been installed). They are chained by /design at the points below and never replace aesthetic-core.md / Hallmark; strictest rule wins:

    Moment in a /design run Load Why
    Building any interactive component, or the ask is "make it feel great" Skill(emil-design-eng) Polish philosophy: press feedback, origin-aware popovers, @starting-style, blur-masked crossfades, gesture/drag rules, Motion x/y hardware-accel caveat. Ships performance-cheatsheet.md.
    Writing an animation from scratch Skill(animate) (+ its RECIPES.md) Build sequence in the right order; recipes for press / dropdown / tooltip / modal / drawer / toast / accordion / stagger / hold-to-confirm / tab indicator / scroll reveal / drag-to-dismiss
    iOS-flavored web, Capacitor / WKWebView surface, sheets, drags, springs Skill(apple-design) Apple's fluid-interface physics for the web (springs, velocity handoff, momentum projection, rubber-banding, materials, optical typography). Motion physics only — HIG rules live in references/apple-hig.md
    The output ships inside the iOS app (Capacitor shell, native SwiftUI) and you need to SEE it on a real iOS runtime, not desktop emulation baguette / serve-sim — boot an iPhone 17 Pro sim headless, baguette screenshot at 402×874 pt for the Hallmark mobile gate, describe-ui to verify labels/hit-targets, serve-sim camera --webcam for camera-driven screens; routing in ~/.claude/skills/shared/ios-sim-agent-control.md Simulator-only, never the real phone. The rendered artifact on the real runtime is the evidence for "mobile-verified", not a resized desktop viewport
    The output will be used on a phone (any mobile-facing web, PWA, Capacitor) Skill(mobile-native) — its Baseline block is a ship gate Sticky hover, tap-highlight flash, 100vh, input zoom, 300 ms tap delay, overscroll, safe areas, theme-color. None reproduce in desktop emulation
    "Which library for toasts / ⌘K / OTP / DnD / virtualization / charts / state / dark mode?" Skill(pick-ui-library) One opinionated pick per task; check package.json first, never churn an installed competitor
    Sonner is in play (toasts missing, doubled, unstyled, behind a modal, wrong theme) Skill(ask-sonner) Setup, styling ladder, troubleshooting, API.md
    Phase 1b needs several candidates, not one mockup Skill(prototype) 2–4 genuinely different builds behind a picker harness; promote the winner (see Phase 1b)
    "What could be animated here?" / "make it feel more alive" Skill(find-animation-opportunities) Read-only; proposes exact values AND lists what must NOT animate
    "Improve / audit the animations across the app" Skill(improve-animations) Read-only survey → prioritized, self-contained plans (AUDIT.md, PLAN-TEMPLATE.md)
    Before declaring ANY motion work done Skill(review-animations) Strict Before/After/Why table + Block/Approve verdict. Default is to flag. A Block is a real block
    The user describes an effect without its name Skill(animation-vocabulary) Names it so the brief/prompt is precise
    Expo / React Native target Skill(animate-expo) Reanimated / Gesture Handler / haptics, keep motion off the JS thread
    Native Swift / SwiftUI code Skill(write-swift) Swift 6 concurrency, value types, Swift Testing — pair with /ios

    Token precedence when the curves disagree: Hallmark's references/motion.md tokens (--ease-out: cubic-bezier(0.16, 1, 0.3, 1) etc.) win whenever Hallmark emitted the code, and an existing repo's tokens win over both — animate's Hard Rule 3 ("extend the codebase's tokens, don't fork them") is the tie-breaker. animate's curves (cubic-bezier(0.23, 1, 0.32, 1)) are the default only when no token system exists yet. On bounce: Hallmark says none on UI state; apple-design allows damping ≈ 0.8 only after a momentum gesture (flick, throw, drag release) — both are true at once.


Prerequisites by Engine

  • Hallmark (default) — no external prerequisites, no API key, no MCP server. Installed at ~/.claude/skills/hallmark/ (source: github.com/nutlope/hallmark, MIT, by Together AI; installed 2026-07-14 at v1.1.0). Invoke with Skill(hallmark). To update:
    ! npx skills add nutlope/hallmark
    
  • Stitch (opt-in) requires the stitch MCP server running (configured in ~/.claude/settings.json). If Stitch tools are unavailable, tell the user to run:
    ! npx @_davideast/stitch-mcp init
    
  • Code has no external prerequisites. It runs in any repo.

Reference Files (load on demand, not always)

File When loaded
references/aesthetic-core.md Always — Phase 0
references/apple-hig.md Always — Phase 0.5. Apple HIG + Liquid Glass, cited from developer.apple.com/design (2026-09-14). BINDING on Apple surfaces, baseline elsewhere; ends with the 13-line gate checklist
Skill(hallmark) → its own references/ (20 themes, 21 macrostructures, 57 slop gates, component archetypes) Default — every design/build/redesign/audit/study
references/code-implementation.md Repo plumbing, design-system wiring, or porting an approved design into the framework
references/stitch-workflows.md Only when the user explicitly names Stitch
Skill(emil-design-eng) · Skill(animate) · Skill(review-animations) · Skill(apple-design) · Skill(mobile-native) · Skill(pick-ui-library) · Skill(prototype) · Skill(ask-sonner) · Skill(find-animation-opportunities) · Skill(improve-animations) · Skill(animation-vocabulary) · Skill(animate-expo) · Skill(write-swift) Emil Kowalski skills — loaded at the moments listed in Cross-Mode Rules. review-animations is mandatory before any motion work is declared done; mobile-native Baseline is mandatory for any mobile-facing web output

This skill follows the progressive-disclosure pattern (same as /code): the entry-point SKILL.md stays lean and routes to references that load only when their mode fires. Hallmark is itself progressive — its SKILL.md pulls only the theme / macrostructure / component files the brief actually needs.


Quick Trigger Examples

  • /design build a hospital ledger landing page → Phase 0 (pick direction, e.g., "editorial / magazine") → Hallmark default Design flow
  • /design build a sticky pricing card component in this Next.js repo → Phase 0 (e.g., "brutalist raw") → Hallmark Component-scope flow (all 8 interactive states mandatory)
  • /design make example.com look less AI-generated → Phase 0 → Hallmark audit (read-only punch list) → then redesign on approval
  • /design here's a site I love: https://… → Hallmark study (extract DNA — never copies pixels; refuses template-marketplace URLs)
  • /design create a design system for example.org → Phase 0 → Hallmark for the DNA + design.md → code-implementation.md to wire the tokens
  • /design generate a hospital ledger landing page **in Stitch** → Phase 0 → Stitch mode (explicit opt-in) → generate_screen_from_text
  • /design a settings screen for the AIVA iOS app → Phase 0 → Phase 0.5 BINDING (re-read HIG Settings + Modality live) → Hallmark, then print the HIG gate checklist
  • /design add a drag-to-dismiss bottom sheet to the AIVA Capacitor app → Phase 0 → Phase 0.5 BINDING → apple-design (velocity handoff, rubber-band, spring) + animate RECIPES drag-to-dismiss + mobile-native Baseline → review-animations before done
  • /design show me three directions for the pricing page → Phase 0 with 3 named directions → prototype picker → promote the winner → Hallmark gates
  • /design what should I use for toasts in this repo → pick-ui-library (Sonner) → ask-sonner for wiring
  • /design (no context) → ask what they're designing, then route (almost always Hallmark)

04 同仓库更多 Skills

barkleesanders
barkleesanders/claude-code-starter

zi-search

暂无简介

★ 4
barkleesanders
barkleesanders/claude-code-starter

visualise

Render inline interactive visuals — SVG diagrams, HTML widgets, charts, and explainers — directly in the conversation. Use this skill whenever the user asks to visualize, diagram, chart, illustrate, or explain something visually, or when an explanation would genuinely benefit from a spatial/interactive diagram rather than text. Also triggers for: flowcharts, architecture diagrams, data visualizations, interactive explainers, comparison layouts, UI mockups, and any request containing 'show me', 'draw', 'map out', 'visualize', or 'diagram'. Even when the user doesn't explicitly ask for a visual, use this skill proactively when the topic has spatial, sequential, or systemic relationships that a diagram would clarify better than prose.

★ 4
barkleesanders
barkleesanders/claude-code-starter

video

When the user wants to create, generate, or produce video content using AI tools or programmatic frameworks. Also use when the user mentions 'video production,' 'AI video,' 'Remotion,' 'Hyperframes,' 'HeyGen,' 'Synthesia,' 'Veo,' 'Runway,' 'Kling,' 'Pika,' 'video generation,' 'AI avatar,' 'talking head video,' 'programmatic video,' 'video template,' 'explainer video,' 'product demo video,' 'video pipeline,' or 'make me a video.' Use this for video creation, generation, and production workflows. For video content strategy and what to post, see social-content. For paid video ad creative, see ad-creative.

★ 4
barkleesanders
barkleesanders/claude-code-starter

manim-video

Production pipeline for mathematical and technical animations using Manim Community Edition. Creates 3Blue1Brown-style explainer videos, algorithm visualizations, equation derivations, architecture diagrams, and data stories. Use when users request: animated explanations, math animations, concept visualizations, algorithm walkthroughs, technical explainers, 3Blue1Brown style videos, or any programmatic animation with geometric/mathematical content.

★ 4
barkleesanders
barkleesanders/claude-code-starter

video-use

Edit any video by conversation. Transcribe, cut, color grade, generate overlay animations, burn subtitles — for talking heads, montages, tutorials, travel, interviews. No presets, no menus. Ask questions, confirm the plan, execute, iterate, persist. Production-correctness rules are hard; everything else is artistic freedom.

★ 4
barkleesanders
barkleesanders/claude-code-starter

ui-improver

暂无简介

★ 4