@design-intelligence/ghost 0.21.0 → 0.22.0

package/dist/skill-bundle/references/steering-audit.md

@@ -1,6 +1,6 @@
 ---
 name: steering-audit
-description: Audit a Ghost fingerprint for concrete steering coverage and guard routing.
+description: Audit a Ghost fingerprint for concrete steering coverage.
 ---
 
 # Recipe: Audit Steering Coverage
@@ -19,16 +19,13 @@ ghost pulse --format json
 
 If checks are installed and a diff exists, run `ghost review` too.
 
-## Headline the audit with concreteness + guards
+## Headline the audit with concreteness
 
 Report first:
 
 - **Concreteness coverage:** total nodes, concrete-material nodes, prose-only
   nodes. Concrete means non-empty `materials`, a fenced code block of at least 3
   lines, or a `## Skeleton` section.
-- **Guard routing:** how many guard nodes exist, whether they stay in default
-  gather, and whether `ghost review` can auto-offer matched guards via
-  materials.
 - **Pulse by concreteness:** concrete exposure/pull rate vs prose-only
   exposure/pull rate. This is the tuning instrument: if concrete nodes are not
   pulled, descriptions or task selection are failing.
@@ -37,16 +34,16 @@ Report first:
 
 | Row | Status | Evidence | Next move |
 | --- | --- | --- | --- |
-| Retrieval | strong / weak | descriptions, ids, `index` | sharpen descriptions or mention cold nodes in `index` |
+| Retrieval | strong / weak | descriptions, ids, cover | sharpen descriptions or move universal truth to the cover |
 | Concreteness | strong / thin | materials, fenced examples, Skeletons | add concrete locators, exemplars, or opening structures |
-| Guards | routed / missing / vague | `posture: guard`, review packet | write not-X-instead-Y guards and material locators |
-| Consistency | clean / conflicting | concrete bodies vs rules/guards | update stale examples; examples average with rules |
-| Stance | present / missing | `index`, `principle.*` | write forced-choice principles |
+| Anti-goals | present / missing / vague | `anti-goal.*`, review packet | write not-X-instead-Y replacements and material locators |
+| Consistency | clean / conflicting | concrete bodies vs rules | update stale examples; examples average with rules |
+| Stance | present / missing | cover, `principle.*` | write forced-choice principles |
 | Materials | present / missing | `materials`, inspect-pointers | point at real assets/components/tokens |
 | Exemplars | annotated / unannotated / missing | fenced samples, screenshots | say what to copy and what is incidental |
 | Patterns | bound-open / loose / missing | `pattern.*`, Skeletons | state applies / bound / open and add a Skeleton when opening structure matters |
 | Checks | covered / partial / missing | checks/, probes, review packet | add checks/probes for high-risk invariants |
-| Silence posture | defined / missing | `index` | say when to proceed provisionally or ask |
+| Silence posture | defined / missing | cover | say when to proceed provisionally or ask |
 
 ## Task-level readiness
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@design-intelligence/ghost",
-  "version": "0.21.0",
+  "version": "0.22.0",
   "description": "Ghost CLI for the brand fingerprint: a portable steering packet of prose truths your agent reads before it builds, with advisory review after",
   "license": "Apache-2.0",
   "author": "Block, Inc.",

package/dist/init-payloads/skeleton/grammar.color-roles.md

@@ -1,26 +0,0 @@
----
-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."
----
-
-The token roles are the source of truth. An agent may combine roles, 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; its size
-and members are a dial — 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/skeleton/grammar.conversation.md

@@ -1,23 +0,0 @@
----
-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."
----
-
-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.

package/dist/init-payloads/skeleton/grammar.hierarchy.md

@@ -1,39 +0,0 @@
----
-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."
----
-
-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.

package/dist/init-payloads/skeleton/grammar.motion.md

@@ -1,24 +0,0 @@
----
-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."
----
-
-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/skeleton/grammar.rhythm.md

