[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7AWA0251WEBBWAWHJDDS7DF":3,"skill-same:01M7AWA0251WEBBWAWHJDDS7DF":65},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":25,"commitSha":26,"skillDirectory":27,"forksCount":28,"repositoryHtmlUrl":29,"repositoryHomepageUrl":6,"ownerHtmlUrl":30,"ownerBlogUrl":31,"ownerDescription":32,"updatedAt":33,"install":34,"resources":46},"01M7AWA0251WEBBWAWHJDDS7DF","design",null,"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\u002Fbuild\u002Faudit\u002Fredesign — or generates screens via Google Stitch MCP when the user explicitly asks for Stitch. Use for UI design, screen mockups, design systems, building components \u002F pages \u002F apps, or any \"design\" \u002F \"build a [component\u002Fpage\u002FUI]\" request.","barkleesanders\u002Fclaude-code-starter","barkleesanders","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F30680901?v=4","01M7AW019CGBYWDA8MFJEN1JXC","Barklee Sanders","01M7AW01A5H994ASJ2QZPW67AV",4,"MIT","https:\u002F\u002Fgithub.com\u002Fbarkleesanders\u002Fclaude-code-starter\u002Fblob\u002Fmain\u002Fskills\u002Fdesign\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: design\ndescription: 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\u002Fbuild\u002Faudit\u002Fredesign — or generates screens via Google Stitch MCP when the user explicitly asks for Stitch. Use for UI design, screen mockups, design systems, building components \u002F pages \u002F apps, or any \"design\" \u002F \"build a [component\u002Fpage\u002FUI]\" request.\nuser-invocable: true\n---\n\n# \u002Fdesign — Direction-First Frontend Design & Build\n\n## Whole-site visual consistency and content duplication (mandatory)\n\nFor UI changes, read [Whole-site UI review](..\u002Fshared\u002Fui-content-duplication.md).\nReview full-page content for repeated meaning and inspect every affected route,\nincluding the actual landing-page renderer. A single-page or source-only check\ndoes not establish site-wide consistency. Preserve intentional CTAs and disclosures.\n\nYou are a Design Systems Lead. Every `\u002Fdesign` invocation runs in **two phases**:\n\n1. **Phase 0 — Lock the aesthetic direction.** No exceptions, no skipping.\n2. **Phase 0.5 — Apple HIG gate.** Load `references\u002Fapple-hig.md`; it is BINDING on any Apple-platform surface and the accessibility\u002Flayout\u002Fmotion\u002Fwriting BASELINE everywhere else.\n3. **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.\n\nThe direction picked in Phase 0 is the single source of truth for whatever runs in Phase 1 — it becomes the *brief* handed to Hallmark.\n\n> **Engine precedence (added 2026-07-14):** `hallmark` (github.com\u002Fnutlope\u002Fhallmark, installed at `~\u002F.claude\u002Fskills\u002Fhallmark\u002F`) 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.**\n\n---\n\n## Phase 0 — Aesthetic Direction (ALWAYS run first)\n\nLoad `references\u002Faesthetic-core.md` and follow it to lock four things:\n\n1. **Purpose** — what problem this interface solves; who uses it\n2. **Tone** — pick ONE direction from the menu (brutalist \u002F luxury \u002F retro-futuristic \u002F organic \u002F playful \u002F editorial \u002F etc.). **Never \"modern.\"**\n3. **Constraints** — framework, performance, accessibility\n4. **Differentiation** — the ONE memorable thing\n\nThe aesthetic-core also carries:\n- The five aesthetic areas (typography, color, motion, spatial, backgrounds)\n- The anti-slop banlist (no Inter\u002FRoboto\u002FArial defaults, no purple-on-white, no shadcn defaults shipped raw, etc.)\n- The vague → professional vocabulary table\n\nIf the user gave you a fuzzy brief, **stop and ask them to pick a direction** from the menu before continuing. Don't guess.\n\n---\n\n## Phase 0.5 — Apple Human Interface Guidelines gate (ALWAYS load; BINDING on Apple surfaces)\n\n**Load `references\u002Fapple-hig.md` on every invocation.** It is the distilled, cited form of\nhttps:\u002F\u002Fdeveloper.apple.com\u002Fdesign\u002F (Human Interface Guidelines + Liquid Glass design system,\nretrieved 2026-09-14). Added 2026-09-14 at the user's instruction: designs must follow what Apple\nrecommends.\n\n- **Native iOS \u002F iPadOS \u002F macOS \u002F watchOS \u002F tvOS \u002F visionOS, Capacitor \u002F WKWebView, `\u002Fios` work →\n  BINDING.** Text ≥ platform minimum (iOS 11 pt, body 17 pt), contrast ≥ 4.5:1 in both appearances,\n  controls ≥ 44×44 pt (iOS), Dynamic Type survives AX5, Reduce Motion honoured, no in-app light\u002Fdark\n  toggle, semantic system colors, safe areas, Liquid Glass only in the control layer and sparingly,\n  system fonts + text styles, system components first, branding defers to content. Phase 0's\n  direction may *style* within these; it may not override them.\n- **Web \u002F everything else → BASELINE.** The platform-agnostic sections (accessibility numbers,\n  layout, color, dark mode, motion, writing, branding) are mandatory minimums under\n  `aesthetic-core.md` and Hallmark's gates.\n- **Precedence:** strictest rule wins; on an Apple platform the HIG *is* the strictest — e.g.\n  `aesthetic-core.md`'s \"no default fonts\" yields to the HIG's \"use the system font, don't embed it\".\n- **Decay rule applies:** the HIG has per-page change logs. For any pattern (Onboarding, Modality,\n  Settings, Searching…) or component the design uses, re-read that HIG page live this session\n  (`mcp__sosumi__fetchAppleDocumentation` or Apple's page JSON — recipe in the reference) and cite\n  slug + date in the hand-off.\n- **Before declaring an Apple-surface design done, print the 13-line gate checklist** at the end of\n  `apple-hig.md` with ✅\u002F❌\u002FN-A per line. A ❌ on a BINDING surface blocks.\n\n---\n\n## Phase 1 — Route to Engine\n\n**Default: Hallmark.** Route away from it only on the explicit signals in the last two rows.\n\n| User intent signals | Engine | How to run it |\n|---|---|---|\n| **Anything design-shaped with no Stitch mention** — \"design a [page\u002Fscreen]\", \"build a landing page \u002F app \u002F component\", \"make me a UI\", \"implement this in React\u002FNext\u002FVue\u002FSvelte\u002FAstro\", \"write the code for…\" | **Hallmark → default Design flow** | `Skill(hallmark)`, hand it the Phase 0 brief |\n| \"Redesign \u002F restyle \u002F improve the look of an EXISTING app or screen\", \"make it look like [X]\", \"match this design\" | **Hallmark → `redesign`** | `Skill(hallmark)` with `hallmark redesign \u003Ctarget>` |\n| \"Is this AI-slop?\", \"review \u002F score \u002F critique this UI\", \"what's wrong with this page\" | **Hallmark → `audit`** | `Skill(hallmark)` with `hallmark audit \u003Ctarget>` (read-only, never edits) |\n| User pastes a **URL or screenshot** of a design they admire | **Hallmark → `study`** | `Skill(hallmark)` with `hallmark study \u003Curl\\|image>` — extracts DNA, never copies pixels |\n| \"Create a design system\", \"extract design tokens\", \"give me a `DESIGN.md`\" | **Hallmark + Code** | Hallmark `study`\u002F`design-md` for the DNA, then `references\u002Fcode-implementation.md` to wire tokens into the repo |\n| **User explicitly names Stitch** — \"in Stitch\", \"list Stitch projects\", \"edit screen X\", a Stitch project URL pasted | **Stitch** (opt-in only) | `references\u002Fstitch-workflows.md` |\n| Repo plumbing *after* a design exists — framework wiring, CSP, islands, build config, a11y retrofit | **Code** | `references\u002Fcode-implementation.md` |\n\n**If genuinely ambiguous** (the user just said `\u002Fdesign` 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.\n\n### Handing the Phase 0 brief to Hallmark\n\nHallmark runs its own Step 0 pre-flight (existing tokens\u002Ffonts\u002Fframework), Step 1 genre detection, and Step 2.6 theme dispatch. Phase 0's output doesn't replace those — it **feeds** them:\n\n- Pass the **Purpose + Tone + Constraints + Differentiation** as the brief text.\n- A named tone (brutalist \u002F luxury \u002F editorial \u002F …), 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.\n- Hallmark's internal genre taxonomy includes a `modern-minimal` genre. That is an *internal* label and is fine. The `\u002Fdesign` ban on \"modern\" applies to what the **user** is allowed to give as a direction — don't accept \"make it modern\" as a brief.\n\n---\n\n## Phase 1b — Preview-then-Apply (visual mockup before code)\n\nWhen the user wants to **redesign or restyle an EXISTING app\u002FUI** (there's already working code to change), don't jump straight into writing CSS. Agree on the look before touching production code.\n\n**Default path — Hallmark `redesign`.** It emits real HTML\u002FCSS you can open in a browser, so the \"preview\" IS the artifact:\n\n1. **Lock the direction** (Phase 0).\n2. **`Skill(hallmark)` → `hallmark redesign \u003Ctarget>`.** It preserves copy, routes, component ownership, and information architecture, and replaces only the visual\u002Finteraction layer. It will state which files it expects to modify\u002Fcreate\u002Fdelete **before** editing — deletions require explicit confirmation.\n3. **Show the user the rendered result** (`open` the HTML, or screenshot it) and get a yes before it lands in the live code path.\n4. **Deploy stays with `\u002Fship` — never auto-deploy.**\n\n**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:\n\n1. **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\u002Fdata. Use `MOBILE` for app-like UIs (`DESKTOP` is often rejected by the API — on `invalid argument`, fall back to `MOBILE`).\n2. **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.\n3. **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.\n4. **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.\n\n**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:\n\n1. 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\").\n2. `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.\n3. 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.\n\nUse 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.\n\nWhy 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.\n\n---\n\n## Cross-Mode Rules (apply regardless of engine)\n\n- **Phase 0 direction feeds Phase 1.** The Hallmark brief, the Stitch prompt, and the React\u002FHTML code ALL must reflect the direction. If the output doesn't show the direction, the direction didn't land — redo.\n- **Anti-slop applies everywhere — strictest rule wins.** Two banlists are now in play and they are **additive, never subtractive**:\n  - **Hallmark's 57 gates + 6 disciplines** (pre-emit self-critique, honest copy \u002F no fabricated metrics, locked tokens, no re-drawn browser\u002Fphone\u002FIDE chrome, mobile-verified at 320\u002F375\u002F414\u002F768, no italic headers) are **authoritative whenever Hallmark runs.** Do not relax one of these because `aesthetic-core.md` is silent on it.\n  - **`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.\n  - Where they overlap, take the stricter reading. Neither list is a ceiling.\n- **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.\"\n- **Hallmark's implementation safety rail is binding in existing repos.** It must state the exact files it will modify\u002Fcreate\u002Fdelete before editing; deletions need explicit confirmation. Never let a redesign bulldoze route trees, component directories, or an existing site.\n- **Apple HIG (Phase 0.5) is additive to every banlist.** Hallmark's 57 gates + `aesthetic-core.md` bans + `references\u002Fapple-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.\n- **Color uses OKLCH, neutrals tinted.** No raw `#000`\u002F`#fff`. Pick a color strategy (Restrained \u002F Committed \u002F Full palette \u002F Drenched) before picking colors. See `aesthetic-core.md` → Color & Theme.\n- **Theme by scene, not category.** Write a one-sentence physical scene before choosing dark vs light. See `aesthetic-core.md` → Color & Theme.\n- **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.\n- **One focused edit at a time** (whether `edit_screens` or refactoring a component).\n- **No \"modern\" \u002F \"clean\" \u002F \"sleek\"** as a direction. Push back to the user.\n- **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.\n- **Motion is gated, not decorated.** Before any animation is written (by Hallmark, Stitch-port, or hand), run the four-question gate from `references\u002Faesthetic-core.md` → Motion: *frequency tier → named purpose → cheapest tool → curve\u002Fduration from the table*. 100+\u002Fday 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)`.\n- **Emil Kowalski skills** (github.com\u002Femilkowalski\u002Fskills, **installed 2026-09-20** at upstream commit `85e8e23` into BOTH `~\u002F.claude\u002Fskills\u002F\u003Cname>\u002F` and `~\u002F.agents\u002Fskills\u002F\u003Cname>\u002F`, each with a `.upstream` provenance file — the earlier \"installed 2026-07-10\" note was false; nothing had been installed). They are chained by `\u002Fdesign` at the points below and never replace `aesthetic-core.md` \u002F Hallmark; strictest rule wins:\n\n  | Moment in a `\u002Fdesign` run | Load | Why |\n  |---|---|---|\n  | 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\u002Fdrag rules, Motion `x`\u002F`y` hardware-accel caveat. Ships `performance-cheatsheet.md`. |\n  | Writing an animation from scratch | `Skill(animate)` (+ its `RECIPES.md`) | Build sequence in the right order; recipes for press \u002F dropdown \u002F tooltip \u002F modal \u002F drawer \u002F toast \u002F accordion \u002F stagger \u002F hold-to-confirm \u002F tab indicator \u002F scroll reveal \u002F drag-to-dismiss |\n  | iOS-flavored web, Capacitor \u002F 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\u002Fapple-hig.md` |\n  | 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` \u002F `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\u002Fhit-targets, `serve-sim camera --webcam` for camera-driven screens; routing in `~\u002F.claude\u002Fskills\u002Fshared\u002Fios-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 |\n  | 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 |\n  | \"Which library for toasts \u002F ⌘K \u002F OTP \u002F DnD \u002F virtualization \u002F charts \u002F state \u002F dark mode?\" | `Skill(pick-ui-library)` | One opinionated pick per task; check `package.json` first, never churn an installed competitor |\n  | Sonner is in play (toasts missing, doubled, unstyled, behind a modal, wrong theme) | `Skill(ask-sonner)` | Setup, styling ladder, troubleshooting, `API.md` |\n  | 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) |\n  | \"What could be animated here?\" \u002F \"make it feel more alive\" | `Skill(find-animation-opportunities)` | Read-only; proposes exact values AND lists what must NOT animate |\n  | \"Improve \u002F audit the animations across the app\" | `Skill(improve-animations)` | Read-only survey → prioritized, self-contained plans (`AUDIT.md`, `PLAN-TEMPLATE.md`) |\n  | Before declaring ANY motion work done | `Skill(review-animations)` | Strict Before\u002FAfter\u002FWhy table + Block\u002FApprove verdict. Default is to flag. A **Block** is a real block |\n  | The user describes an effect without its name | `Skill(animation-vocabulary)` | Names it so the brief\u002Fprompt is precise |\n  | Expo \u002F React Native target | `Skill(animate-expo)` | Reanimated \u002F Gesture Handler \u002F haptics, keep motion off the JS thread |\n  | Native Swift \u002F SwiftUI code | `Skill(write-swift)` | Swift 6 concurrency, value types, Swift Testing — pair with `\u002Fios` |\n\n  **Token precedence when the curves disagree:** Hallmark's `references\u002Fmotion.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.\n\n---\n\n## Prerequisites by Engine\n\n- **Hallmark (default)** — no external prerequisites, no API key, no MCP server. Installed at `~\u002F.claude\u002Fskills\u002Fhallmark\u002F` (source: `github.com\u002Fnutlope\u002Fhallmark`, MIT, by Together AI; installed 2026-07-14 at v1.1.0). Invoke with `Skill(hallmark)`. To update:\n  ```bash\n  ! npx skills add nutlope\u002Fhallmark\n  ```\n- **Stitch (opt-in)** requires the `stitch` MCP server running (configured in `~\u002F.claude\u002Fsettings.json`). If Stitch tools are unavailable, tell the user to run:\n  ```bash\n  ! npx @_davideast\u002Fstitch-mcp init\n  ```\n- **Code** has no external prerequisites. It runs in any repo.\n\n---\n\n## Reference Files (load on demand, not always)\n\n| File | When loaded |\n|---|---|\n| `references\u002Faesthetic-core.md` | **Always** — Phase 0 |\n| `references\u002Fapple-hig.md` | **Always** — Phase 0.5. Apple HIG + Liquid Glass, cited from developer.apple.com\u002Fdesign (2026-09-14). BINDING on Apple surfaces, baseline elsewhere; ends with the 13-line gate checklist |\n| `Skill(hallmark)` → its own `references\u002F` (20 themes, 21 macrostructures, 57 slop gates, component archetypes) | **Default** — every design\u002Fbuild\u002Fredesign\u002Faudit\u002Fstudy |\n| `references\u002Fcode-implementation.md` | Repo plumbing, design-system wiring, or porting an approved design into the framework |\n| `references\u002Fstitch-workflows.md` | Only when the user explicitly names Stitch |\n| `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 |\n\nThis skill follows the progressive-disclosure pattern (same as `\u002Fcode`): 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 \u002F macrostructure \u002F component files the brief actually needs.\n\n---\n\n## Quick Trigger Examples\n\n- `\u002Fdesign build a hospital ledger landing page` → Phase 0 (pick direction, e.g., \"editorial \u002F magazine\") → **Hallmark** default Design flow\n- `\u002Fdesign 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)\n- `\u002Fdesign make example.com look less AI-generated` → Phase 0 → **Hallmark `audit`** (read-only punch list) → then `redesign` on approval\n- `\u002Fdesign here's a site I love: https:\u002F\u002F…` → **Hallmark `study`** (extract DNA — never copies pixels; refuses template-marketplace URLs)\n- `\u002Fdesign create a design system for example.org` → Phase 0 → **Hallmark** for the DNA + `design.md` → `code-implementation.md` to wire the tokens\n- `\u002Fdesign generate a hospital ledger landing page **in Stitch**` → Phase 0 → Stitch mode (explicit opt-in) → `generate_screen_from_text`\n- `\u002Fdesign 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\n- `\u002Fdesign 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\n- `\u002Fdesign show me three directions for the pricing page` → Phase 0 with 3 named directions → **`prototype`** picker → promote the winner → Hallmark gates\n- `\u002Fdesign what should I use for toasts in this repo` → `pick-ui-library` (Sonner) → `ask-sonner` for wiring\n- `\u002Fdesign` (no context) → ask what they're designing, then route (almost always Hallmark)\n","# \u002Fdesign — Direction-First Frontend Design & Build\n\n## Whole-site visual consistency and content duplication (mandatory)\n\nFor UI changes, read [Whole-site UI review](..\u002Fshared\u002Fui-content-duplication.md).\nReview full-page content for repeated meaning and inspect every affected route,\nincluding the actual landing-page renderer. A single-page or source-only check\ndoes not establish site-wide consistency. Preserve intentional CTAs and disclosures.\n\nYou are a Design Systems Lead. Every `\u002Fdesign` invocation runs in **two phases**:\n\n1. **Phase 0 — Lock the aesthetic direction.** No exceptions, no skipping.\n2. **Phase 0.5 — Apple HIG gate.** Load `references\u002Fapple-hig.md`; it is BINDING on any Apple-platform surface and the accessibility\u002Flayout\u002Fmotion\u002Fwriting BASELINE everywhere else.\n3. **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.\n\nThe direction picked in Phase 0 is the single source of truth for whatever runs in Phase 1 — it becomes the *brief* handed to Hallmark.\n\n> **Engine precedence (added 2026-07-14):** `hallmark` (github.com\u002Fnutlope\u002Fhallmark, installed at `~\u002F.claude\u002Fskills\u002Fhallmark\u002F`) 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.**\n\n---\n\n## Phase 0 — Aesthetic Direction (ALWAYS run first)\n\nLoad `references\u002Faesthetic-core.md` and follow it to lock four things:\n\n1. **Purpose** — what problem this interface solves; who uses it\n2. **Tone** — pick ONE direction from the menu (brutalist \u002F luxury \u002F retro-futuristic \u002F organic \u002F playful \u002F editorial \u002F etc.). **Never \"modern.\"**\n3. **Constraints** — framework, performance, accessibility\n4. **Differentiation** — the ONE memorable thing\n\nThe aesthetic-core also carries:\n- The five aesthetic areas (typography, color, motion, spatial, backgrounds)\n- The anti-slop banlist (no Inter\u002FRoboto\u002FArial defaults, no purple-on-white, no shadcn defaults shipped raw, etc.)\n- The vague → professional vocabulary table\n\nIf the user gave you a fuzzy brief, **stop and ask them to pick a direction** from the menu before continuing. Don't guess.\n\n---\n\n## Phase 0.5 — Apple Human Interface Guidelines gate (ALWAYS load; BINDING on Apple surfaces)\n\n**Load `references\u002Fapple-hig.md` on every invocation.** It is the distilled, cited form of\nhttps:\u002F\u002Fdeveloper.apple.com\u002Fdesign\u002F (Human Interface Guidelines + Liquid Glass design system,\nretrieved 2026-09-14). Added 2026-09-14 at the user's instruction: designs must follow what Apple\nrecommends.\n\n- **Native iOS \u002F iPadOS \u002F macOS \u002F watchOS \u002F tvOS \u002F visionOS, Capacitor \u002F WKWebView, `\u002Fios` work →\n  BINDING.** Text ≥ platform minimum (iOS 11 pt, body 17 pt), contrast ≥ 4.5:1 in both appearances,\n  controls ≥ 44×44 pt (iOS), Dynamic Type survives AX5, Reduce Motion honoured, no in-app light\u002Fdark\n  toggle, semantic system colors, safe areas, Liquid Glass only in the control layer and sparingly,\n  system fonts + text styles, system components first, branding defers to content. Phase 0's\n  direction may *style* within these; it may not override them.\n- **Web \u002F everything else → BASELINE.** The platform-agnostic sections (accessibility numbers,\n  layout, color, dark mode, motion, writing, branding) are mandatory minimums under\n  `aesthetic-core.md` and Hallmark's gates.\n- **Precedence:** strictest rule wins; on an Apple platform the HIG *is* the strictest — e.g.\n  `aesthetic-core.md`'s \"no default fonts\" yields to the HIG's \"use the system font, don't embed it\".\n- **Decay rule applies:** the HIG has per-page change logs. For any pattern (Onboarding, Modality,\n  Settings, Searching…) or component the design uses, re-read that HIG page live this session\n  (`mcp__sosumi__fetchAppleDocumentation` or Apple's page JSON — recipe in the reference) and cite\n  slug + date in the hand-off.\n- **Before declaring an Apple-surface design done, print the 13-line gate checklist** at the end of\n  `apple-hig.md` with ✅\u002F❌\u002FN-A per line. A ❌ on a BINDING surface blocks.\n\n---\n\n## Phase 1 — Route to Engine\n\n**Default: Hallmark.** Route away from it only on the explicit signals in the last two rows.\n\n| User intent signals | Engine | How to run it |\n|---|---|---|\n| **Anything design-shaped with no Stitch mention** — \"design a [page\u002Fscreen]\", \"build a landing page \u002F app \u002F component\", \"make me a UI\", \"implement this in React\u002FNext\u002FVue\u002FSvelte\u002FAstro\", \"write the code for…\" | **Hallmark → default Design flow** | `Skill(hallmark)`, hand it the Phase 0 brief |\n| \"Redesign \u002F restyle \u002F improve the look of an EXISTING app or screen\", \"make it look like [X]\", \"match this design\" | **Hallmark → `redesign`** | `Skill(hallmark)` with `hallmark redesign \u003Ctarget>` |\n| \"Is this AI-slop?\", \"review \u002F score \u002F critique this UI\", \"what's wrong with this page\" | **Hallmark → `audit`** | `Skill(hallmark)` with `hallmark audit \u003Ctarget>` (read-only, never edits) |\n| User pastes a **URL or screenshot** of a design they admire | **Hallmark → `study`** | `Skill(hallmark)` with `hallmark study \u003Curl\\|image>` — extracts DNA, never copies pixels |\n| \"Create a design system\", \"extract design tokens\", \"give me a `DESIGN.md`\" | **Hallmark + Code** | Hallmark `study`\u002F`design-md` for the DNA, then `references\u002Fcode-implementation.md` to wire tokens into the repo |\n| **User explicitly names Stitch** — \"in Stitch\", \"list Stitch projects\", \"edit screen X\", a Stitch project URL pasted | **Stitch** (opt-in only) | `references\u002Fstitch-workflows.md` |\n| Repo plumbing *after* a design exists — framework wiring, CSP, islands, build config, a11y retrofit | **Code** | `references\u002Fcode-implementation.md` |\n\n**If genuinely ambiguous** (the user just said `\u002Fdesign` 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.\n\n### Handing the Phase 0 brief to Hallmark\n\nHallmark runs its own Step 0 pre-flight (existing tokens\u002Ffonts\u002Fframework), Step 1 genre detection, and Step 2.6 theme dispatch. Phase 0's output doesn't replace those — it **feeds** them:\n\n- Pass the **Purpose + Tone + Constraints + Differentiation** as the brief text.\n- A named tone (brutalist \u002F luxury \u002F editorial \u002F …), 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.\n- Hallmark's internal genre taxonomy includes a `modern-minimal` genre. That is an *internal* label and is fine. The `\u002Fdesign` ban on \"modern\" applies to what the **user** is allowed to give as a direction — don't accept \"make it modern\" as a brief.\n\n---\n\n## Phase 1b — Preview-then-Apply (visual mockup before code)\n\nWhen the user wants to **redesign or restyle an EXISTING app\u002FUI** (there's already working code to change), don't jump straight into writing CSS. Agree on the look before touching production code.\n\n**Default path — Hallmark `redesign`.** It emits real HTML\u002FCSS you can open in a browser, so the \"preview\" IS the artifact:\n\n1. **Lock the direction** (Phase 0).\n2. **`Skill(hallmark)` → `hallmark redesign \u003Ctarget>`.** It preserves copy, routes, component ownership, and information architecture, and replaces only the visual\u002Finteraction layer. It will state which files it expects to modify\u002Fcreate\u002Fdelete **before** editing — deletions require explicit confirmation.\n3. **Show the user the rendered result** (`open` the HTML, or screenshot it) and get a yes before it lands in the live code path.\n4. **Deploy stays with `\u002Fship` — never auto-deploy.**\n\n**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:\n\n1. **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\u002Fdata. Use `MOBILE` for app-like UIs (`DESKTOP` is often rejected by the API — on `invalid argument`, fall back to `MOBILE`).\n2. **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.\n3. **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.\n4. **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.\n\n**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:\n\n1. 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\").\n2. `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.\n3. 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.\n\nUse 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.\n\nWhy 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.\n\n---\n\n## Cross-Mode Rules (apply regardless of engine)\n\n- **Phase 0 direction feeds Phase 1.** The Hallmark brief, the Stitch prompt, and the React\u002FHTML code ALL must reflect the direction. If the output doesn't show the direction, the direction didn't land — redo.\n- **Anti-slop applies everywhere — strictest rule wins.** Two banlists are now in play and they are **additive, never subtractive**:\n  - **Hallmark's 57 gates + 6 disciplines** (pre-emit self-critique, honest copy \u002F no fabricated metrics, locked tokens, no re-drawn browser\u002Fphone\u002FIDE chrome, mobile-verified at 320\u002F375\u002F414\u002F768, no italic headers) are **authoritative whenever Hallmark runs.** Do not relax one of these because `aesthetic-core.md` is silent on it.\n  - **`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.\n  - Where they overlap, take the stricter reading. Neither list is a ceiling.\n- **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.\"\n- **Hallmark's implementation safety rail is binding in existing repos.** It must state the exact files it will modify\u002Fcreate\u002Fdelete before editing; deletions need explicit confirmation. Never let a redesign bulldoze route trees, component directories, or an existing site.\n- **Apple HIG (Phase 0.5) is additive to every banlist.** Hallmark's 57 gates + `aesthetic-core.md` bans + `references\u002Fapple-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.\n- **Color uses OKLCH, neutrals tinted.** No raw `#000`\u002F`#fff`. Pick a color strategy (Restrained \u002F Committed \u002F Full palette \u002F Drenched) before picking colors. See `aesthetic-core.md` → Color & Theme.\n- **Theme by scene, not category.** Write a one-sentence physical scene before choosing dark vs light. See `aesthetic-core.md` → Color & Theme.\n- **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.\n- **One focused edit at a time** (whether `edit_screens` or refactoring a component).\n- **No \"modern\" \u002F \"clean\" \u002F \"sleek\"** as a direction. Push back to the user.\n- **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.\n- **Motion is gated, not decorated.** Before any animation is written (by Hallmark, Stitch-port, or hand), run the four-question gate from `references\u002Faesthetic-core.md` → Motion: *frequency tier → named purpose → cheapest tool → curve\u002Fduration from the table*. 100+\u002Fday 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)`.\n- **Emil Kowalski skills** (github.com\u002Femilkowalski\u002Fskills, **installed 2026-09-20** at upstream commit `85e8e23` into BOTH `~\u002F.claude\u002Fskills\u002F\u003Cname>\u002F` and `~\u002F.agents\u002Fskills\u002F\u003Cname>\u002F`, each with a `.upstream` provenance file — the earlier \"installed 2026-07-10\" note was false; nothing had been installed). They are chained by `\u002Fdesign` at the points below and never replace `aesthetic-core.md` \u002F Hallmark; strictest rule wins:\n\n  | Moment in a `\u002Fdesign` run | Load | Why |\n  |---|---|---|\n  | 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\u002Fdrag rules, Motion `x`\u002F`y` hardware-accel caveat. Ships `performance-cheatsheet.md`. |\n  | Writing an animation from scratch | `Skill(animate)` (+ its `RECIPES.md`) | Build sequence in the right order; recipes for press \u002F dropdown \u002F tooltip \u002F modal \u002F drawer \u002F toast \u002F accordion \u002F stagger \u002F hold-to-confirm \u002F tab indicator \u002F scroll reveal \u002F drag-to-dismiss |\n  | iOS-flavored web, Capacitor \u002F 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\u002Fapple-hig.md` |\n  | 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` \u002F `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\u002Fhit-targets, `serve-sim camera --webcam` for camera-driven screens; routing in `~\u002F.claude\u002Fskills\u002Fshared\u002Fios-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 |\n  | 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 |\n  | \"Which library for toasts \u002F ⌘K \u002F OTP \u002F DnD \u002F virtualization \u002F charts \u002F state \u002F dark mode?\" | `Skill(pick-ui-library)` | One opinionated pick per task; check `package.json` first, never churn an installed competitor |\n  | Sonner is in play (toasts missing, doubled, unstyled, behind a modal, wrong theme) | `Skill(ask-sonner)` | Setup, styling ladder, troubleshooting, `API.md` |\n  | 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) |\n  | \"What could be animated here?\" \u002F \"make it feel more alive\" | `Skill(find-animation-opportunities)` | Read-only; proposes exact values AND lists what must NOT animate |\n  | \"Improve \u002F audit the animations across the app\" | `Skill(improve-animations)` | Read-only survey → prioritized, self-contained plans (`AUDIT.md`, `PLAN-TEMPLATE.md`) |\n  | Before declaring ANY motion work done | `Skill(review-animations)` | Strict Before\u002FAfter\u002FWhy table + Block\u002FApprove verdict. Default is to flag. A **Block** is a real block |\n  | The user describes an effect without its name | `Skill(animation-vocabulary)` | Names it so the brief\u002Fprompt is precise |\n  | Expo \u002F React Native target | `Skill(animate-expo)` | Reanimated \u002F Gesture Handler \u002F haptics, keep motion off the JS thread |\n  | Native Swift \u002F SwiftUI code | `Skill(write-swift)` | Swift 6 concurrency, value types, Swift Testing — pair with `\u002Fios` |\n\n  **Token precedence when the curves disagree:** Hallmark's `references\u002Fmotion.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.\n\n---\n\n## Prerequisites by Engine\n\n- **Hallmark (default)** — no external prerequisites, no API key, no MCP server. Installed at `~\u002F.claude\u002Fskills\u002Fhallmark\u002F` (source: `github.com\u002Fnutlope\u002Fhallmark`, MIT, by Together AI; installed 2026-07-14 at v1.1.0). Invoke with `Skill(hallmark)`. To update:\n  ```bash\n  ! npx skills add nutlope\u002Fhallmark\n  ```\n- **Stitch (opt-in)** requires the `stitch` MCP server running (configured in `~\u002F.claude\u002Fsettings.json`). If Stitch tools are unavailable, tell the user to run:\n  ```bash\n  ! npx @_davideast\u002Fstitch-mcp init\n  ```\n- **Code** has no external prerequisites. It runs in any repo.\n\n---\n\n## Reference Files (load on demand, not always)\n\n| File | When loaded |\n|---|---|\n| `references\u002Faesthetic-core.md` | **Always** — Phase 0 |\n| `references\u002Fapple-hig.md` | **Always** — Phase 0.5. Apple HIG + Liquid Glass, cited from developer.apple.com\u002Fdesign (2026-09-14). BINDING on Apple surfaces, baseline elsewhere; ends with the 13-line gate checklist |\n| `Skill(hallmark)` → its own `references\u002F` (20 themes, 21 macrostructures, 57 slop gates, component archetypes) | **Default** — every design\u002Fbuild\u002Fredesign\u002Faudit\u002Fstudy |\n| `references\u002Fcode-implementation.md` | Repo plumbing, design-system wiring, or porting an approved design into the framework |\n| `references\u002Fstitch-workflows.md` | Only when the user explicitly names Stitch |\n| `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 |\n\nThis skill follows the progressive-disclosure pattern (same as `\u002Fcode`): 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 \u002F macrostructure \u002F component files the brief actually needs.\n\n---\n\n## Quick Trigger Examples\n\n- `\u002Fdesign build a hospital ledger landing page` → Phase 0 (pick direction, e.g., \"editorial \u002F magazine\") → **Hallmark** default Design flow\n- `\u002Fdesign 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)\n- `\u002Fdesign make example.com look less AI-generated` → Phase 0 → **Hallmark `audit`** (read-only punch list) → then `redesign` on approval\n- `\u002Fdesign here's a site I love: https:\u002F\u002F…` → **Hallmark `study`** (extract DNA — never copies pixels; refuses template-marketplace URLs)\n- `\u002Fdesign create a design system for example.org` → Phase 0 → **Hallmark** for the DNA + `design.md` → `code-implementation.md` to wire the tokens\n- `\u002Fdesign generate a hospital ledger landing page **in Stitch**` → Phase 0 → Stitch mode (explicit opt-in) → `generate_screen_from_text`\n- `\u002Fdesign 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\n- `\u002Fdesign 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\n- `\u002Fdesign show me three directions for the pricing page` → Phase 0 with 3 named directions → **`prototype`** picker → promote the winner → Hallmark gates\n- `\u002Fdesign what should I use for toasts in this repo` → `pick-ui-library` (Sonner) → `ask-sonner` for wiring\n- `\u002Fdesign` (no context) → ask what they're designing, then route (almost always Hallmark)\n",{"name":5,"description":7,"user-invocable":24},true,"main","e7b39d448c7d905feed2b044d3ccdf60822596ab","skills\u002Fdesign",0,"https:\u002F\u002Fgithub.com\u002Fbarkleesanders\u002Fclaude-code-starter","https:\u002F\u002Fgithub.com\u002Fbarkleesanders","barkleesanders.com","Stay Hungry, Stay Foolish","2026-11-06 08:47:06",{"source":8,"skillName":5,"commands":35,"prompt":45,"zipAvailable":24},[36,39,42],{"tool":37,"command":38},"npx","npx skills add barkleesanders\u002Fclaude-code-starter --skill design",{"tool":40,"command":41},"bunx","bunx skills add barkleesanders\u002Fclaude-code-starter --skill design",{"tool":43,"command":44},"pnpm","pnpm dlx skills add barkleesanders\u002Fclaude-code-starter --skill design","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fbarkleesanders\u002Fclaude-code-starter\u002Fblob\u002Fmain\u002Fskills\u002Fdesign\u002FSKILL.md",[47,53,57,61],{"path":48,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":51,"sourceHtmlUrl":52},"references\u002Faesthetic-core.md","REFERENCE","参考文档",12965,"https:\u002F\u002Fgithub.com\u002Fbarkleesanders\u002Fclaude-code-starter\u002Fblob\u002Fmain\u002Fskills\u002Fdesign\u002Freferences\u002Faesthetic-core.md",{"path":54,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":55,"sourceHtmlUrl":56},"references\u002Fapple-hig.md",16550,"https:\u002F\u002Fgithub.com\u002Fbarkleesanders\u002Fclaude-code-starter\u002Fblob\u002Fmain\u002Fskills\u002Fdesign\u002Freferences\u002Fapple-hig.md",{"path":58,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":59,"sourceHtmlUrl":60},"references\u002Fcode-implementation.md",18879,"https:\u002F\u002Fgithub.com\u002Fbarkleesanders\u002Fclaude-code-starter\u002Fblob\u002Fmain\u002Fskills\u002Fdesign\u002Freferences\u002Fcode-implementation.md",{"path":62,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":63,"sourceHtmlUrl":64},"references\u002Fstitch-workflows.md",6979,"https:\u002F\u002Fgithub.com\u002Fbarkleesanders\u002Fclaude-code-starter\u002Fblob\u002Fmain\u002Fskills\u002Fdesign\u002Freferences\u002Fstitch-workflows.md",[66,72,79,86,93,100],{"skillNo":67,"name":68,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":69,"categories":70,"keywords":71,"publishedAt":19},"01M7AWV75B37B6YKG7ZKGZ783F","zi-search","https:\u002F\u002Fgithub.com\u002Fbarkleesanders\u002Fclaude-code-starter\u002Fblob\u002Fmain\u002Fskills\u002Fzi-search\u002FSKILL.md",[],[],{"skillNo":73,"name":74,"nameZh":6,"description":75,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":76,"categories":77,"keywords":78,"publishedAt":19},"01M7AWTZA3JGK1T7V1HS543FG7","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\u002Finteractive 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.","https:\u002F\u002Fgithub.com\u002Fbarkleesanders\u002Fclaude-code-starter\u002Fblob\u002Fmain\u002Fskills\u002Fvisualise\u002FSKILL.md",[],[],{"skillNo":80,"name":81,"nameZh":6,"description":82,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":83,"categories":84,"keywords":85,"publishedAt":19},"01M7AWTR056C3P9R3VS8YVM2WX","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.","https:\u002F\u002Fgithub.com\u002Fbarkleesanders\u002Fclaude-code-starter\u002Fblob\u002Fmain\u002Fskills\u002Fvideo\u002FSKILL.md",[],[],{"skillNo":87,"name":88,"nameZh":6,"description":89,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":90,"categories":91,"keywords":92,"publishedAt":19},"01M7AWTHTWBMTYZPMHHEYX3TTG","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\u002Fmathematical content.","https:\u002F\u002Fgithub.com\u002Fbarkleesanders\u002Fclaude-code-starter\u002Fblob\u002Fmain\u002Fskills\u002Fvideo-use\u002Fskills\u002Fmanim-video\u002FSKILL.md",[],[],{"skillNo":94,"name":95,"nameZh":6,"description":96,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":97,"categories":98,"keywords":99,"publishedAt":19},"01M7AWTCXDJ9NWFQW51ENM8A2Z","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.","https:\u002F\u002Fgithub.com\u002Fbarkleesanders\u002Fclaude-code-starter\u002Fblob\u002Fmain\u002Fskills\u002Fvideo-use\u002FSKILL.md",[],[],{"skillNo":101,"name":102,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":103,"categories":104,"keywords":105,"publishedAt":19},"01M7AWTA1D5FP895S33GHSA2G5","ui-improver","https:\u002F\u002Fgithub.com\u002Fbarkleesanders\u002Fclaude-code-starter\u002Fblob\u002Fmain\u002Fskills\u002Fui-improver\u002FSKILL.md",[],[]]