@design-intelligence/ghost 0.20.0 → 0.21.0

package/dist/init-payloads/skeleton/signature.shape.md

@@ -0,0 +1,19 @@
+---
+description: "Gather before setting any radius or corner treatment. The shape dial: controls take --radius-control, surfaces take --radius-surface — this dial is unanswered; ask the human or flag the gap, don't freehand it."
+---
+
+This dial is unanswered — ask the human or flag the gap. Do not freehand a
+value and present it as brand-backed.
+
+The relationship is fixed: controls and surfaces carry different radius
+roles, and the two never swap. Buttons and text inputs use
+`--radius-control`; cards and other surfaces use `--radius-surface`. One
+radius for what you click, one for what contains — that split is the part
+worth keeping, whatever the values turn out to be.
+
+The open question: what are this brand's two radii — how round is a control,
+and how round is a surface? When the human answers, restate this node as
+"this brand's current answer is …" and record the values where your
+materials live. If the task can't wait for an answer, proceed with a quiet
+provisional choice, honor the fixed relationship, label the choice
+provisional in your report — and never restate this node as answered.

package/dist/init-payloads/skeleton/signature.temperature.md

@@ -0,0 +1,20 @@
+---
+description: "Gather for any copy and for motion character. The temperature dial: how the brand sounds and how it moves, one shared temperature — this dial is unanswered; ask the human or flag the gap, don't freehand it."
+---
+
+This dial is unanswered — ask the human or flag the gap. Do not freehand a
+value and present it as brand-backed.
+
+The relationship is fixed: voice and motion carry the same temperature. Copy
+states what happened, what is possible, or what the user must decide — it
+does not perform personality — and motion confirms rather than entertains.
+The coupling — words and motion sharing one temperature — is the part worth
+keeping.
+
+The open question: where does this brand sit — how warm or cool is its copy,
+what does its motion feel like, and what character does its one ease carry?
+When the human answers, restate this node as "this brand's current answer
+is …" and record the values where your materials live. If the task can't
+wait for an answer, proceed with a quiet provisional choice, honor the fixed
+relationship, label the choice provisional in your report — and never
+restate this node as answered.

package/dist/init-payloads/skeleton/signature.type.md

@@ -0,0 +1,22 @@
+---
+description: "Gather for any text, and for heroes, landing pages, and editorial moments. The type dial: one voice typeface plus a mono for machine detail, editorial scale kept separate from product text — this dial is unanswered; ask the human or flag the gap, don't freehand it."
+---
+
+This dial is unanswered — ask the human or flag the gap. Do not freehand a
+value and present it as brand-backed.
+
+The relationship is fixed: one typeface is the voice of the interface,
+everywhere, with a mono variant only for code, tool detail, and machine
+output. The heading scale is editorial — it exists for pages composed
+outside the text variants, heroes and editorial moments — and product UI
+never mixes the two vocabularies in one view. A modal title is not a poster.
+The one-voice rule and the editorial/product split are the parts worth
+keeping.
+
+The open question: what typeface is this brand's voice, what mono partners
+it, and what rhythm does the editorial heading scale carry? When the human
+answers, restate this node as "this brand's current answer is …" and record
+the values where your materials live. If the task can't wait for an answer,
+proceed with a quiet provisional choice, honor the fixed relationship, label
+the choice provisional in your report — and never restate this node as
+answered.

package/dist/init-payloads/vessel-light/anti-goal.median.md

