@design-intelligence/ghost 0.29.0 → 0.31.0

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

@@ -1,56 +0,0 @@
----
-context: Any view containing text or actions.
-materials:
-  - materials/primitives.css
-  - materials/examples/composition.form.html
----
-
-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. At most one primary action per view is the rule
-(`--primary-budget: 1`); 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. And some views honestly earn none: a steady
-status view or an open comparison has no action the screen exists to
-complete, and promoting one anyway puts the system's thumb on the scale.
-Zero is a valid spend.
-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.
-
-Figures that will be compared or scanned — amounts, counts, dates in
-columns, any metric — set in tabular numerals (`--numeric-tabular`), with
-the unit tight to the number. Proportional figures in a data column wobble,
-and a wobbling column reads as sloppy arithmetic. Mono already carries this
-for machine detail; the rule extends to any numeric data in product UI.
-
-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.job.md

@@ -1,54 +0,0 @@
----
-context: Any new view before its structure or register is chosen.
-materials:
-  - materials/examples/composition.form.html
-  - materials/examples/composition.table.html
-  - materials/examples/composition.editorial.html
-  - materials/examples/composition.overlay.html
-  - materials/examples/composition.conversation.html
-  - materials/examples/email.html
----
-
-Before any structure exists, name what the reader does next with the view.
-The topic never picks the shape; the reader's job does. A billing question
-is not "a billing page" — it is a form to fill, a table to scan, a decision
-to confirm, or a thread to continue, and each of those is a different
-composition. A view built for the wrong job does not merely look off; it
-misleads.
-
-The jobs and where they route:
-
-- **Fill something in** — settings, signup, any submit-and-done task → the
-  form example. Stacked labels and fields, one submit, secondary escape.
-- **Scan and compare records** — lists, audits, anything with rows and
-  figures → the table example, in the data-density register.
-- **Read a narrative** — a landing page, an announcement, a story → the
-  editorial example, in the editorial register.
-- **Stop and decide** — a confirmation, a destructive act, a choice that
-  interrupts the task → the overlay example. The decision is the view.
-- **Converse with the system** — an AI thread, an agent console, a prompt
-  composer → the conversation example.
-- **Be notified elsewhere** — receipts, alerts, anything that lands in an
-  inbox → the email example, in the email register.
-
-Read the request's verbs, not its nouns: "edit / set up / submit" routes to
-form; "compare / list / review the records" to table; "announce / tell the
-story" to editorial; "confirm / are you sure" to overlay; "ask / draft with
-me" to conversation. When two jobs fold into one request, build for the job
-the reader performs on this view, now — the other job is the next view. When
-a job fits none of these, compose from the grammar and say so; do not force
-the nearest example.
-
-Three shapes lie about the job, and we refuse them everywhere:
-
-- A view whose content is an artifact the reader will review — a draft, a
-  filled form, a generated plan — leads with the artifact, never with an
-  announcement headline. "Here's your draft" in display type demotes the
-  actual deliverable; the artifact sitting there with its actions is the
-  statement that it is ready.
-- A view reporting a live or ongoing state carries its freshness — "updated
-  2 min ago" — in quiet metadata. Presenting a moving value as a settled
-  fact is a small lie the reader eventually catches.
-- A view where the decision belongs to the reader presents the material and
-  withholds the verdict. Recommendation framing on a choice the system
-  cannot honestly make is manufactured confidence, and it reads that way.

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

@@ -1,25 +0,0 @@
----
-context: Any transition, animation, or hover treatment.
-materials:
-  - materials/tokens.css
----
-
-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

@@ -1,25 +0,0 @@
----
-context: Laying out any view.
-materials:
-  - materials/primitives.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.

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

