monomind 2.7.12 → 2.7.14

package/packages/@monomind/cli/.claude/skills/monodesign/reference/audit.native.md

@@ -1,139 +0,0 @@
-Run systematic **technical** quality checks on a native app (`ios` / `android` / `adaptive`) and generate a comprehensive report. Don't fix issues; document them for other commands to address.
-
-This is a code-level audit, not a design critique. Audit from source (SwiftUI / UIKit / Compose / React Native / Flutter); no browser tooling or `detect.mjs` applies. Score against the platform reference(s): [ios.md](ios.md) / [android.md](android.md), both for `adaptive`. Read them before scoring if Setup hasn't already. The report skeleton mirrors [audit.md](audit.md); keep the two in sync when changing it.
-
-## Diagnostic Scan
-
-Run comprehensive checks across 5 dimensions. Score each dimension 0-4 using the criteria below.
-
-### 1. Accessibility (VoiceOver / TalkBack)
-
-**Check for**:
-- **Missing labels**: interactive elements without accessibility labels, traits/roles, or state announcements
-- **Reading and focus order**: illogical traversal, unreachable controls, focus lost on navigation
-- **Text scaling**: fixed point sizes defeating Dynamic Type (iOS) or px instead of sp (Android); layouts that clip or overlap at large sizes
-- **Touch targets**: below 44 pt (iOS) / 48 dp (Android), or crammed without spacing
-- **Reduce Motion ignored**: parallax and large slides with no crossfade alternative
-- **Contrast**: text failing contrast in either appearance, light or dark
-
-**Score 0-4**: 0=Screen reader unusable, 1=Major gaps (unlabeled controls, no scaling), 2=Partial (labels exist, order or scaling breaks), 3=Good (minor gaps), 4=Excellent (labeled, ordered, scales cleanly, Reduce Motion honored)
-
-### 2. Performance
-
-**Check for**:
-- **Slow startup**: heavy work on launch before first frame
-- **Unvirtualized lists**: long content without FlatList / LazyColumn / List recycling
-- **Main-thread jank**: synchronous work in scroll or gesture paths, dropped frames on 60/120 Hz
-- **Wasted rendering**: unnecessary re-renders (React Native) or recompositions (Compose); missing memoization/keys
-- **Image handling**: full-size images decoded for thumbnails, no caching
-- **App weight**: bloated JS bundle or binary, unused dependencies
-
-**Score 0-4**: 0=Janky everywhere, 1=Major problems (unvirtualized lists, slow launch), 2=Partial, 3=Good (minor improvements possible), 4=Excellent (fast launch, smooth scroll, lean)
-
-### 3. Appearance & Theming
-
-**Check for**:
-- **Hard-coded colors**: raw hex instead of semantic system colors (iOS) / Material color roles (Android) / design tokens
-- **Broken dark appearance**: missing dark variants, poor contrast in dark, quick inverts
-- **Dynamic Color** (Android 12+): no static fallback scheme, or ignored where it fits
-- **Off-platform materials**: hand-rolled blur/glassmorphism instead of system materials or tonal elevation
-
-**Score 0-4**: 0=Hard-coded everything, 1=Minimal tokens, 2=Partial (tokens exist, inconsistently used), 3=Good (minor hard-coded values), 4=Excellent (semantic throughout, both appearances first-class)
-
-### 4. Platform Conformance (CRITICAL)
-
-Score against the loaded platform reference(s), including their slop tests. **Check for**:
-- **Broken system gestures**: edge-swipe back disabled (iOS), predictive Back hijacked (Android)
-- **Inset violations**: content under the notch, Dynamic Island, home indicator, status bar, or keyboard
-- **Off-platform navigation**: custom global nav, overloaded tab bars, iOS patterns on Android or vice versa
-- **Web-shaped controls**: HTML-style buttons, custom toggles, hover-dependent affordances
-- **Icon drift**: mixed icon sets instead of SF Symbols / Material Symbols
-- **AI tells**: the shared absolute bans still apply (AI palette, gradient text, hero metrics)
-
-**Score 0-4**: 0=Web port (nothing native), 1=Heavy violations (3-4 kinds), 2=Some (1-2 noticeable), 3=Mostly conformant (subtle issues), 4=Fully native (a fluent user trusts every screen)
-
-### 5. Adaptivity
-
-**Check for**:
-- **Stretched phone layouts**: tablet/iPad rendering a scaled-up phone UI instead of using size classes / window size classes
-- **Orientation breakage**: landscape clipping, ignored, or locked without reason
-- **Keyboard/IME handling**: inputs hidden behind the keyboard, no inset adjustment
-- **Multitasking**: iPad Split View / Android multi-window breaking layout
-- **Foldables**: hinge-unaware layouts on posture change (Android)
-
-**Score 0-4**: 0=One screen size only, 1=Major breakage (landscape or tablet broken), 2=Partial, 3=Good (minor edge cases), 4=Excellent (adapts across sizes, orientations, and windowing)
-
-## Generate Report
-
-### Audit Health Score
-
-| # | Dimension | Score | Key Finding |
-|---|-----------|-------|-------------|
-| 1 | Accessibility | ? | [most critical issue or "--"] |
-| 2 | Performance | ? | |
-| 3 | Appearance & Theming | ? | |
-| 4 | Platform Conformance | ? | |
-| 5 | Adaptivity | ? | |
-| **Total** | | **??/20** | **[Rating band]** |
-
-**Rating bands**: 18-20 Excellent (minor polish), 14-17 Good (address weak dimensions), 10-13 Acceptable (significant work needed), 6-9 Poor (major overhaul), 0-5 Critical (fundamental issues)
-
-### Platform Conformance Verdict
-**Start here.** Pass/fail: does this read as a native app or a ported website? List specific violations. Be brutally honest.
-
-### Executive Summary
-- Audit Health Score: **??/20** ([rating band])
-- Total issues found (count by severity: P0/P1/P2/P3)
-- Top 3-5 critical issues
-- Recommended next steps
-
-### Detailed Findings by Severity
-
-Tag every issue with **P0-P3 severity**:
-- **P0 Blocking**: Prevents task completion. Fix immediately
-- **P1 Major**: Significant difficulty or platform-guideline violation. Fix before release
-- **P2 Minor**: Annoyance, workaround exists. Fix in next pass
-- **P3 Polish**: Nice-to-fix, no real user impact. Fix if time permits
-
-For each issue, document:
-- **[P?] Issue name**
-- **Location**: Screen, file, line
-- **Category**: Accessibility / Performance / Theming / Conformance / Adaptivity
-- **Impact**: How it affects users
-- **Guideline**: The HIG / Material rule it violates (if applicable)
-- **Recommendation**: How to fix it
-- **Suggested command**: Which command to use (prefer: /monodesign craft, /monodesign init, /monodesign document, /monodesign extract, /monodesign live, /monodesign adapt, /monodesign animate, /monodesign audit, /monodesign bolder, /monodesign clarify, /monodesign colorize, /monodesign critique, /monodesign delight, /monodesign distill, /monodesign harden, /monodesign onboard, /monodesign layout, /monodesign optimize, /monodesign overdrive, /monodesign polish, /monodesign quieter, /monodesign shape, /monodesign typeset)
-
-### Patterns & Systemic Issues
-
-Identify recurring problems that indicate systemic gaps rather than one-off mistakes:
-- "Hard-coded colors appear in 15+ screens, should use semantic colors"
-- "Touch targets consistently below 44 pt throughout the tab bar and list rows"
-
-### Positive Findings
-
-Note what's working well: good practices to maintain and replicate.
-
-## Recommended Actions
-
-List recommended commands in priority order (P0 first, then P1, then P2):
-
-1. **[P?] `/command-name`**: Brief description (specific context from audit findings)
-2. **[P?] `/command-name`**: Brief description (specific context)
-
-**Rules**: Only recommend commands from: /monodesign craft, /monodesign init, /monodesign document, /monodesign extract, /monodesign live, /monodesign adapt, /monodesign animate, /monodesign audit, /monodesign bolder, /monodesign clarify, /monodesign colorize, /monodesign critique, /monodesign delight, /monodesign distill, /monodesign harden, /monodesign onboard, /monodesign layout, /monodesign optimize, /monodesign overdrive, /monodesign polish, /monodesign quieter, /monodesign shape, /monodesign typeset. Map findings to the most appropriate command. End with `/monodesign polish` as the final step if any fixes were recommended.
-
-After presenting the summary, tell the user:
-
-> You can ask me to run these one at a time, all at once, or in any order you prefer.
->
-> Re-run `/monodesign audit` after fixes to see your score improve.
-
-**IMPORTANT**: Be thorough but actionable. Too many P3 issues creates noise. Focus on what actually matters.
-
-**NEVER**:
-- Report issues without explaining impact (why does this matter?)
-- Provide generic recommendations (be specific and actionable)
-- Skip positive findings (celebrate what works)
-- Forget to prioritize (everything can't be P0)
-- Report false positives without verification

package/packages/@monomind/cli/.claude/skills/monodesign/reference/bolder.md

@@ -1,120 +0,0 @@
-When asked for "bolder," AI defaults to the same tired tricks: cyan/purple gradients, glassmorphism, neon accents on dark backgrounds, gradient text on metrics. These are the opposite of bold. Reject them first, then increase visual impact by making the existing design language more decisive, specific, and committed.
-
----
-
-## Register
-
-Brand: "bolder" means distinctive. Express a stronger point of view through hierarchy, pacing, proportion, copy, evidence, and one committed visual idea.
-
-Product: "bolder" rarely means theatrics; those undermine trust. It means stronger hierarchy, clearer weight contrast, sharper information density, and more decisive prioritization. The amplification is in clarity, not drama.
-
----
-
-## Assess Current State
-
-Analyze what makes the design feel too safe or boring:
-
-1. **Identify weakness sources**:
-   - **Generic choices**: The page could belong to any product in the category.
-   - **Timid scale**: Everything is medium-sized with no clear lead.
-   - **Low contrast**: Important and supporting elements have similar visual weight.
-   - **Static**: The surface has no meaningful moment of emphasis.
-   - **Predictable**: The composition follows a default pattern without a point of view.
-   - **Flat hierarchy**: Nothing stands out or commands attention.
-
-2. **Understand the context**:
-   - What is the brand personality?
-   - What is the purpose of this surface?
-   - Who is the audience?
-   - What design system, tokens, components, and visual conventions already exist?
-
-If any of these are unclear from the codebase, STOP and call the AskUserQuestion tool to clarify.
-
-**CRITICAL**: "Bolder" does not mean chaotic or garish. It means distinctive, memorable, and confident. Think intentional drama, not random noise.
-
-**WARNING - AI SLOP TRAP**: Review ALL the DON'T guidelines from the parent monodesign skill (already loaded in this context) before proceeding. Bold means distinctive, not "more effects."
-
-## Design-System Lock
-
-If the project has `DESIGN.md`, tokens, theme variables, or established component styles, treat that system as the boundary. Make the existing language stronger before adding new language.
-
-Do not invent new colors, gradients, radii, shadows, fonts, decorative backgrounds, or effects just because the request says "bolder." A bolder pass should usually change emphasis, proportion, rhythm, density, contrast, copy, artifact specificity, and layout relationships while staying inside the documented system.
-
-If the existing system is genuinely too limited to express the bolder direction, stop and ask the user before expanding it. Name the exact additions, the role each would play, and why the current system cannot do the job. If the user approves expansion, update the design system or tokens alongside the implementation.
-
-## Plan Amplification
-
-Create a strategy to increase impact while maintaining coherence:
-
-- **Focal point**: Pick one thing the viewer should remember, then make the rest support it.
-- **System levers**: Identify which existing tokens, components, layout patterns, and copy structures can carry more weight.
-- **Risk budget**: Decide how far the surface can push while still feeling like the same product or brand.
-- **Hierarchy amplification**: Increase contrast between primary, secondary, and tertiary content instead of making every element louder.
-
-**IMPORTANT**: Bold design must still be usable. Impact without function is just decoration.
-
-## Amplify the Design
-
-Systematically increase impact through intention, not a menu of effects:
-
-### Typography Amplification
-- Strengthen the existing type hierarchy before changing typefaces.
-- Make important text meaningfully more dominant, and make supporting text quieter.
-- Use weight, measure, spacing, and line breaks to sharpen the point of view.
-- Add or replace fonts only after user-approved design-system expansion.
-
-### Color Amplification
-- Use the existing palette more decisively before adding colors.
-- Shift the proportion, placement, and contrast of documented colors to clarify meaning.
-- Treat any new color, gradient, or tint ramp as a design-system expansion that requires user approval.
-- Keep color tied to hierarchy, state, or brand meaning; do not use it as surface decoration.
-
-### Spatial Amplification
-- Change proportion, density, alignment, and sequencing so the composition has a stronger point of view.
-- Create clearer contrast between dense evidence and open breathing room.
-- Let layout express priority and narrative order before adding ornament.
-- Preserve responsive behavior and avoid text overflow at every breakpoint.
-
-### Surface Amplification
-- Use existing surface, border, radius, and shadow rules more deliberately.
-- Remove timid half-measures: either give an element a clear role or simplify it.
-- Add texture, depth, illustration, or decorative treatments only when already established by the system or explicitly approved.
-- Make real product artifacts, imagery, data, or copy carry attention before reaching for effects.
-
-### Motion & Animation
-- Design one meaningful moment of emphasis when motion genuinely supports the point.
-- Make interaction feedback feel more decisive without becoming distracting.
-- Keep transitions smooth and intentional.
-- **Bolder != scroll-fade-rise on every section.** That's the saturated AI default, the opposite of bold.
-
-### Composition Boldness
-- Make the dominant idea unmistakable.
-- Use layout tension, sequencing, contrast, and restraint to create a stronger read.
-- Let the page's structure communicate priority before adding decorative layers.
-- If every element is louder, the composition is not bolder; it is flatter.
-
-**NEVER**:
-- Add undocumented design-system primitives without user approval
-- Add effects randomly without purpose
-- Hide weak hierarchy behind decoration
-- Sacrifice readability for aesthetics
-- Make everything bold; contrast is the point
-- Ignore accessibility
-- Overwhelm with motion
-- Copy trendy aesthetics blindly
-
-## Verify Quality
-
-Ensure amplification maintains usability and coherence:
-
-- **System-faithful**: Did the pass make the existing design language stronger before adding anything new?
-- **No undocumented drift**: Are new colors, gradients, shadows, radii, fonts, and effects either absent or explicitly approved and documented?
-- **NOT AI slop**: Does this look like every other AI-generated "bold" design? If yes, start over.
-- **Still functional**: Can users accomplish tasks without distraction?
-- **Coherent**: Does everything feel intentional and unified?
-- **Memorable**: Will users remember this experience for the intended reason?
-- **Performant and accessible**: Does the result stay fast, readable, responsive, and WCAG-conscious?
-
-**The test**: If you showed this to someone and said "AI made this bolder," would they believe you immediately? If yes, you've failed. Bold means distinctive, not "more AI effects."
-
-When the result feels right, hand off to `/monodesign polish` for the final pass.

package/packages/@monomind/cli/.claude/skills/monodesign/reference/brand-workflow.md

@@ -1,180 +0,0 @@
-# Brand Workflow
-
-How to define, document, and operationalize brand identity for a project. Use when the task involves brand identity work, visual identity guidelines, or establishing a brand-consistent design system from scratch.
-
----
-
-## The Brand Hierarchy
-
-```
-brand-guidelines.md          ← Source of truth (human-readable)
-       ↓
-design-tokens (primitives)   ← Derived color/type values
-       ↓
-semantic tokens              ← Purpose assignments
-       ↓
-component tokens             ← Implementation
-       ↓
-all UI surfaces              ← Consistent brand expression
-```
-
-**The principle:** Every design decision in code should trace back to the brand guidelines. When the guidelines change, only the tokens change — not the components.
-
----
-
-## Step 1: Define Brand Guidelines
-
-Create `BRAND.md` (or `docs/brand-guidelines.md`) as the project's source of truth. Sections to cover:
-
-### Brand Positioning
-- The one sentence that describes what this product is and who it's for
-- Personality: 3 adjectives that describe the brand's character
-- Register: editorial, functional, playful, authoritative, intimate, aspirational?
-
-### Visual Identity
-
-**Color palette** — use OKLCH for all values per the OKLCH-Only Rule:
-```
-Primary (1 color)
-  └── The one vibrant accent (One Voice Rule — no second accent)
-
-Neutrals (3–4 values)
-  ├── Page background (warm, never pure white)
-  ├── Primary text
-  ├── Secondary text
-  └── Borders / dividers
-
-Feedback (system colors)
-  ├── Error
-  ├── Success
-  └── Warning
-```
-
-**Typography**
-```
-Display / Headline  — the editorial voice (personality font)
-Body                — the readable voice (text font)
-Mono                — code / technical content
-
-Rules:
-- line-height: 1.6 for body (non-negotiable)
-- Headings use clamp() fluid sizing
-- Body uses fixed rem
-```
-
-**Shape language**
-- Default border-radius: 0 (sharp/editorial) or N px (softer/friendly)?
-- Is this a brand-register (sharp) or product-register (rounded) surface?
-- Shadow depth: flat-by-default or consistently elevated?
-
-**Motion**
-- Default easing: `cubic-bezier(0.16, 1, 0.3, 1)` (expo-out) for all transitions
-- Duration: 150ms (micro) / 250ms (standard) / 400ms (complex)
-- Always respect `prefers-reduced-motion`
-
-### Brand Voice
-- Tone: formal / conversational / technical / warm?
-- Copy rules: short/punchy vs detailed/thorough? Active/imperative? First/second/third person?
-- What to avoid: jargon? Hedging? Superlatives?
-
----
-
-## Step 2: Derive Token Primitives from Brand
-
-Translate brand guidelines → primitive token values. See `token-architecture.md` for the full three-layer system.
-
-For the **color palette**, verify every token value with the OKLCH color space:
-1. Convert brand colors to OKLCH (tool: oklch.com)
-2. Verify the accent-to-background chroma relationship (warm backgrounds harmonize with warm-hue accents)
-3. Check WCAG contrast: text tokens must pass 4.5:1 against surface tokens
-4. Build the tonal ramp (8 steps from darkest to lightest) for the primary accent
-
-For **typography**, document:
-- Font families and their CDN/license source
-- Exact weight and size values for each type style (see design-principles.md Reference Typography System)
-
----
-
-## Step 3: Sync Brand to Code
-
-Maintain a single-direction sync flow:
-
-```
-BRAND.md  ──(manual review)──→  tokens/primitives.css
-                                 tokens/semantic.css
-                                 tokens/components.css
-```
-
-The sync is intentionally manual for the primitive and semantic layers — these changes are load-bearing and should be reviewed, not automated. Component tokens can be generated.
-
-**Validation checks after any brand update:**
-1. Run WCAG contrast check on all text/surface token pairs
-2. Check all OKLCH values still use OKLCH (not hex/hsl)
-3. Verify there is still exactly one vibrant accent (One Voice Rule)
-4. Verify page background is warm, not pure white (Paper-Not-White Rule)
-
----
-
-## Step 4: Brand Consistency Audit
-
-When auditing an existing product for brand consistency, check:
-
-### Visual consistency
-- [ ] All colors trace to the brand token system — no orphaned hex values in components
-- [ ] Typography scale and weights match the brand spec
-- [ ] Border-radius is consistent with the brand's shape language
-- [ ] The accent color appears on ≤10% of any given screen
-- [ ] No second accent color has crept in
-
-### Voice consistency
-- [ ] Copy tone matches the brand voice guidelines
-- [ ] No hedging language ("we think", "maybe", "might be useful")
-- [ ] CTAs are imperative and clear
-- [ ] Error messages are direct, not apologetic
-
-### Motion consistency
-- [ ] All transitions use the brand easing token (`--ease-out`)
-- [ ] Duration values are from the brand scale (fast/base/slow)
-- [ ] No bounce or elastic easing anywhere
-
----
-
-## Visual Identity Quick Reference
-
-### Logo Usage
-- Use the correct variant for context (primary vs. compact vs. icon-only)
-- Maintain minimum clear space around all logo variants
-- Never stretch, distort, recolor, or add effects
-- Never place on a busy background without a scrim
-
-### Color Usage Ratios (rule of thumb)
-- 60% neutral/background surfaces
-- 30% secondary/supporting tones
-- 10% accent (the one vibrant color)
-
-### Icon System
-- One icon family across the entire product
-- Consistent stroke weight and corner radius
-- Filled vs outline: pick one style per hierarchy level — don't mix
-- All icons have `aria-label` or accompanying visible text
-
-### Photography / Illustration
-- Define the lighting and mood palette (warm / cool / neutral)
-- Establish subject guidelines (people-focused? abstract? product?)
-- Consistent editing style (desaturated / vibrant / duotone?)
-
----
-
-## Brand Register Decision
-
-Before any design session, confirm the **register** of the surface you're designing:
-
-| Register | Characteristics | Shape language | Motion |
-|---|---|---|---|
-| Brand / marketing | Expressive, editorial, emotional | Sharp edges, strong hierarchy | Cinematic, scroll-driven |
-| Product / functional | Efficient, clear, reliable | Slight radius ok, systematic | Micro-interactions, functional |
-| Data / dense | Precise, neutral, information-first | Compact, tabular | Minimal, purposeful |
-
-The register determines which rules are in effect. Italic serif display type is appropriate on a brand surface; embarrassing on a product surface. Glassmorphism on a product surface is decorative noise; on a landing page it can be intentional.
-
-Cross-register failures (product surfaces with brand-surface decoration, or marketing pages with dense product UI) are among the most common and most damaging design mistakes.

package/packages/@monomind/cli/.claude/skills/monodesign/reference/brand.md

@@ -1,108 +0,0 @@
-# Brand register
-
-When design IS the product: brand sites, landing pages, marketing surfaces, campaign pages, portfolios, long-form content, about pages. The deliverable is the design itself; a visitor's impression is the thing being made.
-
-The register spans every genre. A tech brand (Stripe, Linear, Vercel). A luxury brand (a hotel, a fashion house). A consumer product (a restaurant, a travel site, a CPG packaging page). A creative studio, an agency portfolio, a band's album page. They all share the stance (*communicate, not transact*) and diverge wildly in aesthetic. Don't collapse them into a single look.
-
-## The brand slop test
-
-If someone could look at this and say "AI made that" without hesitation, it's failed. The bar is distinctiveness; a visitor should ask "how was this made?", not "which AI made this?"
-
-Brand isn't a neutral register. AI-generated landing pages have flooded the internet, and average is no longer findable. Restraint without intent now reads as mediocre, not refined. Brand surfaces need a POV, a specific audience, a willingness to risk strangeness. Go big or go home.
-
-**The second slop test: aesthetic lane.** Before committing to moves, name the reference. A Klim-style specimen page is one lane; Stripe-minimal is another; Liquid-Death-acid-maximalism is another. Don't drift into editorial-magazine aesthetics on a brief that isn't editorial. A hiking brand with Cormorant italic drop caps has the wrong register within the register.
-
-Then the inverse test: in one sentence, describe what you're about to build the way a competitor would describe theirs. If that sentence fits the modal landing page in the category, restart.
-
-## Typography
-
-### Font selection procedure
-
-Every project. Never skip.
-
-1. Read the brief. Write three concrete brand-voice words. Not "modern" or "elegant," but "warm and mechanical and opinionated" or "calm and clinical and careful." Physical-object words.
-2. List the three fonts you'd reach for by reflex. If any appear in the reflex-reject list below, reject them; they are training-data defaults and they create monoculture.
-3. Browse a real catalog (Google Fonts, Pangram Pangram, Future Fonts, Adobe Fonts, ABC Dinamo, Klim, Velvetyne) with the three words in mind. Find the font for the brand as a *physical object*: a museum caption, a 1970s terminal manual, a fabric label, a cheap-newsprint children's book, a concert poster, a receipt from a mid-century diner. Reject the first thing that "looks designy."
-4. Cross-check. "Elegant" is not necessarily serif. "Technical" is not necessarily sans. "Warm" is not Fraunces. If the final pick lines up with the original reflex, start over.
-
-### Reflex-reject list
-
-Training-data defaults. Ban list. Look further:
-
-Fraunces · Newsreader · Lora · Crimson · Crimson Pro · Crimson Text · Playfair Display · Cormorant · Cormorant Garamond · Syne · IBM Plex Mono · IBM Plex Sans · IBM Plex Serif · Space Mono · Space Grotesk · Inter · DM Sans · DM Serif Display · DM Serif Text · Outfit · Plus Jakarta Sans · Instrument Sans · Instrument Serif
-
-### Reflex-reject aesthetic lanes
-
-Parallel to the font list. Currently saturated aesthetic families that have flooded brand surfaces. If a brief lands in one of these lanes without a register reason that *requires* it (a literal magazine, a literal terminal, a literal industrial signage system), it's the second-order training reflex: the trap one tier deeper than picking a Fraunces font. Look further.
-
-- **Editorial-typographic.** Display serif (often italic) + small mono labels + ruled separators + monochromatic restraint. Klim-influenced, magazine-cover affectation. By 2026, every Stripe-adjacent and Notion-adjacent brand has landed here. The fingerprint: three rule-separated columns, an italic Fraunces / Recoleta / Newsreader headline, lowercase track-spaced metadata, no imagery.
-
-(More entries land here on the same cadence the font list updates. Brutalist-utility and acid-maximalism may join when they saturate. Removing entries when they fall back below saturation is also fine.)
-
-The reflex-reject lists apply to **new design choices**. When the existing brand has already committed to a font or a lane as part of its identity, identity-preservation wins; variants on an existing surface don't second-guess what's already shipping. The reflex-reject lists are for greenfield decisions and for departure-mode variants in [live.md](live.md).
-
-### Pairing and voice
-
-Distinctive + refined is the goal. The specific shape depends on the brand, not on the brand's category. A category ("restaurant", "dev tool", "magazine", "fintech") is not a recipe; treating it as one is the first-order reflex SKILL.md warns against.
-
-Two families minimum is the rule *only* when the voice needs it. A single well-chosen family with committed weight/size contrast is stronger than a timid display+body pair.
-
-### Scale
-
-Modular scale, fluid `clamp()` for headings, ≥1.25 ratio between steps. Flat scales (1.1× apart) read as uncommitted.
-
-Light text on dark backgrounds: add 0.05–0.1 to line-height. Light type reads as lighter weight and needs more breathing room.
-
-## Color
-
-Brand surfaces have permission for Committed, Full palette, and Drenched strategies. Use them. A single saturated color spread across a hero is not excess; it's voice. A beige-and-muted-slate landing page ignores the register.
-
-- Name a real reference before picking a strategy. "Klim Type Foundry #ff4500 orange drench", "Stripe purple-on-white restraint", "Liquid Death acid-green full palette", "Mailchimp yellow full palette", "Condé Nast Traveler muted navy restraint", "Vercel pure black monochrome". Unnamed ambition becomes beige.
-- Palette IS voice. A calm brand and a restless brand should not share palette mechanics.
-- When the strategy is Committed or Drenched, color carries the brand. Don't hedge with neutrals around the edges. Commit.
-- Don't converge across projects. Each brand surface differentiates from the last.
-- When a cultural-symbol palette is the obvious pull, reach past it. Let the cultural reading come from typography, imagery, and copy, not the palette.
-
-## Layout
-
-- Asymmetric compositions are one option. Break the grid intentionally for emphasis.
-- Fluid spacing with `clamp()` that breathes on larger viewports. Vary for rhythm: generous separations, tight groupings.
-- For image-led briefs (hotels, restaurants, magazines, photography), full-bleed hero imagery with overlaid menu and centered headline is a canonical move; let the photograph be the design.
-- When cards ARE the right affordance, use `grid-template-columns: repeat(auto-fit, minmax(280px, 1fr))` for breakpoint-free responsiveness.
-
-## Imagery
-
-Brand surfaces lean on imagery. A restaurant, hotel, magazine, or product landing page without any imagery reads as incomplete, not as restrained. A solid-color rectangle where a hero image should go is worse than a representative stock photo.
-
-**When the brief implies imagery, you must ship imagery.** Zero images is a bug, not a design choice. "Restraint" is not an excuse. If the approved comp or brief is image-led, ship real project assets, generated raster assets, or a credible canvas/SVG/WebGL scene. Do not replace photographic, architectural, product, or place imagery with generic CSS panels, decorative diagrams, cards, bullets, or copy.
-
-- **For greenfield work without local assets, use stock imagery.** Unsplash is the default. The URL shape is `https://images.unsplash.com/photo-{id}?auto=format&fit=crop&w=1600&q=80`. **Verify the URLs before referencing them.** If you have an image-search MCP, web-fetch tool, or browser access, use it to find real photo IDs and confirm they resolve. Guessed IDs (even ones that look real) often 404 and ship as broken-image placeholders. Without a verification path, pick fewer photos you're confident exist over more that you guessed; never substitute colored `<div>` placeholders.
-- **Search for the brand's physical object**, not the generic category: "handmade pasta on a scratched wooden table" beats "Italian food"; "cypress trees above a limestone hotel facade at dusk" beats "luxury hotel".
-- **One decisive photo beats five mediocre ones.** Hero imagery should commit to a mood; padding with more stock doesn't rescue an indecisive one.
-- **Alt text is part of the voice.** "Coastal fettuccine, hand-cut, served on the terrace" beats "pasta dish".
-
-"Imagery" here is broader than stock photography: product screenshots, custom data visualizations, generated SVG, and canvas/WebGL scenes are all imagery. Text-only pages where typography alone carries the entire visual weight are the failure mode.
-
-## Motion
-
-- One well-orchestrated page-load beats scattered micro-interactions, when the brand invites it. Some brands skip entrance motion entirely; the restraint is the voice.
-
-## Brand bans (on top of the shared absolute bans)
-
-- Monospace as lazy shorthand for "technical / developer." If the brand isn't technical, mono reads as costume.
-- Large rounded-corner icons above every heading. Screams template.
-- Single-family pages that picked the family by reflex, not voice. (A single family chosen deliberately is fine.)
-- All-caps body copy. Reserve caps for short labels and headings.
-- Timid palettes and average layouts. Safe = invisible.
-- Zero imagery on a brief that implies imagery (restaurant, hotel, food, travel, fashion, photography, hobbyist). Colored blocks where a hero photo belongs.
-- Defaulting to editorial-magazine aesthetics (display serif + italic + drop caps + broadsheet grid) on briefs that aren't magazine-shaped. Editorial is ONE aesthetic lane, not the default brand aesthetic.
-- Repeated tiny uppercase tracked labels above every section heading. A single strong kicker can be voice; repeating it as section grammar is AI scaffolding unless it's a deliberate, named brand system.
-
-## Brand permissions
-
-Brand can afford things product can't. Take them.
-
-- Ambitious first-load motion. Reveals and typographic choreography that earn their place; not fade-on-scroll for every section.
-- Single-purpose viewports. One dominant idea per fold, long scroll, deliberate pacing.
-- Unexpected color strategies. Palette IS voice; a calm brand and a restless brand should not share palette mechanics.
-- Art direction per section. Different sections can have different visual worlds if the narrative demands it. Consistency of voice beats consistency of treatment.