@@ -0,0 +1,86 @@
+---
+description: "The model's median defaults this fingerprint refuses — gather for any greenfield visual surface or first-draft copy. Each rule is reject→replace; delete lines your brand legitimately violates."
+---
+
+This is the model's median, not your brand. Each rule is reject→replace.
+Delete every line your brand legitimately violates — `ghost validate` will
+warn on any check reference the deletion orphans — delete the paired flag too.
+
+These are not aesthetic opinions. Where a count is given, it is the measured
+convergence of 300 unsteered generations across three frontier models (the
+antimedian experiment): the defaults a model reaches for when nobody hands it
+a brand. An output showing several of these tells reads as generated,
+whatever else it does right. A deterministic floor rides alongside these
+rules in the paired check — mechanical tells like gradient-filled text,
+emoji as interface icons, em-dash pileups, and aphoristic cadence —
+verified at review, never steered in prose.
+
+### Hover-lift
+Reject hover-lift (`translateY` + growing shadow) as the default interaction
+→ confirm with color and background change at the fingerprint's fast
+duration. (measured: 341)
+
+### Indigo accent
+Reject the indigo/blue/purple default accent (`#4f46e5`, `#2563eb`,
+`#8b5cf6` family; purple/violet hue 260–310) → the fingerprint's declared
+palette; absent one, monochrome plus a single functional accent.
+
+### Dark theme
+Reject unprompted dark theme → the fingerprint's declared surface.
+Dark-to-look-cool and light-to-be-safe are the same retreat from a decision.
+(measured: 271)
+
+### Gradients
+Reject gradient page and section backgrounds and gradient-filled CTAs → flat
+surfaces in semantic roles.
+
+### Side-stripe
+Reject side-stripe borders (a thick colored border on one side of a rounded
+card) — the single most recognizable tell of AI-generated UI → a full
+hairline border, a 4–8% surface tint, or a leading glyph.
+
+### Cream surface
+Reject the cream/sand/beige default surface (warm off-white; token names
+like `--cream`, `--sand`, `--parchment` are the tell) → a true off-white,
+the brand's own hue, or a committed color; warmth via accent and type, not
+the ground.
+
+### Glassmorphism
+Reject glassmorphism (decorative backdrop blur) → flat surfaces with real
+borders and the fingerprint's elevation tiers.
+
+### Chat bubbles
+Reject chat bubbles with initials-circle avatars for assistant turns →
+assistant text plain on the page surface; user turns marked compactly.
+
+### Stock copy
+Reject stock template copy ("Simple, transparent pricing") → headings that
+state what this product specifically does.
+
+### Celebration
+Reject celebration copy and UI (exclamation success, confetti language) →
+quiet factual confirmation.
+
+### Nested cards
+Reject nested cards and everything-in-cards → one surface level per region;
+interior hierarchy from spacing and type; spacing and alignment group
+without card overhead.
+
+### Hero metric
+Reject the hero-metric template (big number + small label + supporting stats
+as default proof) → evidence specific to the product, or nothing. A
+prominent metric showing real user data is fine.
+
+### Every button primary
+Reject every button a primary button → one primary per view; the rest step
+down the fingerprint's emphasis ladder.
+
+### Eyebrow kicker
+Reject an eyebrow kicker on every section → at most one, where the register
+sanctions it; one named kicker is voice, every-section is AI grammar.
+
+### Decorative motion
+Reject decorative looping animation (pulse/float/shimmer) and uniform
+fade-and-rise on every scrolled section → motion as evidence of state
+change; loops only for genuine loading; decoration never compensates for
+weak structure — fix spacing, copy, and hierarchy first.

package/dist/init-payloads/vessel-light/anti-goal.tells.md

@@ -0,0 +1,37 @@
+---
+description: "Failure modes specific to this brand's own signature — gather alongside any signature node you pull."
+---
+
+These are the near-misses of Vessel's own signature: outputs that got close
+enough to cite the brand and still missed it. Each reject names its
+replacement.
+
+Reject rectangular buttons. A rectangular button is not a variant; it is a
+different design system → controls take `--radius-control`, the pill.
+
+Reject swapped radius roles: the surface radius on a control, the pill on a
+surface, or 20px cells in a data table → `--radius-control` on what you
+click, `--radius-surface` on what contains, small radius on data cells.
+
+Reject expression hues on interactive controls, an invented sixth hue, or a
+tinted gray posing as monochrome → the five named expression hues at their
+register's volume, and a true gray spine. An invented hue is not a bolder
+Vessel; it is a different brand.
+
+Reject custom shadows that sit near a tier → the exact tier — card, popover,
+or modal — chosen by interaction importance.
+
+Reject borrowing `--shadow-btn` or `--shadow-kbd` for layout → component
+shadows belong to the primitives that own them; layout elevation comes from
+the three tiers.
+
+Reject editorial display type in product UI, and product type timidity in
+editorial → each register keeps its own vocabulary; a modal title is not a
+poster, and a hero at product scale reads as timid.
+
+Reject borders around assistant text → the assistant speaks as plain text on
+the page surface; use space, tone, and type hierarchy instead.
+
+Fidelity note: pills and fluid clamp display headings are medians Vessel
+deliberately shares — their presence is fidelity, not drift. Convergence is
+not the crime; surrendering the choice is.

