# StyleSeed Effective Rule Bundle - Engine: 4.0.0 - Agent: claude - Output grammar: operations-console - Surface adapter: product-ui - Domain: booking - Page type: dashboard - Brand recipe: enterprise-workbench - Palette recipe: signal-coral - Generated palette: #FF6966 · light · balanced · auto - Aesthetic profile: warm-dtc Read this bundle before implementation. The agent execution contract is operational; method authority then runs core → grammar → adapter → domain/page → brand recipe → palette recipe → profile → lock → compact craft baseline, with the earlier method layer winning conflicts. Run the code gate and rendered visual gate. ## Claude Code execution contract - Invoke StyleSeed skills with `/ss-*`. - Read this compiled bundle before implementation; do not load the full handbook unless a named ambiguity remains. - Use the selected renderer, run `/ss-score`, then inspect rendered output with `/ss-verify`. --- # StyleSeed Product Constitution StyleSeed is an **AI design-method engine**. Its primary job is to make a coding agent reason like a strong UI/UX designer and apply that reasoning consistently. Components, skins, scores, and screenshots support that job; they do not define it. ## The fixed method, not one fixed look StyleSeed enforces a stable way of judging design. It does **not** force every product to look like Toss, a SaaS dashboard, or the StyleSeed demo. A trustworthy consumer-finance home, an observability console, an editorial story, and a product-detail page solve different jobs and therefore need different design grammars. The effective rule set is composed: ```text Core judgment × one output grammar from RULESETS.md (built-in or reference-compiled) × one surface adapter from ADAPTERS.md × one domain playbook from APP-PLAYBOOKS.md × one page type from PAGE-TYPES.md × one brand recipe from BRAND-RECIPES.md × one semantic palette posture plus an optional key-color generation from PALETTE-RECIPES.md × optional aesthetic profile from PRESETS.md × bounded project tokens from STYLESEED.md = the rules for this screen ``` ## Authority order When instructions disagree, use this order: 1. **Core invariants** below. 2. **Output grammar** — the functional visual language selected in `RULESETS.md`, or a project-local grammar compiled by `REFERENCE-COMPILER.md`. 3. **Surface adapter** — the renderer contract and physical constraints in `ADAPTERS.md`. 4. **Domain playbook** and **page/artifact type**. 5. **Brand recipe** — a reusable morphology and component-selection contract from `BRAND-RECIPES.md`. 6. **Palette system** — a maintained semantic posture plus deterministic key-color generation, role mapping, gamut handling, and contrast correction from `PALETTE-RECIPES.md`. 7. **Aesthetic profile** — an optional coordinated restyle from `PRESETS.md`. 8. **Design lock** — records selections and bounded project parameters. 9. **Skins and components** — implementation material, not sources of judgment. 10. **Score and visual verification** — evidence that the method was applied. `STYLESEED.md` is persistence, not permission. An arbitrary value in the lock never turns a violation into a sound design decision. Unknown values fall back to the nearest maintained grammar and the core defaults. ## Core invariants These apply to every grammar, profile, domain, page, skin, and agent: - One deliberate visual system per product: radius, spacing, elevation, icon language, typography, color roles, imagery, and motion agree. - One focal point per screen and a clear information hierarchy. - Color communicates role or meaning. One primary action remains identifiable even when semantic, categorical, or product colors are present. - Semantic tokens replace component-level hardcoded colors. - Spacing follows a repeatable scale; proximity communicates grouping. - Typography fits the surface and task, with readable measure, contrast, and hierarchy. - Data surfaces include useful loading, empty, and error states. - Controls remain operable: visible focus, sufficient targets, labels, reduced-motion support, and no dark patterns. - Motion fits the surface and never delays comprehension or action. - Distinctiveness comes from the product, its content, and its selected grammar — not a copied demo, generic indigo, repeated icon chips, emoji chrome, or template uniformity. ## What the lock may select The lock may select only inputs the engine understands: - domain, surface adapter, page/artifact type, and one output grammar; - one maintained brand recipe, one semantic palette posture, optional bounded key-color generation, one optional aesthetic profile, and one skin or project token implementation; - primary action/accent, type pairing, density, radius, elevation, imagery, and motion values inside the selected grammar's allowed ranges; - one product-specific signature move that still obeys the invariants; - a project-local reference grammar with provenance and confidence recorded by the compiler. The lock may not invent a palette mode, waive accessibility, legalize mixed systems, or override a core invariant. A reusable built-in grammar requires research, examples, and regression evaluation. A reference-derived grammar stays project-local until it meets that bar. ## The product loop ```text understand the job → choose or compile a grammar → lock bounded decisions → build with judgment → score the implementation → visually verify rendered output → present the result and evidence ``` The build method is the product. Scoring and verification are auxiliary gates: they find drift, but they never choose or rewrite the design philosophy after the fact. --- ### `operations-console` - **Job:** scan system or business state, compare changes, find exceptions, act efficiently. - **Attention:** one operational focal panel; supporting KPIs form hierarchy rather than a uniform card wall. - **Composition:** persistent navigation → scope/time controls → focal trend or queue → comparable metrics → actionable table/list. Detail lives below or on demand. - **Density/type:** comfortable to compact; neutral grotesk; tabular numerals; labels may be small but body and decisions remain readable on desktop. - **Color/surface:** restrained brand accent; categorical colors only for stable, repeated data semantics. Tone, alignment, and grouping carry more hierarchy than decoration. - **Feedback:** filters and mutations respond instantly; loading preserves layout; bulk action consequences are explicit. - **Reject:** same-weight KPI tiles everywhere, decorative gradients, mobile-tight type on a 1440px canvas, or charts without a decision they support. --- ## `product-ui` - **Canvas:** responsive viewports declared in the design lock; verify at least one narrow and one wide target when both are in scope. - **Primitives:** semantic HTML and project-native components. Preserve framework conventions, routes, state, and real content rather than replacing the application with a mock. - **States:** loading, empty, error, success, disabled, focus, and responsive navigation are part of the artifact when the screen owns those behaviors. - **Export:** source code plus reproducible dev/build commands and screenshot paths. - **QA:** run project checks, render the real route, inspect target viewports and important states, and record what could not be exercised. --- ## 11. Booking / Travel / Reservations - **Color:** confident and visual — imagery (places, rooms) leads; accent drives the booking step. Calm so users feel sure about committing money/time. - **Density:** low-medium, step-focused. Dates and availability must be obvious. - **Typography:** clear dates/times, price prominent, friendly labels. - **Motion:** **Float** / **Silk** — smooth, reassuring transitions between steps; `reveal-blur` on imagery. Confidence, not flash. - **Signature patterns:** date/range picker, availability calendar, multi-step booking with progress, map, price summary, confirmation. - **Anti-patterns:** hidden total/fees, unclear current step, jarring motion mid- booking, tiny date controls, anxiety-inducing scarcity spam. - **Brand recipe:** `commerce-operator`; use `native-mobile` for an app-first itinerary. - **Skin material:** custom travel tokens; Arc and Notion remain optional references. --- ## Dashboard / Home / Overview - **Job:** answer "how are things?" in 3 seconds, then let the user drill down. - **Structure:** information pyramid — one hero metric → a small KPI set → supporting list/chart. Vary section types (Rule 14/61): never four identical cards in a row. - **Hierarchy:** density increases as you scroll. Top = 48px hero number; bottom = 13–14px detailed rows. - **Patterns:** HeroCard, KPI grid (mixed: trend / progress / comparison), ChartCard, RankedList, BriefingCarousel for alerts. - **Anti-patterns:** wall of identical KPIs, no clear primary metric, charts with 6 legend colors, everything the same visual weight. - **Mobile:** single column, hero first, horizontal-scroll carousels for KPI sets, `mx-6` single cards / `px-6` grids. --- ## `enterprise-workbench` - **Best fit:** admin, analytics, operations, collaboration, and multi-step B2B work. Strong with `operations-console`. - **Containment:** persistent shell, aligned panels, toolbars, tables, and detail regions. Group by work relationship; use card grids sparingly. - **Geometry:** 0–8px radius, 1px boundaries or tonal layers, minimal floating shadow, 16–24px page rhythm on an explicit grid. - **Type/icons:** neutral UI sans, tabular numbers, compact labels, one functional icon family. - **Controls/collections:** rectangular controls, visible filters, bulk actions, dense rows, comparison tables, and preserved loading geometry. - **Motion/responsive:** fast state changes; panels reflow or collapse by task priority rather than merely shrinking. - **Characteristic move:** one operational focal panel connected directly to an actionable queue or evidence table. - **Reject:** identical KPI cards, oversized mobile typography on desktop, decorative gradients, hidden scope controls, or floating shadows on every panel. - **Lineage:** [IBM Carbon 2x Grid](https://carbondesignsystem.com/elements/2x-grid/overview/), [Microsoft Fluent 2](https://fluent2.microsoft.design/design-principles), [Atlassian foundations](https://atlassian.design/foundations). --- ### signal-coral - Name: Signal coral - Mode: light - Best for: Expressive launches, social products, and consumer discovery - Recipe bias: expressive-brand, native-mobile - 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 - Usage: Let coral own the hook and selected moment. Violet supports spatial or media context; never let both compete as primary actions. - Generated-media anchors: #FFF3EC, #C83D2C, #5B3EC8 - Avoid in generated media: pink-purple gradient wash, rainbow icon chips, coral body text - Re-run deterministic contrast validation after any project override. ## Generated semantic palette override - Key color: #FF6966 - Mode: light - Character: balanced - Harmony: auto - Surface temperature: warm - Semantic roles: background=#FAF2EA · surface=#FFFCF9 · chrome=#EADFD6 · foreground=#0D0B08 · mutedForeground=#544F4A · chromeForeground=#0D0B08 · border=#C4B8AE · primary=#B1282E · primaryForeground=#FFFBF8 · accent=#3154BA · accentForeground=#FFFBF8 · focus=#3154BA · success=#006425 · successForeground=#FFFBF8 · warning=#6E4B00 · warningForeground=#FFFBF8 · danger=#902824 · dangerForeground=#FFFBF8 - Contrast gates: foreground/background=17.74:1 · mutedForeground/background=7.31:1 · foreground/surface=19.23:1 · chromeForeground/chrome=15:1 · primaryForeground/primary=6.35:1 · accentForeground/accent=6.57:1 · successForeground/success=7.16:1 · warningForeground/warning=7.64:1 · dangerForeground/danger=8.11:1 · focus/background=6.1:1 · focus/surface=6.61:1 - Allocation: 60% canvas/surfaces · 30% chrome/type/structure · at most 10% primary and accent emphasis combined. - This override replaces the recipe hex values while preserving its product posture and semantic restrictions. - Components consume semantic roles. Raw ramp values remain reference tokens. --- ### warm-dtc - Coordinate: soft/pill · airy · warm-vivid · spring - Signature: tactile product/image moment - This profile does not permit: competing warm colors or pill-everything - Apply the coordinate coherently across radius, density, typography, palette temperature, elevation, motion, composition, and one signature move. --- ## Project design lock # StyleSeed — Design Lock - App domain: booking - Surface: desktop-app - Surface adapter: product-ui - Page type: dashboard - Output grammar: operations-console - Grammar path: built-in:engine/RULESETS.md - Grammar fallback: operations-console - Reference confidence: n/a - Brand recipe: enterprise-workbench - Palette recipe: signal-coral - Key color: #FF6966 - Palette character: balanced - Palette mode: light - Palette harmony: auto - Surface temperature: warm - Aesthetic profile: warm-dtc - Skin: custom - Primary action: #FF6966 - Font: Pretendard - Radius: soft - Elevation: light=warm tonal grouping + restrained shadow · dark=n/a - Density: comfortable - Motion: Spring restrained - Imagery/data role: slot availability and automation state first; decoration only around the single hook moment - Signature move: one coral "다음 오픈 슬롯" briefing strip above the branch/theme selector - Locked: 2026-08-12 --- # StyleSeed Compact Craft Baseline This is the small, task-independent craft layer used by the Context Compiler. It preserves the highest-leverage rules without injecting the full design handbook into every agent turn. The selected output grammar, adapter, domain, page type, brand recipe, profile, and project lock narrow these defaults. `PRODUCT-PRINCIPLES.md` remains the higher authority. ## Coherence - Choose one coordinated family for radius, elevation, borders, icon style, typography, motion, control heights, and interaction states. Encode each family as semantic tokens and reuse it. - A coherent system may contain multiple component shapes and colors, but every variation must have a repeated role. Local decoration is not a role. - Preserve strengths and already-set project decisions. Do not restyle unrelated surfaces while fixing one screen. ## Hierarchy and composition - Give every screen one dominant user decision or reading promise. Supporting content must recede through scale, position, contrast, density, or disclosure—not random color. - Proximity communicates grouping: space around a group should normally be at least twice the space within it. Repeated sections need deliberate variation in height, density, or composition. - Use real product content and evidence. Placeholder dashboards, fake metrics, stock chat panels, and equal card walls make otherwise clean work look generic. - Keep prose near 50–75 characters per line. Let data surfaces use width, but bound any reading column inside them. ## Spacing and type - Start from `{4, 8, 12, 16, 24, 32, 40, 48, 64, 80, 96}` and use off-scale values only for a documented optical correction. - Default body text to 16px on general surfaces. Dense desktop UI may use 13–14px for metadata, table chrome, timestamps, or identifiers; decisions and explanatory copy stay readable. - Use no more than two type families and one intentional weight ramp. Use tabular numerals for money, tables, timers, and comparable metrics. - Tighten leading as type grows: body about 1.5, headings 1.2–1.35, display 1.0–1.2. ## Components and interaction - Use the lightest separation that works: whitespace, then tone, then hairline, then shadow. Do not combine a visible border and floating shadow without a functional reason. - Buttons, inputs, and selects in one context share a height. Touch surfaces provide at least 44px targets; pointer-first dense desktop controls may be smaller when still operable. - Labels remain visible. Errors name the problem and recovery and never rely on color alone. - Use one icon family, fill mode, and stroke family. Do not use emoji as application chrome. - Loading, empty, error, success, disabled, and permission states preserve layout and provide a useful next action where the surface owns data or mutation. ## Color, accessibility, and motion - Use semantic tokens. Keep one identifiable primary action while allowing stable semantic, categorical, or brand roles required by the selected grammar. - Body text targets WCAG AA contrast; large text and meaningful graphics meet their applicable threshold. Focus is visible, controls have names, and keyboard order follows visual order. - Motion uses one duration/easing family, communicates state or sequence, and never delays the first read or an action. Provide a complete reduced-motion result. - Inspect the real render at the target viewport. Source review cannot certify optical balance, font loading, crop, responsive transformation, or visual states.