{ "schemaVersion": 3, "engineVersion": "4.0.0", "generatedFrom": [ "PRODUCT-PRINCIPLES.md", "CRAFT-BASELINE.md", "RULESETS.md", "ADAPTERS.md", "APP-PLAYBOOKS.md", "PAGE-TYPES.md", "BRAND-RECIPES.md", "PALETTE-RECIPES.md", "color/palettes.json", "PRESETS.md" ], "core": "# StyleSeed Product Constitution\n\nStyleSeed is an **AI design-method engine**. Its primary job is to make a coding agent\nreason like a strong UI/UX designer and apply that reasoning consistently. Components,\nskins, scores, and screenshots support that job; they do not define it.\n\n## The fixed method, not one fixed look\n\nStyleSeed enforces a stable way of judging design. It does **not** force every product to\nlook like Toss, a SaaS dashboard, or the StyleSeed demo. A trustworthy consumer-finance\nhome, an observability console, an editorial story, and a product-detail page solve\ndifferent jobs and therefore need different design grammars.\n\nThe effective rule set is composed:\n\n```text\nCore judgment\n × one output grammar from RULESETS.md (built-in or reference-compiled)\n × one surface adapter from ADAPTERS.md\n × one domain playbook from APP-PLAYBOOKS.md\n × one page type from PAGE-TYPES.md\n × one brand recipe from BRAND-RECIPES.md\n × one semantic palette posture plus an optional key-color generation from PALETTE-RECIPES.md\n × optional aesthetic profile from PRESETS.md\n × bounded project tokens from STYLESEED.md\n= the rules for this screen\n```\n\n## Authority order\n\nWhen instructions disagree, use this order:\n\n1. **Core invariants** below.\n2. **Output grammar** — the functional visual language selected in `RULESETS.md`, or a\n project-local grammar compiled by `REFERENCE-COMPILER.md`.\n3. **Surface adapter** — the renderer contract and physical constraints in `ADAPTERS.md`.\n4. **Domain playbook** and **page/artifact type**.\n5. **Brand recipe** — a reusable morphology and component-selection contract from\n `BRAND-RECIPES.md`.\n6. **Palette system** — a maintained semantic posture plus deterministic key-color generation,\n role mapping, gamut handling, and contrast correction from `PALETTE-RECIPES.md`.\n7. **Aesthetic profile** — an optional coordinated restyle from `PRESETS.md`.\n8. **Design lock** — records selections and bounded project parameters.\n9. **Skins and components** — implementation material, not sources of judgment.\n10. **Score and visual verification** — evidence that the method was applied.\n\n`STYLESEED.md` is persistence, not permission. An arbitrary value in the lock never turns\na violation into a sound design decision. Unknown values fall back to the nearest maintained\ngrammar and the core defaults.\n\n## Core invariants\n\nThese apply to every grammar, profile, domain, page, skin, and agent:\n\n- One deliberate visual system per product: radius, spacing, elevation, icon language,\n typography, color roles, imagery, and motion agree.\n- One focal point per screen and a clear information hierarchy.\n- Color communicates role or meaning. One primary action remains identifiable even when\n semantic, categorical, or product colors are present.\n- Semantic tokens replace component-level hardcoded colors.\n- Spacing follows a repeatable scale; proximity communicates grouping.\n- Typography fits the surface and task, with readable measure, contrast, and hierarchy.\n- Data surfaces include useful loading, empty, and error states.\n- Controls remain operable: visible focus, sufficient targets, labels, reduced-motion\n support, and no dark patterns.\n- Motion fits the surface and never delays comprehension or action.\n- Distinctiveness comes from the product, its content, and its selected grammar — not a\n copied demo, generic indigo, repeated icon chips, emoji chrome, or template uniformity.\n\n## What the lock may select\n\nThe lock may select only inputs the engine understands:\n\n- domain, surface adapter, page/artifact type, and one output grammar;\n- one maintained brand recipe, one semantic palette posture, optional bounded key-color generation,\n one optional aesthetic profile, and one skin or project token implementation;\n- primary action/accent, type pairing, density, radius, elevation, imagery, and motion values\n inside the selected grammar's allowed ranges;\n- one product-specific signature move that still obeys the invariants;\n- a project-local reference grammar with provenance and confidence recorded by the compiler.\n\nThe lock may not invent a palette mode, waive accessibility, legalize mixed systems, or\noverride a core invariant. A reusable built-in grammar requires research, examples, and\nregression evaluation. A reference-derived grammar stays project-local until it meets that bar.\n\n## The product loop\n\n```text\nunderstand the job → choose or compile a grammar → lock bounded decisions\n→ build with judgment → score the implementation → visually verify rendered output\n→ present the result and evidence\n```\n\nThe build method is the product. Scoring and verification are auxiliary gates: they find\ndrift, but they never choose or rewrite the design philosophy after the fact.", "craft": "# StyleSeed Compact Craft Baseline\n\nThis is the small, task-independent craft layer used by the Context Compiler. It preserves\nthe highest-leverage rules without injecting the full design handbook into every agent turn.\nThe selected output grammar, adapter, domain, page type, brand recipe, profile, and project lock narrow these\ndefaults. `PRODUCT-PRINCIPLES.md` remains the higher authority.\n\n## Coherence\n\n- Choose one coordinated family for radius, elevation, borders, icon style, typography, motion,\n control heights, and interaction states. Encode each family as semantic tokens and reuse it.\n- A coherent system may contain multiple component shapes and colors, but every variation must\n have a repeated role. Local decoration is not a role.\n- Preserve strengths and already-set project decisions. Do not restyle unrelated surfaces while\n fixing one screen.\n\n## Hierarchy and composition\n\n- Give every screen one dominant user decision or reading promise. Supporting content must recede\n through scale, position, contrast, density, or disclosure—not random color.\n- Proximity communicates grouping: space around a group should normally be at least twice the\n space within it. Repeated sections need deliberate variation in height, density, or composition.\n- Use real product content and evidence. Placeholder dashboards, fake metrics, stock chat panels,\n and equal card walls make otherwise clean work look generic.\n- Keep prose near 50–75 characters per line. Let data surfaces use width, but bound any reading\n column inside them.\n\n## Spacing and type\n\n- Start from `{4, 8, 12, 16, 24, 32, 40, 48, 64, 80, 96}` and use off-scale values only for a\n documented optical correction.\n- Default body text to 16px on general surfaces. Dense desktop UI may use 13–14px for metadata,\n table chrome, timestamps, or identifiers; decisions and explanatory copy stay readable.\n- Use no more than two type families and one intentional weight ramp. Use tabular numerals for\n money, tables, timers, and comparable metrics.\n- Tighten leading as type grows: body about 1.5, headings 1.2–1.35, display 1.0–1.2.\n\n## Components and interaction\n\n- Use the lightest separation that works: whitespace, then tone, then hairline, then shadow.\n Do not combine a visible border and floating shadow without a functional reason.\n- Buttons, inputs, and selects in one context share a height. Touch surfaces provide at least\n 44px targets; pointer-first dense desktop controls may be smaller when still operable.\n- Labels remain visible. Errors name the problem and recovery and never rely on color alone.\n- Use one icon family, fill mode, and stroke family. Do not use emoji as application chrome.\n- Loading, empty, error, success, disabled, and permission states preserve layout and provide a\n useful next action where the surface owns data or mutation.\n\n## Color, accessibility, and motion\n\n- Use semantic tokens. Keep one identifiable primary action while allowing stable semantic,\n categorical, or brand roles required by the selected grammar.\n- Body text targets WCAG AA contrast; large text and meaningful graphics meet their applicable\n threshold. Focus is visible, controls have names, and keyboard order follows visual order.\n- Motion uses one duration/easing family, communicates state or sequence, and never delays the\n first read or an action. Provide a complete reduced-motion result.\n- Inspect the real render at the target viewport. Source review cannot certify optical balance,\n font loading, crop, responsive transformation, or visual states.", "grammars": { "consumer-service": "### `consumer-service`\n\n- **Job:** understand personal state without anxiety and take one useful next action.\n- **Attention:** one dominant balance, status, benefit, or briefing; secondary services recede.\n- **Composition:** short contextual heading → dominant summary → small set of next actions →\n progressive detail. Mobile-first, thumb-reachable, explicit bottom navigation where needed.\n- **Density/type:** comfortable to airy; friendly sans; large plain-language numbers; short copy.\n- **Color/surface:** calm neutral base, one brand action color, semantic colors only for real\n status. Soft grouped surfaces are common but a card is used only when it groups a decision.\n- **Feedback:** immediate, reassuring, reversible; money and health values do not animate\n theatrically.\n- **Reject:** every service as equal card, promotional clutter above state, rainbow categories,\n cute language in serious moments, or copying Toss component-for-component.", "operations-console": "### `operations-console`\n\n- **Job:** scan system or business state, compare changes, find exceptions, act efficiently.\n- **Attention:** one operational focal panel; supporting KPIs form hierarchy rather than a\n uniform card wall.\n- **Composition:** persistent navigation → scope/time controls → focal trend or queue →\n comparable metrics → actionable table/list. Detail lives below or on demand.\n- **Density/type:** comfortable to compact; neutral grotesk; tabular numerals; labels may be\n small but body and decisions remain readable on desktop.\n- **Color/surface:** restrained brand accent; categorical colors only for stable, repeated data\n semantics. Tone, alignment, and grouping carry more hierarchy than decoration.\n- **Feedback:** filters and mutations respond instantly; loading preserves layout; bulk action\n consequences are explicit.\n- **Reject:** same-weight KPI tiles everywhere, decorative gradients, mobile-tight type on a\n 1440px canvas, or charts without a decision they support.", "technical-instrument": "### `technical-instrument`\n\n- **Job:** observe live state, isolate anomalies, and diagnose a system.\n- **Attention:** current incident, trace, monitor, or performance state dominates.\n- **Composition:** stable navigation and scope → live status/timeline → dense evidence table or\n trace → drill-down. Group by diagnostic relationship, not visual symmetry.\n- **Density/type:** compact to dense; sans for UI, mono only for identifiers, timestamps, code,\n and aligned numeric evidence.\n- **Color/surface:** neutral light or dark tonal ramp; one signal accent; status colors are\n semantic and sparse. Dark mode uses tonal levels and hairlines, not floating shadows.\n- **Feedback:** near-instant, non-blocking, time-aware; paused/live state is unmistakable.\n- **Reject:** decorative terminal cosplay, neon rainbow telemetry, excessive mono body copy,\n or animation that competes with changing data.", "editorial-reading": "### `editorial-reading`\n\n- **Job:** understand, retain, and navigate a narrative or argument.\n- **Attention:** title/deck/byline or the opening visual establishes the reading promise.\n- **Composition:** strong title rhythm → bounded reading column → meaningful media/pull quote →\n related context after the narrative. Chrome recedes.\n- **Density/type:** airy around the story; 45–90 characters per line, normally near 60–70;\n comfortable body size/leading; serif is optional and role-specific, never an automatic theme.\n- **Color/surface:** ink and paper-like neutrals may be used without faking print; one quiet\n accent for links and editorial signals. Whitespace and type replace gratuitous cards.\n- **Feedback:** reading position, save, share, and footnotes are calm and unobtrusive.\n- **Reject:** forcing all content into cards, app-dashboard chrome around prose, overly wide\n measures, serif everywhere, or interaction patterns that interrupt reading.", "commerce-conversion": "### `commerce-conversion`\n\n- **Job:** evaluate an offer, resolve uncertainty, select a variant, and commit.\n- **Attention:** product/service evidence leads; price, availability, primary CTA, and trust\n information remain easy to connect.\n- **Composition:** media → identity/price/proof → variants → primary action → delivery/returns →\n details and comparison. On mobile, keep the commitment action reachable without hiding terms.\n- **Density/type:** comfortable; product information is highly scannable; images are evidence,\n not decorative filler.\n- **Color/surface:** brand color supports the purchase action; ratings, discounts, stock, and\n errors use stable semantics rather than a promotional rainbow.\n- **Feedback:** variant and cart changes are immediate and reversible; costs and constraints\n appear before commitment.\n- **Reject:** urgency dark patterns, buried shipping/returns, competing CTAs, tiny variant\n targets, or a lifestyle mood that obscures the actual product.", "institutional-service": "### `institutional-service`\n\n- **Job:** understand eligibility or obligation, provide accurate information, and complete a\n consequential task with confidence.\n- **Attention:** task title, current step, and required action dominate over branding.\n- **Composition:** plain-language intro → prerequisites → one step at a time → review → clear\n confirmation and recovery path.\n- **Density/type:** comfortable, highly legible, robust at zoom; labels and help stay adjacent\n to controls; long content uses bounded measure.\n- **Color/surface:** conservative semantic palette with high contrast; errors never rely on\n color alone; decorative color is rare.\n- **Feedback:** preserve entered data, explain errors, expose progress, and provide reference\n numbers/next steps after completion.\n- **Reject:** novelty over comprehension, ambiguous icons, low-contrast minimalism, hidden\n requirements, or motion that makes a serious workflow feel unstable.", "expressive-marketing": "### `expressive-marketing`\n\n- **Job:** understand the proposition, believe the proof, and choose a next step.\n- **Attention:** one unmistakable promise paired with real product or brand evidence.\n- **Composition:** proposition → proof → differentiated mechanism → examples/outcomes → CTA.\n Section forms vary to create rhythm; repetition is deliberate, not template filler.\n- **Density/type:** airy with confident display hierarchy; body copy remains readable.\n- **Color/surface:** wider brand palette and expressive media are allowed when roles remain\n coherent and one action is primary.\n- **Feedback:** cinematic motion may support sequence, but first read and CTA work without it;\n reduced motion yields a complete page.\n- **Reject:** generic gradient headline, equal three-card feature rows, fake metrics, copied\n demo visuals, scroll-jacking, or motion used as a substitute for a proposition.", "sequential-story": "### `sequential-story`\n\n- **Job:** make one idea understandable and worth continuing across a bounded visual sequence.\n- **Attention:** slide/frame one earns the next gesture; each following frame has one dominant\n message and a visible place in the sequence.\n- **Composition:** hook → context/why → evidence or mechanism → useful action → reframe/close.\n Alternate big type, evidence, image, and utility frames so the sequence has rhythm.\n- **Density/type:** designed for the adapter's viewing distance and dwell time; one message per\n frame; body copy is bounded and never shrunk to rescue an overloaded slide.\n- **Color/surface:** project grammar and brand tokens carry across all frames; emphasis roles\n remain stable. Continuity comes from a system, not identical templates.\n- **Imagery:** crops, captions, and sources are intentional; generated-image text/logos are\n replaced during deterministic rendering.\n- **Feedback/navigation:** folio, progress, swipe cue, and CTA fit the publishing surface without\n occupying its unsafe UI zones.\n- **Reject:** ten identical cards, a weak explanatory cover, one composition repeated on every\n frame, content that works only as a caption, missing source attribution, or platform crop loss." }, "adapters": { "product-ui": "## `product-ui`\n\n- **Canvas:** responsive viewports declared in the design lock; verify at least one narrow and\n one wide target when both are in scope.\n- **Primitives:** semantic HTML and project-native components. Preserve framework conventions,\n routes, state, and real content rather than replacing the application with a mock.\n- **States:** loading, empty, error, success, disabled, focus, and responsive navigation are part\n of the artifact when the screen owns those behaviors.\n- **Export:** source code plus reproducible dev/build commands and screenshot paths.\n- **QA:** run project checks, render the real route, inspect target viewports and important states,\n and record what could not be exercised.", "social-carousel": "## `social-carousel`\n\nUse `sequential-story` unless another grammar clearly owns the content. The installed Claude\n`carousel-build` skill is the canonical companion when available:\n\n1. StyleSeed reads or compiles the grammar and writes brand/type/motion/content rules to\n `STYLESEED.md`.\n2. `carousel-build` reads that lock, then applies deterministic engineering constraints:\n 3:4 `1080×1440`, platform safe zones, crop behavior, 8px rhythm, type scale, gradient\n banding prevention, available font weights, and reproducible PIL rendering.\n3. Copy and publishing skills may add their own contracts without altering visual authority.\n4. `/ss-score` checks sequence coherence and grammar fit; `/ss-verify` opens every exported\n frame and checks crop, safe zone, typography, rhythm, false text, and continuity.\n\nRecommended lock additions:\n\n```markdown\n- Surface adapter: social-carousel\n- Artifact type: information-carousel\n- Canvas: 1080x1440\n- Sequence grammar: hook → why → evidence → action → reframe → CTA\n- Renderer: carousel-build\n- Safe zone contract: adapter:ADAPTERS.md#social-carousel-integration\n```\n\nDo not duplicate the renderer's rapidly changing platform measurements inside a visual grammar.\nThe adapter/companion owns them; StyleSeed owns the visual judgment applied within them.", "slide-deck": "## `slide-deck`\n\n- **Canvas:** use the presentation renderer's declared aspect ratio and safe area. Assume distance\n viewing; body copy that works on a web page is usually too small or dense on a slide.\n- **Sequence:** one claim per slide, visible narrative progression, and deliberate alternation\n between statement, evidence, comparison, and action.\n- **Assets:** use real charts, diagrams, screenshots, and cited imagery. Never use a text-heavy\n card grid as a substitute for a presentation.\n- **Export:** editable deck plus rendered PDF or page images.\n- **QA:** render every slide, inspect overflow and contrast, and compare repeated masters,\n alignment, folios, and speaker-facing information.", "document-report": "## `document-report`\n\n- **Canvas:** paginated output with explicit paper size, margins, headers/footers, and print-safe\n color. Reading measure and page breaks take priority over app-like chrome.\n- **Structure:** title and executive summary establish the decision; headings, figures, tables,\n notes, and appendices expose evidence at the right depth.\n- **Assets:** captions and sources remain attached to figures and tables. Repeated components use\n document styles rather than local formatting.\n- **Export:** editable source plus visually verified PDF.\n- **QA:** render every page and inspect widows/orphans, clipped tables, broken links, page numbers,\n accessibility structure, and cross-page consistency.", "single-frame": "## `single-frame`\n\n- **Canvas:** declare exact dimensions, crop variants, safe zones, and intended viewing distance.\n- **Composition:** one dominant message and one supporting action or proof. The frame must work\n without surrounding caption text unless the publishing contract says otherwise.\n- **Assets:** logos, product imagery, and text are deterministic and legible. Generated imagery\n must not supply final logos or critical text.\n- **Export:** source plus final PNG/JPEG/SVG variants and an asset manifest.\n- **QA:** inspect at native size and thumbnail size, verify crop variants, contrast, text safety,\n and platform compression risk." }, "domains": { "fintech": "## 1. Fintech / Banking / Payments\n\n- **Color:** maximum restraint — the brand accent is reserved for *money in\n motion* (CTAs, positive trend, the active balance). Greens/reds only for\n up/down, never decoration. Trust reads as calm, not loud.\n- **Density:** medium-low. One number should dominate each card. Whitespace\n signals \"we're careful with your money.\"\n- **Typography:** numbers first — hero balance at 48px with 24px unit (2:1).\n Currency, dates, and labels recede.\n- **Motion:** **Spring** (Toss-style confident bounce on CTAs) or **Silk** for\n balances and sheets. Never bouncy on a number that represents real money\n changing — it reads as unstable.\n- **Signature patterns:** HeroCard (balance), transaction `ListItem` with status\n dot, KPI `StatCard` with trend, period toggle, donut for spend breakdown.\n- **Anti-patterns:** playful/rainbow palettes, gradients on amounts, fake\n precision (`$8,400.0000`), shadows that float cards \"off the page,\" motion that\n delays seeing a balance.\n- **Brand recipe:** `calm-consumer`; use `native-mobile` for a platform-first utility.\n- **Skin material:** custom brand tokens; Toss and Stripe remain optional token references.", "saas": "## 2. SaaS / B2B Dashboard / Analytics\n\n- **Color:** disciplined grayscale with one accent for the primary action and\n selected state. Data viz gets a small, fixed categorical scale — not a new\n color per metric.\n- **Density:** high. Power users want information per pixel: tables, filters,\n multi-KPI rows. Density is a feature, not clutter — but keep rhythm.\n- **Typography:** balanced numbers + labels. Tables need tabular-nums and tight\n line-height; headings stay quiet.\n- **Motion:** **Snap** (Linear-style instant). Power users hate waiting on\n animation. Layout/FLIP for reordering, near-zero entrance.\n- **Signature patterns:** ChartCard (period toggle + bottom stats), dense KPI\n grid, filterable list/table, segmented control, RankedList.\n- **Anti-patterns:** decorative motion, oversized hero numbers that waste space,\n 6 accent colors in a chart legend, modal-heavy flows (prefer inline).\n- **Brand recipe:** `enterprise-workbench`; use `developer-platform` for technical evidence.\n- **Skin material:** custom brand tokens; Linear and Vercel remain optional token references.", "ecommerce": "## 3. E-commerce / Retail\n\n- **Color:** product imagery is the hero — UI chrome stays neutral so photos pop.\n The accent drives one thing: **add-to-cart / buy**. Price gets weight, not color.\n- **Density:** medium. Browsing = generous product cards; PDP = focused, one CTA\n above the fold.\n- **Typography:** price prominent (2:1 with currency), product title bold, specs\n quiet. Imagery > text in the hierarchy.\n- **Motion:** **Spring** (energetic, Arc-style) for add-to-cart, quantity stepper,\n cart badge pop (`pop-in`, `confetti-pop` on purchase is fair). Hover lift on\n product cards.\n- **Signature patterns:** product card grid, cart badge, quantity stepper, sticky\n buy bar, price + strikethrough, ranked/featured rails.\n- **Anti-patterns:** burying the CTA, more than one primary action on a PDP,\n shouty discount colors everywhere (dilutes urgency), motion that blocks adding\n to cart.\n- **Brand recipe:** `commerce-operator` for merchant/product operations; `calm-consumer` for a\n lightweight consumer purchase flow.\n- **Skin material:** custom brand tokens; Arc and Toss remain optional token references.", "social": "## 4. Social / Community / Feed\n\n- **Color:** energetic and warm — the accent can appear more often (likes,\n mentions, online dots). Still one accent, but a livelier hue.\n- **Density:** medium, content-led. Avatars and media drive the layout; chrome is\n minimal.\n- **Typography:** names bold, timestamps tiny and tertiary, body readable. Let\n user content (images, text) lead.\n- **Motion:** **Pulse** (alive, rhythmic) for likes/reactions (`like-burst`),\n live indicators (`pulse-beat`), and new-content arrival (`stagger-cascade`).\n- **Signature patterns:** feed list, avatar + name + time row, like/comment/share\n actions, like-burst, bottom-sheet composer, story rail.\n- **Anti-patterns:** heavy chrome that competes with user content, slow entrance\n on a feed (kills scroll), engagement bait colors, inconsistent avatar shapes.\n- **Brand recipe:** `native-mobile` for app-first feeds; `expressive-brand` for creator surfaces.\n- **Skin material:** custom warm accent; Arc remains an optional token reference.", "content": "## 5. Content / Media / News / Blog / Docs\n\n- **Color:** near-monochrome; the accent is for links and one CTA. Reading is the\n product — color is a distraction.\n- **Density:** low in the reading column (measure ~60–75ch), denser in nav/index.\n- **Typography:** **typography is the design.** Strong type scale, comfortable\n line-height (1.5–1.65 for body), real hierarchy between H/body/caption.\n- **Motion:** **Silk** (smooth, continuous) — `reveal-blur`/`reveal-rise` on\n headlines, subtle. Nothing that interrupts reading.\n- **Signature patterns:** article hero, readable body column, table of contents,\n pull quotes, related-content rail, code blocks (for docs).\n- **Anti-patterns:** full-width body text, decorative motion mid-article, multiple\n accents, cramped line-height, autoplaying anything.\n- **Brand recipe:** `editorial-authority`.\n- **Skin material:** custom editorial tokens; Notion and Vercel remain optional token references.", "productivity": "## 6. Productivity / Tools / Workspace\n\n- **Color:** quiet grayscale, one accent for primary action + active item.\n Calm so the user's *work* is the focus.\n- **Density:** high but organized — sidebars, panels, keyboard-first. Reward\n power use.\n- **Typography:** compact, tabular where needed, clear active/hover states.\n- **Motion:** **Snap** (instant, precise). Layout transitions for reorder; avoid\n anything that adds latency to a frequent action.\n- **Signature patterns:** sidebar + content + (optional) inspector, command\n palette, list/board toggle, inline edit, segmented control, keyboard hints.\n- **Anti-patterns:** slow motion on frequent actions, modal overload, decorative\n color, hiding power features behind too much progressive disclosure.\n- **Brand recipe:** `creative-professional` or `developer-platform` by task.\n- **Skin material:** custom brand tokens; Linear, Notion, and Vercel remain optional references.", "health": "## 7. Health / Wellness / Fitness\n\n- **Color:** calm and reassuring — soft accent, vivid only for *metric rings /\n progress* on a calm base. Avoid alarming reds except for genuine alerts.\n- **Density:** low-medium. One clear focus per screen (today's rings, next\n action). Reduce cognitive load — users may be tired or stressed.\n- **Typography:** big friendly numbers (2:1), gentle labels, generous spacing.\n- **Motion:** **Float** (weightless, gentle) for reveals; **Pulse** only for live\n heartbeat/recording. Motion should feel calm, never urgent.\n- **Signature patterns:** activity rings, big-metric hero, streak/progress, large\n touch targets (≥44px, often bigger), weekly history.\n- **Anti-patterns:** dense data dumps, alarming colors for normal states, tiny\n targets, jittery motion, shame-y empty states.\n- **Brand recipe:** `calm-consumer`; use `native-mobile` for tracking and capture.\n- **Skin material:** custom soft accent; Toss remains an optional token reference.", "education": "## 8. Education / Learning / Courses\n\n- **Color:** encouraging — accent marks progress and the next step. Use color to\n reward (completed = success tone), not to decorate.\n- **Density:** low per step (one concept at a time), denser in course index.\n- **Typography:** clear hierarchy, readable body, prominent \"what's next.\"\n- **Motion:** **Spring** for rewards/completion (`pop-in`, `confetti-pop` on\n finishing a module), `stagger-cascade` for lesson lists.\n- **Signature patterns:** progress bar/ring, step list with states, lesson card,\n next-action CTA, achievement/streak, empty→first-lesson onboarding.\n- **Anti-patterns:** showing the whole curriculum at once (overwhelm), unclear\n next step, punishing empty/incomplete states, no sense of progress.\n- **Brand recipe:** `calm-consumer` for learners; `editorial-authority` for reading-heavy courses.\n- **Skin material:** custom learning tokens; Notion and Arc remain optional references.", "developer-tools": "## 9. Developer Tools / Infra / API\n\n- **Color:** dark-first, restrained, one accent for primary/active. Syntax colors\n are their own controlled scale.\n- **Density:** high — devs read dense screens fine. Monospace where it belongs\n (code, IDs, logs).\n- **Typography:** mono for code/identifiers, tight tabular numbers, quiet UI text.\n- **Motion:** **Snap** (instant, precise). Devs distrust slow/flashy UI. Minimal,\n functional only.\n- **Signature patterns:** code blocks with copy, logs/terminal, status badges,\n command palette, key-value config, dark base.\n- **Anti-patterns:** flashy motion (reads as unserious to devs), light-only\n themes, decorative gradients, hiding the CLI/copy affordance.\n- **Brand recipe:** `developer-platform`.\n- **Skin material:** custom technical tokens; Raycast, Vercel, and Linear remain optional references.", "marketplace": "## 10. Marketplace / Listings (two-sided)\n\n- **Color:** trust + conversion — neutral chrome, accent for the primary action\n (book/contact/buy) and for ratings/verified signals.\n- **Density:** medium — scannable listing grid, focused detail page.\n- **Typography:** listing title bold, price/rating prominent, meta quiet.\n- **Motion:** **Silk** for transitions, hover lift on listing cards, `pop-in` for\n saved/favorited.\n- **Signature patterns:** listing card (image + title + price + rating), filters,\n map/list toggle, detail with sticky action, reviews, verified badge.\n- **Anti-patterns:** untrustworthy density (too much, too fast), weak rating/trust\n signals, more than one primary action, buried contact/CTA.\n- **Brand recipe:** `commerce-operator`.\n- **Skin material:** custom marketplace tokens; Stripe and Notion remain optional references.", "booking": "## 11. Booking / Travel / Reservations\n\n- **Color:** confident and visual — imagery (places, rooms) leads; accent drives\n the booking step. Calm so users feel sure about committing money/time.\n- **Density:** low-medium, step-focused. Dates and availability must be obvious.\n- **Typography:** clear dates/times, price prominent, friendly labels.\n- **Motion:** **Float** / **Silk** — smooth, reassuring transitions between steps;\n `reveal-blur` on imagery. Confidence, not flash.\n- **Signature patterns:** date/range picker, availability calendar, multi-step\n booking with progress, map, price summary, confirmation.\n- **Anti-patterns:** hidden total/fees, unclear current step, jarring motion mid-\n booking, tiny date controls, anxiety-inducing scarcity spam.\n- **Brand recipe:** `commerce-operator`; use `native-mobile` for an app-first itinerary.\n- **Skin material:** custom travel tokens; Arc and Notion remain optional references.", "ai-assistant": "## 12. AI / Chat / Assistant\n\n- **Color:** minimal chrome so the conversation is the focus; one accent for the\n send/primary action. Let content (the answer) lead.\n- **Density:** low chrome, high content. Generous reading width for responses.\n- **Typography:** readable body for answers, mono for code, quiet UI around the\n thread.\n- **Motion:** **Silk** — streaming/typing feel, smooth message entrance\n (`reveal-blur`/`stagger`), nothing that competes with reading the answer.\n- **Signature patterns:** message thread, streaming response, composer with\n send, prompt suggestions, copy-on-message, minimal top bar.\n- **Anti-patterns:** heavy chrome around the chat, flashy motion on every token,\n cramped reading width, burying the input, multiple accents.\n- **Brand recipe:** `creative-professional` for workbench assistants; `calm-consumer` for simple\n personal assistants.\n- **Skin material:** custom assistant tokens; Raycast and Notion remain optional references.\n\n---" }, "pages": { "dashboard": "## Dashboard / Home / Overview\n\n- **Job:** answer \"how are things?\" in 3 seconds, then let the user drill down.\n- **Structure:** information pyramid — one hero metric → a small KPI set →\n supporting list/chart. Vary section types (Rule 14/61): never four identical\n cards in a row.\n- **Hierarchy:** density increases as you scroll. Top = 48px hero number; bottom\n = 13–14px detailed rows.\n- **Patterns:** HeroCard, KPI grid (mixed: trend / progress / comparison),\n ChartCard, RankedList, BriefingCarousel for alerts.\n- **Anti-patterns:** wall of identical KPIs, no clear primary metric, charts with\n 6 legend colors, everything the same visual weight.\n- **Mobile:** single column, hero first, horizontal-scroll carousels for KPI sets,\n `mx-6` single cards / `px-6` grids.", "form": "## Form / Create / Edit\n\n- **Job:** get accurate input with the least friction and the most confidence.\n- **Structure:** **single column**, logical grouping into `SectionCard`s, one\n clear primary action (bottom or sticky). Labels **above** fields, not beside.\n- **Hierarchy:** the field you're on > the next field > everything else. Primary\n action visually dominant; secondary/cancel quiet.\n- **Patterns:** labeled inputs, inline validation (validate on blur, not on every\n keystroke), grouped sections, sticky save bar, `wiggle` + helper text on error,\n clear required/optional marking.\n- **Anti-patterns:** multi-column forms (eye zig-zags), placeholder-as-label,\n validating before the user finishes, two primary buttons, error states with no\n recovery guidance, disabled submit with no explanation.\n- **Mobile:** full-width fields, ≥44px touch targets, numeric keyboards for number\n fields, sticky primary above the keyboard.", "landing": "## Landing / Marketing / Home (public)\n\n- **Job:** in one screen, say what it is + why it matters + one next action.\n- **Structure:** hero (headline + subhead + single primary CTA) → proof\n (features/social proof) → CTA again. One conversion goal per page.\n- **Hierarchy:** headline dominates; CTA is the single brightest element; supporting\n text recedes. The accent belongs to the CTA.\n- **Patterns:** hero with one CTA, feature grid, social proof (logos/stats/quotes),\n before/after, comparison, closing CTA.\n- **Motion — this is the ONE surface where the Cinematic tier applies (DESIGN-LANGUAGE §43).**\n Unlike an app/dashboard, a brand page *should* use motion as craft: **scroll-LINKED reveals,\n pinned/sticky sections, sequential \"the product assembles as you scroll\" choreography, subtle\n parallax, a 3D/tilt hero or showcase card, an animated gradient/mesh or video background, rich\n hover** (magnetic/glow/lift). This is how family.co / stripe.com / linear.app read premium —\n don't apply dashboard restraint here. Guardrails still hold: purposeful (not jitter), 60fps\n (`transform`/`opacity` only), never blocks the first read or the CTA/LCP, `prefers-reduced-motion`\n leaves a complete static page, one motion language.\n- **Anti-patterns:** multiple competing CTAs, wall of text, every section the same rhythm,\n autoplaying *audio*, motion that **delays the headline or hides content until you scroll**,\n **scroll-JACKING** (hijacking scroll speed / trapping — different from scroll-linked, which is\n fine), six accent colors, no reduced-motion fallback.\n- **Mobile:** stack everything, keep the CTA reachable, don't shrink the headline\n into mush.", "detail": "## Detail / Profile / Item\n\n- **Job:** show one thing deeply, with its primary action obvious.\n- **Structure:** identity header (title/image/status) → key facts → body/sections →\n one primary action (often sticky on mobile).\n- **Hierarchy:** the subject's name/title and its primary action win. Metadata is\n tertiary.\n- **Patterns:** hero/identity block, key-value facts, tabbed or sectioned body,\n sticky primary action, related items rail, status indicators.\n- **Anti-patterns:** burying the primary action, equal weight on everything, no\n clear \"what is this,\" metadata louder than the subject.\n- **Mobile:** sticky action bar, collapse long sections, single column.", "list": "## List / Index / Browse / Search\n\n- **Job:** scan many items fast, find the right one, act.\n- **Structure:** optional filter/search bar → consistent rows/cards → clear\n per-item action or tap target. Consistency beats variety here.\n- **Hierarchy:** the item's identifying field (name/title) is boldest; status and\n meta are quieter; the value/amount is emphasized on the trailing edge.\n- **Patterns:** `ListItem` (title + status dot + trailing value), filterable list,\n segmented control, swipe actions on mobile, empty state, `stagger-cascade`\n entrance, skeleton while loading.\n- **Anti-patterns:** rows that vary wildly, no empty/loading state, status by color\n alone (pair with text/dot), tiny tap targets, pagination where infinite scroll\n fits (or vice-versa).\n- **Mobile:** full-width rows, swipe-to-act, ≥44px rows, sticky filter.", "settings": "## Settings / Account / Preferences\n\n- **Job:** let the user find and change one setting with confidence, safely.\n- **Structure:** grouped `SectionCard`s by topic (profile / notifications /\n billing / danger), each setting a labeled row with its control on the trailing\n edge. Destructive actions isolated and clearly marked.\n- **Hierarchy:** flat and scannable — settings are equal-weight within a group;\n group titles orient. Danger zone visually separated.\n- **Patterns:** toggle rows, select rows, account header, billing card, **danger\n zone** (the one place a functional border + destructive tone is right),\n inline-save or explicit-save (be consistent).\n- **Anti-patterns:** destructive actions next to benign ones, unclear save model,\n settings with no labels, toggles whose state is ambiguous, no confirmation on\n irreversible actions.\n- **Mobile:** full-width rows, controls reachable with the thumb, ≥44px toggles.", "onboarding": "## Onboarding / First-run / Empty\n\n- **Job:** get the user to their first win with minimal steps, never a dead end.\n- **Structure:** few steps with visible progress, one decision per step, a strong\n \"what's next.\" Empty states are onboarding in disguise — always offer the next\n action.\n- **Hierarchy:** the current step and its single action dominate; progress is\n visible but quiet.\n- **Patterns:** stepper/progress, one-question-per-screen, `EmptyState` (icon +\n title + description + action), `pop-in`/`confetti-pop` on completion, contextual\n tips, skip/defer where fair.\n- **Anti-patterns:** asking everything up front, empty screens with no next action,\n no sense of progress, punishing or shaming empty states, forcing setup before\n any value.\n- **Mobile:** one step per screen, big primary, progress at top.\n\n---" }, "recipes": { "calm-consumer": "## `calm-consumer`\n\n- **Best fit:** personal state, reassurance, benefits, lightweight health, and short recurring\n tasks. Strong with `consumer-service`; usable for a gentle `commerce-conversion`.\n- **Containment:** tonal groups and a few soft cards. One summary may float; secondary rows\n should not become an equal card wall.\n- **Geometry:** 12–20px outer radius, smaller nested radius, restrained shadow or tonal\n separation, comfortable 20–24px gutters.\n- **Type/icons:** friendly sans, plain-language values, simple line icons without repeated\n tinted icon chips.\n- **Controls/collections:** reachable primary action, short rows or grouped sections, pill\n controls only for true compact choices.\n- **Motion:** immediate and reassuring; spring may be restrained; consequential values do not\n count theatrically.\n- **Characteristic move:** one calm contextual briefing connected to the user's current state.\n- **Reject:** copying Toss layouts, every service as a rounded card, blue as an automatic brand,\n cute language in serious states, or chips as decoration.\n- **Lineage:** StyleSeed consumer-service research; brand examples are evidence, not sources to\n copy.", "native-mobile": "## `native-mobile`\n\n- **Best fit:** focused mobile utilities, capture, communication, media, and one-handed tasks.\n Compatible with any grammar whose primary surface is a mobile app.\n- **Containment:** content is primary; navigation and controls recede into platform-familiar\n bars, sheets, lists, and grouped regions.\n- **Geometry:** platform-aware radii and materials, 16–20px screen gutters, touch targets at\n least 44px, no desktop card grid squeezed into a phone.\n- **Type/icons:** dynamic type and platform conventions; system symbols when licensed for the\n target platform, otherwise one consistent open icon family.\n- **Controls/collections:** few visible controls, secondary actions disclosed nearby, common\n gestures have visible alternatives, important actions remain reachable.\n- **Motion/responsive:** adapt to orientation, dark mode, text scaling, and device insets;\n transitions preserve spatial continuity.\n- **Characteristic move:** one content-first task with controls concentrated in the reachable\n middle or lower region.\n- **Reject:** decorative glass imitation, copying Apple assets, invisible gesture-only actions,\n tiny targets, or a web navbar pretending to be native.\n- **Lineage:** [Apple Human Interface Guidelines](https://developer.apple.com/design/human-interface-guidelines).", "enterprise-workbench": "## `enterprise-workbench`\n\n- **Best fit:** admin, analytics, operations, collaboration, and multi-step B2B work. Strong\n with `operations-console`.\n- **Containment:** persistent shell, aligned panels, toolbars, tables, and detail regions.\n Group by work relationship; use card grids sparingly.\n- **Geometry:** 0–8px radius, 1px boundaries or tonal layers, minimal floating shadow, 16–24px\n page rhythm on an explicit grid.\n- **Type/icons:** neutral UI sans, tabular numbers, compact labels, one functional icon family.\n- **Controls/collections:** rectangular controls, visible filters, bulk actions, dense rows,\n comparison tables, and preserved loading geometry.\n- **Motion/responsive:** fast state changes; panels reflow or collapse by task priority rather\n than merely shrinking.\n- **Characteristic move:** one operational focal panel connected directly to an actionable\n queue or evidence table.\n- **Reject:** identical KPI cards, oversized mobile typography on desktop, decorative\n gradients, hidden scope controls, or floating shadows on every panel.\n- **Lineage:** [IBM Carbon 2x Grid](https://carbondesignsystem.com/elements/2x-grid/overview/),\n [Microsoft Fluent 2](https://fluent2.microsoft.design/design-principles),\n [Atlassian foundations](https://atlassian.design/foundations).", "developer-platform": "## `developer-platform`\n\n- **Best fit:** repositories, observability, infrastructure, APIs, and security. Strong with\n `technical-instrument`; usable for technical `operations-console`.\n- **Containment:** stable shell, compact toolbars, hairline-separated rows, code/evidence\n regions, and contextual drill-down.\n- **Geometry:** 4–8px radius, hairline borders, little or no shadow, compact 12–20px rhythm.\n- **Type/icons:** sans for UI; mono only for identifiers, timestamps, logs, commands, and aligned\n numeric evidence. Icons are small and functional.\n- **Controls/collections:** rectangular or lightly rounded controls, status-aware tables,\n timelines, command palettes, and copyable evidence.\n- **Motion/responsive:** near-instant, non-blocking, time-aware; live/paused state is explicit.\n- **Characteristic move:** one inspectable evidence region that connects status to diagnosis.\n- **Reject:** terminal cosplay, neon telemetry, mono body copy, rounded feature-card grids, or\n animation that competes with live data.\n- **Lineage:** [GitHub Primer foundations](https://primer.style/product/getting-started/foundations/)\n and [Primer pattern guidance](https://primer.style/product/contribute/design/).", "commerce-operator": "## `commerce-operator`\n\n- **Best fit:** merchant admin, inventory, orders, fulfillment, customer support, and complex\n purchase operations. Strong with `operations-console` and `commerce-conversion`.\n- **Containment:** resource index → filters → actionable rows → contextual detail. Cards group\n merchant decisions, not every datum.\n- **Geometry:** 8–12px radius, clear boundaries, moderate density, restrained elevation for\n overlays and temporary context only.\n- **Type/icons:** highly scannable labels and values; product imagery is evidence; status text\n accompanies semantic color.\n- **Controls/collections:** filter bars, resource tables/lists, contextual actions, variant and\n fulfillment state, reversible mutations.\n- **Motion/responsive:** preserve selection and filters; mobile promotes the current task and\n moves secondary columns into detail.\n- **Characteristic move:** a resource row or order state exposes the next operational action\n without opening a decorative card.\n- **Reject:** promotional rainbow admin UI, buried costs or constraints, ambiguous statuses,\n equal-weight analytics tiles, or urgency dark patterns.\n- **Lineage:** [Shopify Polaris](https://polaris-react.shopify.com/) and StyleSeed commerce\n research. Reuse concepts, not Shopify trade dress.", "public-service": "## `public-service`\n\n- **Best fit:** eligibility, applications, regulated forms, healthcare workflows, and civic\n services. Strong with `institutional-service`.\n- **Containment:** flat document flow, bounded reading measure, explicit sections, one step at a\n time, review, confirmation, and recovery.\n- **Geometry:** 0–4px radius, strong visible boundaries, no decorative shadow, generous vertical\n separation, high-contrast focus.\n- **Type/icons:** robust sans, plain language, adjacent labels/help, icons never replace critical\n words.\n- **Controls/collections:** rectangular buttons and inputs, clear legends, summaries and error\n links, preserved entered data, reference number on completion.\n- **Motion/responsive:** minimal and non-essential; layout survives zoom, reflow, text scaling,\n keyboard, and assistive technology.\n- **Characteristic move:** the current task and its requirements are more visually prominent\n than the organization brand.\n- **Reject:** low-contrast minimalism, novelty navigation, hidden prerequisites, rounded app\n cards, altered control meanings, or motion that makes the workflow feel unstable.\n- **Lineage:** [GOV.UK patterns](https://design-system.service.gov.uk/patterns/) and\n [community principles](https://design-system.service.gov.uk/community/community-principles/).", "creative-professional": "## `creative-professional`\n\n- **Best fit:** creation, editing, asset management, media, and expert cross-platform tools.\n Compatible with `operations-console`, `technical-instrument`, and `sequential-story`.\n- **Containment:** focused canvas or artifact, quiet utility chrome, named tool groups, inspectors,\n and progressive disclosure.\n- **Geometry:** 4–8px radius, crisp boundaries, restrained layers, density adapts between\n pointer and touch.\n- **Type/icons:** rational, compact, internationalizable labels; icons support trained use but\n critical actions retain text or discoverable labels.\n- **Controls/collections:** toolbars, property panels, asset grids, contextual controls, and\n explicit selection state.\n- **Motion/responsive:** desktop and mobile scale independently while sharing one language;\n motion explains selection, mode, and spatial change.\n- **Characteristic move:** the user's work occupies the focal field while tools form a\n disciplined supporting frame.\n- **Reject:** decoration around the canvas, one scale stretched across all inputs, unlabeled\n mystery tools, or copying Adobe product chrome.\n- **Lineage:** [Adobe Spectrum principles](https://spectrum.adobe.com/page/principles/) and\n [platform scale](https://spectrum.adobe.com/page/platform-scale/).", "editorial-authority": "## `editorial-authority`\n\n- **Best fit:** journalism, reports, research, policy, and documentation. Strong with\n `editorial-reading`; usable for evidence-heavy `expressive-marketing`.\n- **Containment:** type, whitespace, rules, captions, and bounded columns replace app cards.\n Chrome recedes after orientation.\n- **Geometry:** 0–4px radius, hairline rules, little or no shadow, generous section rhythm and\n 45–90 character reading measures.\n- **Type/icons:** deliberate display/body roles, serif optional and role-specific, captions and\n sources remain attached to evidence.\n- **Controls/collections:** calm inline actions, table of contents, footnotes, save/share,\n figures, pull quotes, and related context after the narrative.\n- **Motion/responsive:** reading position and disclosure only; narrow screens preserve hierarchy\n and source relationships rather than stacking arbitrary cards.\n- **Characteristic move:** an authoritative opening promise followed by inspectable evidence.\n- **Reject:** dashboard chrome around prose, every section in a card, overly wide measure, serif\n everywhere, fake print texture, or interruption-heavy interactions.\n- **Lineage:** StyleSeed editorial research and public-content accessibility guidance.", "expressive-brand": "## `expressive-brand`\n\n- **Best fit:** campaigns, launches, portfolios, brand pages, posters, and social stories.\n Strong with `expressive-marketing` and `sequential-story`.\n- **Containment:** section form varies with the narrative; proof, product media, and display type\n create rhythm instead of a repeated feature-card template.\n- **Geometry:** project-specific and intentionally consistent; one signature geometry may be\n sharp, soft, or sculptural, but nested and control shapes stay coherent.\n- **Type/icons:** distinctive display hierarchy plus readable body; commissioned or licensed\n imagery carries identity more than generic icons.\n- **Controls/collections:** one identifiable CTA, product demonstrations, outcomes, and examples;\n repeated collections earn their repetition.\n- **Motion/responsive:** cinematic choreography is allowed when native scroll remains under user\n control and reduced motion yields a complete result.\n- **Characteristic move:** one product-specific visual mechanism that could not be swapped into\n an unrelated landing page.\n- **Reject:** generic gradient headlines, equal three-card rows, fake metrics, scroll-jacking,\n copied campaign compositions, or motion that substitutes for a proposition.\n- **Lineage:** independent brand/campaign research; compile supplied references with\n `ss-reference` when a particular visual language matters.\n\n## Legal and promotion boundary\n\n- Reference-family names document provenance; never present a recipe as official, endorsed, or\n pixel-compatible with those systems.\n- Do not redistribute protected logos, proprietary icons, fonts, illustrations, product copy,\n screenshots, or trademarked arrangements.\n- A project-local reference grammar remains the correct path for a specific brand. Promote it to\n a built-in recipe only after multiple independent sources and transfer tests prove that the\n morphology is reusable and not a clone." }, "palettes": { "quiet-mineral": "### quiet-mineral\n\n- Name: Quiet mineral\n- Mode: light\n- Best for: Calm consumer products, health, benefits, and personal utilities\n- Recipe bias: calm-consumer, native-mobile\n- Semantic roles: background=#F3F0E8 · surface=#FFFDF8 · chrome=#DCE7E0 · foreground=#19211F · mutedForeground=#56635F · chromeForeground=#19211F · border=#BFC9C2 · primary=#276B5E · primaryForeground=#FFFFFF · accent=#D56A45 · accentForeground=#211713 · focus=#155EEF · success=#1E6F50 · successForeground=#FFFFFF · warning=#8A5700 · warningForeground=#FFFFFF · danger=#B42318 · dangerForeground=#FFFFFF\n- Usage: Let warm neutrals carry most of the canvas. Reserve green for the primary action and current-state reassurance; keep coral below ten percent.\n- Generated-media anchors: #F3F0E8, #276B5E, #D56A45\n- Avoid in generated media: neon blue, rainbow gradients, blue-purple AI glow\n- Re-run deterministic contrast validation after any project override.", "deep-lime-studio": "### deep-lime-studio\n\n- Name: Deep lime studio\n- Mode: dark\n- Best for: Creative work, focused productivity, and high-craft prototypes\n- Recipe bias: creative-professional, expressive-brand\n- Semantic roles: background=#0B0D0F · surface=#15191D · chrome=#262C31 · foreground=#F5F4ED · mutedForeground=#A8AFAB · chromeForeground=#F5F4ED · border=#465057 · primary=#B8FF5A · primaryForeground=#10140C · accent=#7AA7FF · accentForeground=#0B1020 · focus=#B8FF5A · success=#75E6A4 · successForeground=#0B1A10 · warning=#FFC857 · warningForeground=#1B1300 · danger=#FF766E · dangerForeground=#200704\n- Usage: Use lime for selection and one decisive action, never as body text. Layer chrome one step lighter than the canvas; let generated imagery remain low-luminance.\n- Generated-media anchors: #0B0D0F, #B8FF5A, #7AA7FF\n- Avoid in generated media: pure-white bloom, multicolor neon, lime on light backgrounds\n- Re-run deterministic contrast validation after any project override.", "cobalt-instrument": "### cobalt-instrument\n\n- Name: Cobalt instrument\n- Mode: light\n- Best for: Developer platforms, data products, and operational workbenches\n- Recipe bias: developer-platform, enterprise-workbench\n- Semantic roles: background=#F1F5FA · surface=#FFFFFF · chrome=#101828 · foreground=#101828 · mutedForeground=#475467 · chromeForeground=#F9FAFB · border=#C7D1E0 · primary=#175CD3 · primaryForeground=#FFFFFF · accent=#6941C6 · accentForeground=#FFFFFF · focus=#175CD3 · success=#067647 · successForeground=#FFFFFF · warning=#934F00 · warningForeground=#FFFFFF · danger=#B42318 · dangerForeground=#FFFFFF\n- Usage: Use neutral layers for evidence and cobalt for action/selection. Violet belongs to secondary categorization, not a second primary action.\n- Generated-media anchors: #101828, #175CD3, #F1F5FA\n- Avoid in generated media: cyan terminal glow, decorative gradients, low-contrast gray text\n- Re-run deterministic contrast validation after any project override.", "warm-clay-commerce": "### warm-clay-commerce\n\n- Name: Warm clay commerce\n- Mode: light\n- Best for: Commerce, hospitality, booking, and human service brands\n- Recipe bias: commerce-operator, calm-consumer\n- Semantic roles: background=#FFF8F2 · surface=#FFFFFF · chrome=#2B201B · foreground=#2B201B · mutedForeground=#6B5549 · chromeForeground=#FFF8F2 · border=#DCCBC0 · primary=#A64005 · primaryForeground=#FFFFFF · accent=#6441C4 · accentForeground=#FFFFFF · focus=#1D5FD0 · success=#187451 · successForeground=#FFFFFF · warning=#8A5700 · warningForeground=#FFFFFF · danger=#B42318 · dangerForeground=#FFFFFF\n- Usage: Let product imagery and warm paper carry identity. Clay marks purchase intent; violet is reserved for saved or personalized context.\n- Generated-media anchors: #FFF8F2, #A64005, #2B201B\n- Avoid in generated media: orange sale walls, high-saturation red urgency, generic purple gradient\n- Re-run deterministic contrast validation after any project override.", "civic-blue": "### civic-blue\n\n- Name: Civic blue\n- Mode: light\n- Best for: Public services, regulated applications, and consequential workflows\n- Recipe bias: public-service, enterprise-workbench\n- Semantic roles: background=#F3F5F7 · surface=#FFFFFF · chrome=#003078 · foreground=#0B0C0C · mutedForeground=#4C6272 · chromeForeground=#FFFFFF · border=#B1B4B6 · primary=#1D5F91 · primaryForeground=#FFFFFF · accent=#00703C · accentForeground=#FFFFFF · focus=#B45F06 · success=#00703C · successForeground=#FFFFFF · warning=#8A5700 · warningForeground=#FFFFFF · danger=#B42318 · dangerForeground=#FFFFFF\n- Usage: Use blue for institution and primary action, green only for confirmed success, and amber focus with a visible outline. Pair every status with text.\n- Generated-media anchors: #003078, #F3F5F7, #00703C\n- Avoid in generated media: pastel minimalism, glass navigation, color-only status\n- Re-run deterministic contrast validation after any project override.", "editorial-ink": "### editorial-ink\n\n- Name: Editorial ink\n- Mode: light\n- Best for: Research, journalism, reports, and authoritative reading\n- Recipe bias: editorial-authority, public-service\n- Semantic roles: background=#F5F1E8 · surface=#FFFCF6 · chrome=#111111 · foreground=#111111 · mutedForeground=#5B564E · chromeForeground=#FFFFFF · border=#C9C0B2 · primary=#8F2C21 · primaryForeground=#FFFFFF · accent=#1D4E9E · accentForeground=#FFFFFF · focus=#1D4E9E · success=#176B45 · successForeground=#FFFFFF · warning=#805200 · warningForeground=#FFFFFF · danger=#A12B22 · dangerForeground=#FFFFFF\n- Usage: Use ink and paper for the reading field. Red marks editorial emphasis sparingly; blue owns links and focus.\n- Generated-media anchors: #F5F1E8, #111111, #8F2C21\n- Avoid in generated media: fake newspaper texture, sepia photos, card-grid chrome\n- Re-run deterministic contrast validation after any project override.", "signal-coral": "### signal-coral\n\n- Name: Signal coral\n- Mode: light\n- Best for: Expressive launches, social products, and consumer discovery\n- Recipe bias: expressive-brand, native-mobile\n- Semantic roles: background=#FFF3EC · surface=#FFFFFF · chrome=#1A1423 · foreground=#1A1423 · mutedForeground=#645A6C · chromeForeground=#FFFFFF · border=#D8C9D0 · primary=#C83D2C · primaryForeground=#FFFFFF · accent=#5B3EC8 · accentForeground=#FFFFFF · focus=#5B3EC8 · success=#19724E · successForeground=#FFFFFF · warning=#875400 · warningForeground=#FFFFFF · danger=#A92924 · dangerForeground=#FFFFFF\n- Usage: Let coral own the hook and selected moment. Violet supports spatial or media context; never let both compete as primary actions.\n- Generated-media anchors: #FFF3EC, #C83D2C, #5B3EC8\n- Avoid in generated media: pink-purple gradient wash, rainbow icon chips, coral body text\n- Re-run deterministic contrast validation after any project override.", "nocturne-violet": "### nocturne-violet\n\n- Name: Nocturne violet\n- Mode: dark\n- Best for: Media, AI, experimental professional tools, and immersive utilities\n- Recipe bias: creative-professional, developer-platform\n- Semantic roles: background=#0D0B16 · surface=#171327 · chrome=#2A2341 · foreground=#F6F2FF · mutedForeground=#B3A9C9 · chromeForeground=#F6F2FF · border=#554A70 · primary=#A98BFF · primaryForeground=#160F28 · accent=#4BE0C3 · accentForeground=#06251F · focus=#D1C2FF · success=#65D6A2 · successForeground=#062118 · warning=#F4BF55 · warningForeground=#241700 · danger=#FF8078 · dangerForeground=#2A0705\n- Usage: Use violet for primary control and mint for creation/progress. Keep media dark enough to preserve chrome and avoid synthetic AI-glow overload.\n- Generated-media anchors: #0D0B16, #A98BFF, #4BE0C3\n- Avoid in generated media: electric blue haze, purple gradient headlines, white bloom behind text\n- Re-run deterministic contrast validation after any project override." }, "profiles": { "swiss": "### swiss\n\n- Coordinate: sharp · structured · compact · restrained · snap\n- Signature: asymmetric grid and typographic alignment\n- This profile does not permit: illegible tiny type or ornament-free sameness\n- Apply the coordinate coherently across radius, density, typography, palette temperature, elevation, motion, composition, and one signature move.", "editorial": "### editorial\n\n- Coordinate: soft/sharp · airy · warm-muted · silk\n- Signature: one display-type moment\n- This profile does not permit: serif body on every product surface\n- Apply the coordinate coherently across radius, density, typography, palette temperature, elevation, motion, composition, and one signature move.", "technical": "### technical\n\n- Coordinate: sharp · dense · cool · still\n- Signature: mono evidence and tonal layers\n- This profile does not permit: decorative terminal cosplay\n- Apply the coordinate coherently across radius, density, typography, palette temperature, elevation, motion, composition, and one signature move.", "warm-dtc": "### warm-dtc\n\n- Coordinate: soft/pill · airy · warm-vivid · spring\n- Signature: tactile product/image moment\n- This profile does not permit: competing warm colors or pill-everything\n- Apply the coordinate coherently across radius, density, typography, palette temperature, elevation, motion, composition, and one signature move.", "minimal-mono": "### minimal-mono\n\n- Coordinate: sharp/soft · airy · near-monochrome · snap/silk\n- Signature: one precise typographic gesture\n- This profile does not permit: missing hierarchy or invisible controls\n- Apply the coordinate coherently across radius, density, typography, palette temperature, elevation, motion, composition, and one signature move.", "brutalist-lite": "### brutalist-lite\n\n- Coordinate: sharp · comfortable · high-contrast · snap\n- Signature: one hard structural move\n- This profile does not permit: broken states, mixed border weights, or inaccessible contrast\n- Apply the coordinate coherently across radius, density, typography, palette temperature, elevation, motion, composition, and one signature move." }, "agents": { "claude": "## Claude Code execution contract\n\n- Invoke StyleSeed skills with `/ss-*`.\n- Read this compiled bundle before implementation; do not load the full handbook unless a named ambiguity remains.\n- Use the selected renderer, run `/ss-score`, then inspect rendered output with `/ss-verify`.", "codex": "## Codex execution contract\n\n- Invoke StyleSeed skills with `$ss-*` or the Skills picker.\n- Read this compiled bundle before implementation; do not load the full handbook unless a named ambiguity remains.\n- Run project checks, then `$ss-score`; render and inspect the actual artifact with `$ss-verify` before claiming completion.", "cursor": "## Cursor execution contract\n\n- Use the installed StyleSeed skills from the skill picker or follow this bundle directly.\n- Keep decisions in project files, run the project checks, and inspect the real rendered artifact before delivery.", "generic": "## Agent execution contract\n\n- Treat this compiled bundle as the active StyleSeed context.\n- Keep decisions in project files, run available project checks, and inspect the real rendered artifact before delivery." } }