package/dist/init-payloads/vessel-light/checks/conversation-grammar.md

@@ -0,0 +1,20 @@
+---
+name: Conversation grammar
+description: Flags conversation UI that breaks plain assistant text, prompt-input structure, primary-action discipline, or collapsed tool output.
+severity: high
+references:
+  - grammar.conversation
+  - grammar.surfaces
+---
+
+Apply this check to diffs that touch AI threads, agent consoles, prompt composers, chat messages, or tool-call rendering.
+
+Flag assistant messages wrapped in bordered, filled, elevated, or card-like surfaces. Assistant turns should sit as plain text on the page surface.
+
+Flag user messages that are not compact muted surfaces aligned to the right when the layout has a conversational thread.
+
+Flag controls placed inside the prompt-input textarea region. The textarea is for writing only; controls belong in the single row below it.
+
+Flag more than one primary button in the input row. Send, stop, retry, attach, model select, and tools must not compete as primary actions.
+
+Flag tool output shown expanded by default. The default state is a one-line labeled summary with status; mono detail appears after expansion.

package/dist/init-payloads/vessel-light/checks/median-tells.md

@@ -0,0 +1,103 @@
+---
+name: Median tells
+description: Flags the measured defaults of unsteered generation and current model-signature tells — hover-lift, default accents, unprompted dark theme, gradient text, frequency tells, and per-model signatures.
+severity: high
+references:
+  - anti-goal.median > Hover-lift
+  - anti-goal.median > Indigo accent
+  - anti-goal.median > Dark theme
+  - anti-goal.median > Gradients
+  - anti-goal.median > Glassmorphism
+  - anti-goal.median > Side-stripe
+  - anti-goal.median > Cream surface
+  - anti-goal.median > Chat bubbles
+  - anti-goal.median > Stock copy
+  - anti-goal.median > Celebration
+  - anti-goal.median > Hero metric
+  - anti-goal.median > Eyebrow kicker
+---
+
+This is Vessel's adaptation of the shared median check; the fidelity carve-outs
+below are the body's own. These flags target the measured convergence patterns
+of unsteered model generation, plus tells specific to individual models. Each
+is mechanically detectable in a diff. Pruning a rule from `anti-goal.median`
+orphans its paired reference here — `ghost validate` warns; delete the flag and
+its reference together.
+
+Flag `transform` with `translateY` inside a `:hover` rule on cards, buttons,
+or list items, especially paired with a shadow increase. Hover confirmation
+in Vessel is color and background change, not lift.
+(`anti-goal.median > Hover-lift`)
+
+Flag accent values in the indigo/blue/purple default family (`#4f46e5`,
+`#6366f1`, `#2563eb`, `#3b82f6`, `#8b5cf6`, and close neighbors) unless the
+diff shows the user asked for them. They are model defaults, not palette
+members. (`anti-goal.median > Indigo accent`)
+
+Flag whole-page dark backgrounds when the ask did not request dark mode.
+Dark surfaces in Vessel are the editorial dark band or an explicit `.dark`
+theme, never an unprompted default. (`anti-goal.median > Dark theme`)
+
+Flag `linear-gradient` or `radial-gradient` as page or section backgrounds,
+and gradient-filled buttons. (`anti-goal.median > Gradients`)
+
+Flag `backdrop-filter: blur` used for glassmorphism cards.
+(`anti-goal.median > Glassmorphism`)
+
+Flag `background-clip: text` (with or without the `-webkit-` prefix) paired
+with a gradient. Emphasis comes from weight or size in a single solid color.
+
+Flag a thick colored border on one side of an element (`border-left` or a
+`border-l-*` utility at 2px or more in a non-neutral color) while the other
+sides stay thin. (`anti-goal.median > Side-stripe`)
+
+Flag warm off-white page backgrounds in the cream/sand/beige band, and token
+names like `--cream`, `--sand`, `--parchment`, `--linen` introduced by the
+diff. (`anti-goal.median > Cream surface`)
+
+Flag assistant messages rendered as bubbles with initials-circle avatars.
+(`anti-goal.median > Chat bubbles`)
+
+Flag emoji used as icons or imagery in interface chrome. Text labels carry
+meaning.
+
+Flag stock template copy in headings: "Simple, transparent pricing",
+"Welcome back", and interchangeable-with-a-competitor phrasing. Recommend
+copy that states what this product specifically does.
+(`anti-goal.median > Stock copy`)
+
+Flag exclamation-marked success copy, confetti language, and celebratory UI
+("You did it!", "Awesome!"). Confirmation is quiet and factual.
+(`anti-goal.median > Celebration`)
+
+Flag the hero-metric template — a big number, small label, and supporting
+stats as default proof — unless the metric shows real user data. Recommend
+evidence specific to the product, or nothing.
+(`anti-goal.median > Hero metric`)
+
+Frequency tells — the crime is repetition, not the move (advisory):
+
+Flag three or more uppercase, tracked eyebrow kickers above section headings
+in one page. One named kicker is voice; a kicker on every section is model
+grammar. (`anti-goal.median > Eyebrow kicker`)
+
+Flag five or more em-dashes in body copy in one view.
+
+Flag three or more instances of the aphoristic rebuttal cadence ("Not X. Y."
+/ "Sentence. No qualifiers.") in one page's copy.
+
+Model-signature tells — skip any block whose model did not produce the diff
+(advisory):
+
+Codex: flag a 1px border paired with a box-shadow of 16px blur or more on
+the same element — pick a solid border or a tight shadow, not both. Flag
+border-radius of 32px or more on cards, sections, or inputs. Flag 1px
+linear-gradient grid or repeating-stripe backgrounds used as decoration.
+
+Gemini: flag `transform` (scale, rotate, translate) on `img` inside a
+`:hover` rule, including group-hover utilities targeting a child image.
+Animate the card's background, border, or shadow instead.
+
+Do not flag pill-shaped controls or fluid clamp display headings — those
+median patterns are deliberately shared by Vessel and their presence is
+fidelity.