@@ -1,23 +0,0 @@
----
-description: "Layout rhythm — all layout is stacks with a closed gap step set; gather before laying anything out; never ad-hoc sibling margins."
----
-
-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/skeleton/grammar.surfaces.md

@@ -1,26 +0,0 @@
----
-description: "Surface roles and the closed elevation set — gather for any card, popover, modal, dialog, scrim, or bordered container; flat is the default, borders are structural, exactly three elevation tiers."
----
-
-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.

package/dist/init-payloads/skeleton/index.md

@@ -1,27 +0,0 @@
----
-description: "Always read first — the trust tiers of this starter fingerprint, the unanswered dials, and how to work before they are answered."
----
-
-This is a skeleton fingerprint: the adaptation-safe law of good interface work,
-with every brand decision left explicitly open. It steers an agent away from
-the model's median from the first generation, without pretending to be a
-brand it is not.
-
-The corpus carries two trust tiers. Grammar and the median floor are law:
-safe to consume verbatim, unchanged by any adaptation — they speak in
-token roles and closed sets, never in literal values. Signature nodes are
-dials, and in this starter every dial is unanswered: each states the fixed
-relationship worth keeping and the question only a human can answer. Do not
-freehand a dial's value and present it as brand-backed — ask the human or
-flag the gap.
-
-The reset raises the floor; only the fingerprint escapes the median.
-
-Unanswered dials do not block work; they mark what your report must flag.
-When generating before the dials are answered, define the grammar's token
-roles in your own stylesheet with provisional values — the role names are
-the contract; the values are placeholders until the dials say otherwise.
-
-When a requested UI is not covered by a node, compose from the grammar. Do
-not invent a new styling system. If the result needs a new pattern, the new
-pattern should come from observed drift, not anticipation.

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

@@ -1,24 +0,0 @@
----
-description: "Gather whenever color beyond the base roles is in question. The palette dial: a quiet base spine plus a closed expression set at situation-gated volume — 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 brand at different volumes. A quiet base
-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 situation, never by taste. Two constants outrank any
-volume decision: expression never touches what you click — buttons, inputs,
-and links stay on the base roles everywhere — and the status roles are not
-expression; they keep their meanings everywhere and never moonlight as
-atmosphere. The ladder — a quiet spine, a closed hue set, situation-gated
-volume — is the part worth keeping.
-
-The open question: what is this brand's base spine, and what are the named
-hues of its closed expression set — how many, and which? 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.shape.md

@@ -1,19 +0,0 @@
----
-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

@@ -1,20 +0,0 @@
----
-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

@@ -1,22 +0,0 @@
----
-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/skill-bundle/references/wild.md

@@ -1,30 +0,0 @@
----
-name: wild
-description: Use wild nodes deliberately to explore past the fingerprint without claiming conformance.
----
-
-# Recipe: Use Wild Nodes
-
-Use this ritual only when the human asks to explore beyond the current
-fingerprint or when the brief declares explicit **open territory**: the part of
-the work where conformance is intentionally suspended.
-
-1. Run `ghost gather <ask> --wild` to expose wild nodes alongside the
-   steady menu. Wild nodes push past the fingerprint; Ghost still does no
-   selection.
-2. Select deliberately: choose at most a couple of wild nodes whose descriptions
-   match the open territory. Do not bulk-load wild nodes.
-3. Run `ghost pull <steady-id>... <wild-id>...` to read the selected nodes.
-4. In the working brief, name the open territory plainly: where conformance is
-   suspended, which wild node ids are being used, and which steady
-   non-negotiables still bind.
-5. Generate two options:
-   - a conforming baseline grounded only in steady fingerprint context;
-   - a divergent take that uses the selected wild nodes inside the open
-     territory.
-6. Ask a human to pick, reject, or carry the surprise back into the fingerprint
-   through ordinary reviewed edits.
-
-Wild nodes are never routine context. Never claim a divergent take as
-Ghost-backed conformance, and never present surprise as something Ghost chose;
-surprise is chosen by a human.