@@ -1,33 +0,0 @@
----
-context: Any card, popover, modal, dialog, scrim, or bordered container.
-materials:
-  - materials/primitives.css
-  - materials/examples/composition.overlay.html
----
-
-Surface is the only way an element gets a background, border, radius, or
-shadow. If a container needs visual treatment, it first needs a surface role.
-
-The vocabulary is closed: role, padding, radius, border, and elevation. These
-axes create enough range for page flow, cards, popovers, muted blocks,
-accents, and dark moments without inventing one-off boxes.
-
-The default surface is flat: no border, no shadow. We do not outline
-everything to prove layout exists.
-
-The elevation tiers are exactly three: card, popover, modal. Elevation
-implies hierarchy — a card sits in the document flow, a popover floats above
-the flow, a modal interrupts the task. Pick the tier that matches the
-interaction; never write a custom shadow because the composition feels flat,
-and never pair a low tier with an interrupting role or give a routine card
-modal gravity. Component shadows belong to the primitives that own them;
-never borrow them for layout.
-
-Borders are structural, especially for inputs and overlays. They are not
-decorative frames around ordinary text — reject borders as decoration,
-especially around assistant text, and use space, tone, and type hierarchy
-instead.
-
-The overlay reference shows the interrupting end of the system: background
-scrim, modal radius, modal shadow, compact header, clear footer. Copy its
-hierarchy when a user must stop and decide.

package/dist/init-payloads/vessel-light/register.data-density.md

@@ -1,39 +0,0 @@
----
-context: Tables, dashboards, logs, monitoring, or other data-dense consoles.
-materials:
-  - materials/examples/composition.table.html
-  - materials/primitives.css
----
-
-Condition: this node applies to data-dense surfaces — tables, dashboards,
-transaction logs, and admin consoles.
-
-Data density inverts the settings-page rhythm. Operators need scan speed
-before they need breathing room.
-
-Use the two smallest gap steps (`--gap-xs`, `--gap-sm`) where forms use the
-medium step. Tight adjacency is meaning when rows compare against rows.
-
-Numerals are mono so columns align. A ragged amount column is a broken
-instrument.
-
-Hierarchy is muted-first. Data is the default plane, labels are muted, and
-emphasis is rare enough to stay useful.
-
-Data surfaces take the small radius. A surface-radius table cell is costume —
-the signature radius (see signature.shape) belongs on cards, not cells.
-
-Status is a text label with at most one functional color family per view.
-
-Charts inside a console follow the product carve-out from the palette
-signature: expression hues live inside the plot area only. Outside the plot,
-the one-status-hue cap holds — chart color never leaks into rows, badges, or
-headers. More status color turns monitoring into confetti.
-
-No zebra striping. Hairline borders carry rows with less noise and more
-trust.
-
-Hover confirmation uses the fast duration. It should acknowledge targeting,
-not animate the table.
-
-Generous whitespace is drift here. Wasted density makes operators scroll.

package/dist/init-payloads/vessel-light/register.editorial.md