package/dist/init-payloads/vessel-light/checks/motion-restraint.md

@@ -0,0 +1,20 @@
+---
+name: Motion restraint
+description: Flags non-token motion, looping decoration, and keyframes that do not explain state change.
+severity: medium
+references:
+  - grammar.motion
+  - signature.temperature
+---
+
+Review changed transitions and animations for vocabulary first.
+
+Flag durations that do not use `--duration-fast`, `--duration-normal`, or `--duration-slow`. A hard-coded millisecond value is a drift even when it matches the token today.
+
+Flag custom easing unless it uses the fingerprint's one ease or a browser default already required by the primitive.
+
+Flag looping animations outside explicit loading states. Loading must be tied to ongoing work, not ambient motion.
+
+Flag decorative keyframes: glow, float, shimmer, bounce, pulse, parallax, or any motion that can be removed without making a state change harder to understand.
+
+Recommend the smallest opacity or transform transition that explains the state change.

package/dist/init-payloads/vessel-light/checks/relationships.md

@@ -0,0 +1,33 @@
+---
+name: Relationship discipline
+description: Flags structural violations of the grammar — emphasis-ladder breaks, sibling margins, decorative borders, nested cards. These rules survive any adaptation.
+severity: high
+references:
+  - grammar.hierarchy
+  - grammar.rhythm
+  - grammar.surfaces
+  - anti-goal.median > Nested cards
+---
+
+These assertions test relationships between token roles, not the values behind
+them. They hold for any brand built on this grammar; an adapted package keeps this check
+unchanged.
+
+Flag more than one primary-variant button per view. Secondary actions step
+down the emphasis ladder: secondary, outline, ghost, or link.
+
+Flag `margin` set on siblings inside a stack in changed CSS or inline styles.
+Rhythm comes from the gap scale; recommend changing the stack gap or splitting
+the stack.
+
+Flag borders, fills, gradients, glass effects, or colored accents used to make
+ordinary structure feel designed. Recommend semantic surfaces, stack spacing,
+text tone, or the existing elevation tier instead.
+
+Flag card-like surfaces nested inside card-like surfaces. One surface level
+per region; interior hierarchy comes from spacing and type, not another
+container.
+
+Flag `box-shadow` values that belong to no declared elevation tier and no
+component-owned shadow. Do not accept a custom shadow because it is visually
+close to a tier — elevation is a closed set, whatever the values are.

package/dist/init-payloads/vessel-light/checks/values.md

@@ -0,0 +1,51 @@
+---
+name: Value discipline
+description: Flags off-signature values — non-pill controls, off-palette hues, raw color literals, expression over budget. Adapting the dials rewrites this check alongside the signature nodes.
+severity: high
+references:
+  - signature.shape
+  - signature.palette
+  - grammar.color-roles
+  - register.data-density
+  - register.editorial
+  - register.email
+---
+
+These assertions test Vessel's current answers to the signature dials. A
+adaptation that changes the dials rewrites this check with them; the paired
+relationship check stays.
+
+Review changed HTML and CSS by view, not just by file. Classify the register
+of each changed view first: table layout, `bgcolor`, or a 600px wrapper means
+email; display-scale headings, `--section-padding-vertical`, or
+`--surface-dark-*` means editorial; compressed smallest-gap-step layouts with
+mono numerals means data-density; otherwise product.
+
+Flag buttons or text inputs that are not pill-radius (`--radius-control`).
+A rectangular control is a token violation, not a style choice.
+
+Flag surfaces that carry a radius other than `--radius-surface`, and radius
+roles swapped across the boundary: control radius on a surface, surface
+radius on a control.
+
+Count distinct non-gray colors visible in each view, then judge against that
+register's expression budget: product views get one functional accent, with
+expression hues permitted only inside chart or visualization markup; data
+consoles get one status hue family with the same chart carve-out; email gets
+one expressive moment in one hue; editorial pages get at most two expression
+hues. Flag anything over budget, and flag expression hues used
+atmospherically outside their register. Status colors count toward the total
+unless the view compares two or more distinct statuses side by side.
+
+Flag any color that is neither a gray, a status token, nor one of the five
+expression hues (`--expression-1` through `--expression-5`, or their hex
+values in email). Invented hues are drift in every register.
+
+Flag expression hues on buttons, inputs, or links in every register. Controls
+stay monochrome; no budget covers them.
+
+Flag raw hex, rgb, hsl, or named color values in changed CSS or inline styles
+when a Vessel token could express the same role. The authoring vocabulary is
+semantic tokens, not literal color. Exception: email files — hardcoded values
+transcribed from tokens are the contract there; flag only values that
+correspond to no token and no expression hue.

package/dist/init-payloads/vessel-light/glossary.md

@@ -0,0 +1,45 @@
+---
+kinds:
+  - name: grammar
+  - name: signature
+  - name: register
+  - name: anti-goal
+    posture: guard
+---
+
+# grammar
+
+The brand's decision logic: closed sets, role vocabularies, and assembly
+rules, stated in token roles and never in literal values. Grammar survives an
+adaptation unchanged — adapt the package, swap every value, and these nodes still
+hold. Gather grammar before inventing structure.
+
+# signature
+
+The dials: the choices that make this brand this brand, each stated as a
+current answer that stands until you replace it. Signature nodes name real
+values because they are the values — on adaptation, edit the token roles in
+`materials/tokens.css` and restate the node. Gather signature before setting
+any value a dial governs.
+
+# register
+
+A condition-scoped contract: a situation — data-dense consoles, editorial
+pages, transactional email — where parts of the default rules invert. Each
+register names its condition first. Truths from the wrong register are
+poison, not context; gather a register only when its condition matches the
+task.
+
+# anti-goal
+
+What this package refuses, each reject paired with its replacement.
+`anti-goal.median` is the model's floor, not the brand's taste;
+`anti-goal.tells` is the near-miss map of this brand's own signature. Gather
+anti-goals before styling anything greenfield.
+
+---
+
+To adapt this package to another brand, follow the `adapting-a-starter`
+recipe in the ghost skill bundle. In short: new manifest id, prune the
+median rules your brand legitimately violates, answer each signature node,
+edit `materials/tokens.css`, regenerate the refs, rewrite the tells.