@@ -1,41 +0,0 @@
----
-context: Heroes, marketing pages, pull quotes, or full-bleed dark moments.
-materials:
-  - materials/examples/composition.editorial.html
-  - materials/tokens.css
----
-
-Condition: this node applies to marketing, landing, and editorial surfaces —
-never to product UI.
-
-Editorial surfaces invert the product type rules. Display scale is not an
-indulgence here; it is the job.
-
-Use the `--heading-display-*` tokens — size, line height, and weight — when
-the words are the composition. The display tier belongs to this register (see
-signature.type for the scale's character).
-
-Section rhythm uses `--section-padding-vertical`, not a product stack
-stretched until it looks important.
-
-The sanctioned dramatic moment is the full-bleed dark section. Use the
-`--surface-dark-*` family and let contrast carry the scene.
-
-Pull quotes are visual punctuation for longform. They interrupt reading with
-judgment, not decoration.
-
-The tracked uppercase label is the kicker grammar. It gives the page a hard
-editorial edge before the headline lands.
-
-Monochrome remains the spine, but editorial is the loud end of the expression
-ladder (see signature.palette): up to two expression hues per page as
-atmosphere — a tinted dark section, a colored pull-quote accent, a duotone
-image moment. Commit to few colors at scale; variety is where expression
-collapses into decoration.
-
-There is one primary action per page, and it keeps the control radius from
-signature.shape. Editorial confidence does not excuse competing calls to
-action.
-
-A hero built at product scale reads as timid. Timidity is drift here, exactly
-as spectacle is drift in product UI.

package/dist/init-payloads/vessel-light/register.email.md

@@ -1,43 +0,0 @@
----
-context: Transactional email only.
-materials:
-  - materials/examples/email.html
----
-
-Condition: this node applies only to email. In any other medium, everything
-below is a violation.
-
-Email clients do not honor the web contract. Custom properties, external
-stylesheets, flex layout, and webfonts are unreliable materials here.
-
-Email inverts the material contract deliberately. Transcribe token values by
-hand instead of referencing tokens — every hex below is a transcription of
-`materials/tokens.css`, which stays the single source; if a token changes,
-re-transcribe.
-
-Use `#1a1a1a` (`--color-gray-900`, foreground) for text, `#999999`
-(`--color-gray-500`, muted) for muted text, and `#e8e8e8` (`--color-gray-200`,
-border) for borders when the email needs the Vessel palette.
-
-Keep the surface radius on cards and the control radius on buttons (see
-signature.shape). The values survive even when the token names cannot travel.
-
-Build with table layout, a 600px wrapper, predictable cells, and bulletproof
-buttons. Email fidelity is made from boring structure.
-
-HK Grotesk falls back to the system stack. The voice must survive without the
-font file.
-
-The soul survives the body swap: monochrome spine, quiet factual copy, one
-primary action, no celebration.
-
-Email gets exactly one expressive moment: a header band or the figure that
-matters, in one expression hue, transcribed by hand like every value here —
-amber is `#f6b44a` (`--expression-1`). One moment, one hue. A receipt is
-allowed one degree of warmth; it is not allowed a palette.
-
-Do not add further color to compensate for email constraints. Constraint is
-not permission to perform.
-
-Hardcoding hex here is fidelity, not drift. The check exemption is the
-condition itself.

package/dist/init-payloads/vessel-light/signature.palette.md

@@ -1,45 +0,0 @@
----
-context: Color beyond the base roles, in any register.
-materials:
-  - materials/tokens.css
----
-
-This is Vessel's answer to palette — it stands until you replace it.
-
-The relationship is fixed: one brand at different volumes. A monochrome spine
-is the default atmosphere in every medium — calm, legible, and resistant to
-novelty — and a closed expression set supplies the atmosphere, with volume
-set by register, never by taste.
-
-Vessel's current answer: the base palette is monochrome gray, and the
-expression palette is five named hues and only these — amber
-(`--expression-1`), periwinkle (`--expression-2`), clay (`--expression-3`),
-orchid (`--expression-4`), sage (`--expression-5`). Expressive color outside
-this set is not expression; it is another brand. An invented hue is not a
-bolder Vessel; it is a different brand.
-
-The volume ladder, by register:
-
-Product UI: expression lives only in data visualization. A chart may use the
-hues; the interface around it stays monochrome.
-
-Data-dense consoles: one hue family may mark status. Nothing atmospheric.
-Charts inside a console keep the product carve-out — hues stay inside the
-plot area and never leak into rows, badges, or headers.
-
-Email: exactly one expressive moment per message — a header band or the
-figure that matters. One hue, quiet everywhere else.
-
-Editorial: expression is sanctioned atmosphere — a tinted dark section, a
-colored pull-quote accent, a duotone moment. Never more than two hues per
-page. Loudness comes from commitment to few colors at scale, not variety.
-
-Two constants that outrank the ladder: expression never touches what you
-click — buttons, inputs, and links stay monochrome in every register — and
-the status roles are not expression; they keep their meanings everywhere and
-never moonlight as atmosphere.
-
-To adapt: edit the `--expression-*` values (and the gray ramp, if the spine
-changes) in `materials/tokens.css` and restate this node's current answer.
-The ladder — a quiet spine, a closed hue set, register-gated volume — is the
-part worth keeping.

package/dist/init-payloads/vessel-light/signature.shape.md

@@ -1,27 +0,0 @@
----
-context: Choosing or implementing any radius or corner treatment.
-materials:
-  - materials/tokens.css
-  - materials/primitives.css
----
-
-This is Vessel's answer to shape — it stands until you replace it.
-
-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`.
-
-Vessel's current answer: controls are pills (`--radius-control: 999px`) and
-surfaces take the 20px signature radius (`--radius-surface: 20px`). The pill
-is Vessel's most visible control signature; a rectangular button is not a
-variant, it is a different design system. Never give a button the surface
-radius — a rectangular button is the fastest tell that the output is not
-Vessel.
-
-20px is a considered position: rounder than default shadcn, but not bubbly.
-Use the radius system as restraint, not as decoration.
-
-To adapt: edit the `--radius-control` and `--radius-surface` values in
-`materials/tokens.css` and restate this node's current answer. The
-role split — one radius for what you click, one for what contains — is the
-part worth keeping.

package/dist/init-payloads/vessel-light/signature.temperature.md

@@ -1,44 +0,0 @@
----
-context: Writing any copy or choosing the character of motion.
-materials:
-  - materials/tokens.css
----
-
-This is Vessel's answer to temperature — it stands until you replace it.
-
-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.
-
-Vessel's current answer in words: product UI is the default register —
-factual, quiet, sentence case, and free of applause. No exclamation marks;
-celebration is not reassurance. Confirmations are quiet: "Changes saved",
-never "Awesome!" The system should sound reliable, not excited by basic
-competence. Errors name the problem and the fix in the place where the user
-can act; a vague failure banner is evasion. Buttons name the act — "Delete
-account", "Save changes", "Invite member", not "Do it" or "Let's go".
-Destructive copy is direct because the risk is direct; softening the verb
-makes the interface less honest. Vessel never celebrates at the user. Trust
-comes from precision, restraint, and naming the truth plainly.
-
-The voice is a mechanical edit, not a mood — apply it as transformations:
-"Sorry, nothing here yet!" → "Nothing yet". "Awesome, your changes have been
-saved!" → "Changes saved". "Oops! Something went wrong" → "Payment failed —
-card expired". "You might want to consider updating your billing info" →
-"Update your billing info". Strip the apology, the applause, and the hedge;
-keep the fact and the fix.
-
-Vessel's current answer in motion: three durations — `--duration-fast`,
-`--duration-normal`, `--duration-slow` — and one ease, `--ease-spring`, which
-should feel resolved without feeling elastic. Hover confirms with color and
-background shifts at the fast duration, not levitation.
-
-Condition: editorial surfaces switch register. Short declarative confident
-fragments are correct in heroes and section headings. That same editorial
-confidence is wrong in a settings form — product copy serves the task before
-it serves the voice. Email copy uses the product voice: factual, not
-campaign-like.
-
-To adapt: rewrite this node's current answers in your brand's voice and edit
-the duration and ease values in `materials/tokens.css`. The coupling — words
-and motion sharing one temperature — is the part worth keeping.

package/dist/skill-bundle/references/brief.md

@@ -1,50 +0,0 @@
----
-name: brief
-description: Build a compact pre-generation packet from pulled ghost guidance.
----
-
-# Recipe: Brief Work From ghost Package
-
-A brief is an ephemeral steering packet for the generating pass. It is not a new
-schema and is never written back into `.ghost/`.
-
-1. Run `ghost gather <ask> --format json` and select against contexts.
-2. The cover is already in context and outside selection. Pull every applicable
-   node with `ghost pull <id> [<id>…]`; skip nodes whose stated situation does
-   not apply. Topic overlap alone is not applicability.
-3. Note gather payload labels where present: `materials`, substantial fenced
-   examples, or a `## Skeleton`. If there is no concrete material for this
-   surface, the readiness ceiling is **Yellow**.
-4. If no node applies, name the package's silence, follow the cover silence
-   posture, and keep provisional reasoning separate from ghost-backed claims.
-
-## The packet: five sections only
-
-Return this shape:
-
-```markdown
-## Grounded in
-- `node.id` — why it was selected
-
-## Non-negotiables
-- ≤5 lines, each cited to a node id
-
-## Materials inline
-- concrete locators, inlined snippets, inspect-pointers, and what to view/use
-
-## Skeleton
-- matching pulled Skeleton, or "none pulled"
-
-## Silent / provisional
-- what ghost does not cover and what local evidence carries
-```
-
-Rules:
-
-- Do not add sections for every kind. Sections dilute instruction weight.
-- Treat `ghost pull` ordering as packet structure: stance first, concrete-material
-  nodes next, prose rules, Skeletons dead last.
-- If a pulled Skeleton matches the surface, begin the artifact from it verbatim
-  before filling.
-- Anti-goals are review-critical: state the positive replacement, not just the
-  rejected pattern.

package/dist/skill-bundle/references/recall.md

@@ -1,36 +0,0 @@
----
-name: recall
-description: Gather and pull the applicable ghost brand guidance for a task.
----
-
-# Recipe: Recall ghost Package
-
-1. Run `ghost gather <ask>` for the actual task. The cover is inlined by gather;
-   do not pull it separately. Read the coverage line: all-prose packages are
-   weak steering.
-2. Select against `context`; ghost never selects for you. Pull every node
-   whose stated situation applies and whose guidance, material, structure, or
-   refusal governs the work. Skip inapplicable nodes. Topic overlap alone is not
-   applicability.
-3. Run `ghost pull <id> [<id>…]`. Prefer `pull` over reading files directly: it
-   orders the packet for steering, inlines small local materials, emits
-   inspect-pointers for binary materials, extracts Skeletons last, and logs the
-   pull to `.ghost/.events`.
-
-## Read order = pull emission order
-
-`ghost pull` emits selected nodes in steering order:
-
-1. Cover first, when explicitly selected; normally it is already inlined by
-   gather and should not be pulled separately.
-2. Concrete-material nodes: `materials`, substantial fenced examples, or
-   `## Skeleton` sections, with materials inlined or pointed to inspect.
-3. Prose-only rules: principles, conditions, decisions, and other rules without
-   concrete material.
-4. Skeleton fences dead last: if one matches the surface, start from that
-   structure verbatim.
-
-Return the selected guidance with node ids, how each applies, and where the
-package is silent. If no node applies, say so and do not invent ghost-backed
-guidance. If silence is safe, proceed provisionally and label it;
-if it is brand-defining or high-risk, ask or author a node first.

package/dist/skill-bundle/references/self-check.md

@@ -1,64 +0,0 @@
----
-name: self-check
-description: A pre-generation check that reveals whether you have actually gathered and reasoned about the brand guidance before you build.
----
-
-# Recipe: Self-Check Before Generating
-
-Before writing UI, copy, email, or any output, check whether you are grounded in
-the guidance or about to fall back on generic instincts. These questions test
-your **grounding and provenance**, not the package's contents, so they hold
-for any ghost package, however sparse, whatever the medium, whoever authored it.
-
-Ask yourself:
-
-1. **What did you gather?** Which ghost nodes did you pull for this task (from
-   `ghost gather`), and can you cite them by id? If you have not gathered, you
-   are not grounded. Gather first.
-2. **What is ghost-backed vs. provisional?** For each claim you are about to
-   encode, is it backed by a gathered node (cite the id), or is it your own
-   provisional local reasoning? You must be able to label every claim as one or
-   the other.
-3. **Do the conditions apply?** For each conditional node you pulled, does its
-   stated situation actually hold for this task? For each kind with conditional
-   or scoped meaning **per the glossary**, apply it only when its stated
-   situation holds; do not apply it where it does not, and do not ignore it
-   where it does.
-4. **Where is the package silent?** What does the package not cover for
-   your task, and what will carry the reasoning in those gaps? Naming the silence
-   is part of being grounded; pretending coverage you do not have is not.
-
-## Steering readiness
-
-Before generating, can you cite:
-
-- the governing principle, stance, or tradeoff?
-- the concrete materials, if exactness matters?
-- the applicable pattern, if structure matters?
-- the anti-goal that blocks the generic version?
-- the hard invariants?
-- the conditions that apply or do not apply?
-- any decision trace for ambiguous tradeoffs?
-- where the package is silent?
-
-Classify readiness:
-
-- **Green:** enough ghost-backed guidance and concrete material for this surface
-  to generate.
-- **Yellow:** generation is safe, but some reasoning must be labeled
-  provisional; if there is no concrete material for this surface, readiness is
-  at most Yellow.
-- **Red:** missing brand-defining, high-risk, or irreversible guidance; ask a
-  human or author a node first.
-
-When you cannot answer the grounding questions:
-
-1. Run `ghost gather <ask>` to emit the menu for the actual task, then match the
-   work to nodes by their contexts.
-2. Read the selected nodes' bodies and re-ask the questions, citing node ids.
-
-A genuinely silent package is an expected state, not a blocker. When it does
-not cover the task, say so plainly and proceed with provisional local reasoning
-when safe; label it non-ghost-backed. If the package's cover declares a stricter
-silence posture, honor it over this default. Ask a human before
-high-risk or brand-defining choices.