package/dist/init-payloads/vessel-light/grammar.color-roles.md

@@ -0,0 +1,30 @@
+---
+description: "Semantic color roles and the rules that govern them — gather before choosing any color; roles not raw values, status is meaning, expression is register-gated and never on controls."
+materials:
+  - materials/tokens.css
+  - "**/*.css"
+  - "**/*.html"
+---
+
+The token file is the source of truth. An agent may combine tokens, but it
+may not author around them. Raw color values are implementation detail, never
+product language.
+
+Author with semantic roles: `background`, `foreground`, `card`, `popover`,
+`primary`, `secondary`, `muted`, `accent`, `border`, `input`, `ring`, and the
+status roles. If a container needs a color, it first needs a role.
+
+The status roles — destructive, success, warning, info — exist only when
+meaning demands them. Destructive means destructive or error. Success means
+success. Warning means warning. Info means information. None of them are
+brand accents, and they never moonlight as atmosphere, in any register.
+
+One view should not perform a color palette. If a status color is present,
+let the rest of the view stay on the base roles. Richness beyond this is
+register-gated: a closed expression set (`--expression-*`) exists, but its
+size, members, and volume ladder are a brand answer — see the palette
+signature — and each register caps how loud they may be.
+
+The constant that holds across every register: expression never touches what
+you click. Buttons, inputs, and links stay on the base roles everywhere. A
+colored control is a different design system.

package/dist/init-payloads/vessel-light/grammar.conversation.md

@@ -0,0 +1,30 @@
+---
+description: "Conversation grammar — plain assistant text, compact user surfaces, collapsed tool calls, one structured prompt input; gather for any AI thread, agent console, review assistant, or prompt composer."
+materials:
+  - materials/ref/composition.conversation.html
+  - "**/*.html"
+---
+
+Conversation UI is not chat cosplay. The assistant speaks on the page surface
+as plain text: no bubble, no border, no fill.
+
+User turns are compact muted surfaces aligned right. They mark authorship
+without turning the thread into alternating balloons.
+
+Assistant hierarchy comes from prose, spacing, and type. Wrapping assistant
+messages in cards makes the system look defensive and wastes density.
+
+Tool calls are operational evidence. Collapse them to a labeled one-line
+summary with status. Expand only when the user asks for detail, then show
+mono content inside the disclosed area.
+
+The prompt input is one bordered surface. The textarea region stays empty of
+controls so writing remains the focus. Attachments, model choices, secondary
+tools, and send live in a single row below it.
+
+There is one primary send action. Stop and send are mutually exclusive states
+of the same action area, not two competing primary buttons.
+
+Use the conversation reference when building any AI thread, agent console,
+review assistant, or prompt composer. It carries the grammar that agents most
+often get wrong.

package/dist/init-payloads/vessel-light/grammar.hierarchy.md

@@ -0,0 +1,48 @@
+---
+description: "The closed hierarchy vocabulary — six text variants, seven tones, a five-rung control emphasis ladder, one primary per view — gather for any view that contains text or actions."
+materials:
+  - materials/primitives.css
+  - materials/ref/composition.form.html
+  - "**/*.html"
+  - "**/*.css"
+---
+
+Hierarchy is a closed vocabulary, not a size slider. Every piece of text and
+every control picks from a named set; anything outside the set is a broken
+primitive, not a variant.
+
+The text variants are exactly six: display, headline, title, body, label,
+mono. Variant names are jobs, not decoration. Display leads a rare editorial
+moment. Headline names a section. Title anchors a card, dialog, or compact
+region. Body carries reading. Label names structure — category tags, field
+labels, bylines, metadata, compact status. Mono carries code and machine
+detail. Do not fake hierarchy with arbitrary font sizes; choose the tier that
+matches the job, then use tone, weight, and spacing for the rest.
+
+The tones are exactly seven: default, muted, inverse, success, warning, info,
+destructive. Tone is part of the message. Default is the main reading plane.
+Muted carries secondary information. Inverse is for dark or primary surfaces.
+The four status tones appear only when the words have that state meaning.
+Hierarchy starts with tone and weight before size — a secondary note usually
+wants muted body or label, not a smaller custom font. If the prose needs
+emphasis, improve the sentence before adding a style.
+
+The control emphasis ladder is exactly five rungs: primary, secondary,
+outline, ghost, link. One primary action per view is the rule; everything
+else steps down the ladder. Primary is for the action the screen exists to
+complete — if two buttons both look primary, the hierarchy failed.
+Destructive is a meaning, not a rung: it is rare, it names the destructive
+act directly, and it is never borrowed for urgency, emphasis, or brand heat.
+
+Fields are quiet until they are active: hairline border, muted placeholder,
+clear label, and a focused ring when the user engages. The focus ring is
+guidance, not decoration. Errors state facts next to the field that caused
+them — do not hide field errors in modals, toasts, or generic banners when
+the user needs to fix one input.
+
+Balanced text is for headings and compact statements. Do not balance long
+body copy into jagged reading.
+
+The form reference shows the intended decision order: stacked labels and
+fields, compact helper text, one submit, secondary escape. Copy the decision
+order before adjusting surface detail.

package/dist/init-payloads/vessel-light/grammar.motion.md

@@ -0,0 +1,27 @@
+---
+description: "Motion doctrine — motion is evidence of state change, never decoration; a closed vocabulary of three duration roles and one ease; gather for any transition, animation, or hover treatment."
+materials:
+  - materials/tokens.css
+  - "**/*.css"
+  - "**/*.html"
+---
+
+Motion is evidence of a state change. It confirms hover, press, reveal,
+collapse, entrance, exit, and spatial movement. It does not entertain.
+
+The entire vocabulary is three duration roles and one ease. Fast is for hover
+and press. Normal is for reveals, fades, and small state changes. Slow is
+reserved for spatial transitions where the user needs to understand movement.
+Do not introduce novelty easings because a surface feels static; the ease's
+character is a brand answer — see the temperature signature.
+
+Nothing loops except explicit loading states. A spinner may continue because
+work continues. Decorative pulsing, floating, glowing, and attention-seeking
+keyframes are off-language.
+
+Prefer opacity and small transform changes. If removing an animation does not
+reduce comprehension, the animation was decoration.
+
+Condition: marketing and editorial surfaces may stage entrances — scroll reveals and
+section transitions are part of editorial rhythm, still built from the three
+durations and the one ease. In product UI the same staging is decoration.

package/dist/init-payloads/vessel-light/grammar.rhythm.md

@@ -0,0 +1,27 @@
+---
+description: "Layout rhythm — all layout is stacks with a closed gap step set; gather before laying anything out; never ad-hoc sibling margins."
+materials:
+  - materials/primitives.css
+  - "**/*.html"
+  - "**/*.css"
+---
+
+All layout is stacks. Rhythm comes from relationships between siblings, not
+from isolated margins pasted onto whichever element was last touched.
+
+The gap steps are exactly five: `--gap-xs`, `--gap-sm`, `--gap-md`,
+`--gap-lg`, `--gap-xl`. Choose the gap that states the relationship. Do not
+tune by single pixels to make a screenshot pass.
+
+The default is column, medium gap, stretch alignment, start justification.
+That is the ordinary reading rhythm.
+
+Columns are for almost everything: forms, cards, message lists, modal bodies,
+settings, empty states, and page sections. A column lets the user scan.
+
+Rows are conditional. Use them for controls, metadata lines, compact status,
+and paired label/value moments. If a row starts wrapping awkwardly, it
+probably wanted to be a column.
+
+Ad-hoc margins between siblings are forbidden because they hide the rhythm.
+When spacing feels wrong, change the stack gap or split the stack.