Anti-AI-slop design skill for Claude Code, Cursor, and Codex.
CSS
Custom hands the whole design to the model: no theme, shape, section list, component or draw, only the floor, the gates and the sweep, with a short brief to make it unique, clean and full; a custom hero is free of the layout rules and sets its own type scale
Youssef7f09844f8e90
diff --git a/README.md b/README.mdindex 2754f23..48fa135 100644--- a/README.md+++ b/README.md@@ -10,7 +10,7 @@ Made by Together AI.<img src="site/OG-hallmark.png" alt="Hallmark, a design skill that refuses to look AI-generated" /></p>-Hallmark holds a hard floor and then gets out of the way. It deals three themes from a catalog of forty-eight materials, and a script applies the rotation so consecutive builds cannot converge. When the user asks for **custom** it derives a world made to measure, with an outside draw picking among grounded directions so the model cannot repeat its favourite. It keeps every page to one idea per screen, set big enough to fill it. Then it lints the result against the tells that read as machine-made in 2026: the eyebrow above every heading, the small label in tracked capitals, the one coloured word in a headline, middle-dot meta strings, arrows glued to link text, mono labels as a technical costume, cream paper with a high-contrast serif and a clay accent, a page of empty picture frames, a heading and a line adrift on a wide canvas, a hero that stops short of its screen, one price said four times, a form that says thanks without sending anything, content that ships invisible when a script fails, text crammed against the edge of its box, and text painted under another element.+Hallmark holds a hard floor and then gets out of the way. It deals three themes from a catalog of forty-eight materials, and a script applies the rotation so consecutive builds cannot converge. When the user asks for **custom** it steps further back: no theme and no plan, only the floor and a brief to make something it has never made before. It keeps every page to one idea per screen, set big enough to fill it. Then it lints the result against the tells that read as machine-made in 2026: the eyebrow above every heading, the small label in tracked capitals, the one coloured word in a headline, middle-dot meta strings, arrows glued to link text, mono labels as a technical costume, cream paper with a high-contrast serif and a clay accent, a page of empty picture frames, a heading and a line adrift on a wide canvas, a hero that stops short of its screen, one price said four times, a form that says thanks without sending anything, content that ships invisible when a script fails, text crammed against the edge of its box, and text painted under another element.The gates come in tiers. The **Floor** never ships: contrast, focus, reduced motion, invented metrics, layout that breaks on a phone, the fold at three widths, the eyebrow. **Reflex** gates are the defaults a language model falls into rather than laws, and a build with an argument may overrule one on the record, with the reason in the CSS stamp and the guard re-derived by the checker. **Finish** checks are craft detail that never blocks a ship. A fresh-context reviewer with no memory of the build gets the last word.@@ -72,7 +72,7 @@ A theme is a material, not a plan: paper, ink, faces, rule weight, radius, shado## Custom-When the user asks for **custom** ("derive it", "bespoke", "no theme"), Hallmark leaves the catalog and designs the page from the client's own material: it lists what only this client has, rejects the category's default page and its predictable opposite, and writes seven ideas of the form *on this page, X becomes Y*, each tested against the nearest competitor. A deterministic draw (`scripts/seed.mjs`) picks which idea gets built and deals one system discipline. The idea owns the palette, the type voice and one signature move; everything else stays plain and exact. Colours are sampled from the subject and argued one by one, pictures appear only where they carry a fact, and a five-line contract is audited promise by promise before shipping. The protocol lives in [`direction.md`](skills/hallmark/references/direction.md).+When the user asks for **custom** ("bespoke", "no theme", "a world of its own"), Hallmark hands the whole design to the model: no theme, no page shape, no section list, no components, no palette recipe. It keeps the floor, the gates against machine-made pages and the sweep, and gives one short brief in [`direction.md`](skills/hallmark/references/direction.md): learn what only this client has, set aside the page you would make anyway, find one idea and let it run the whole page, and make it unique and clean. Clean means exact, not empty, and pictures appear only when the subject has something to show.---diff --git a/ROADMAP.md b/ROADMAP.mdindex 9fcce77..5db054e 100644--- a/ROADMAP.md+++ b/ROADMAP.md@@ -2,7 +2,7 @@What is next for Hallmark.-**Where v2 stands.** Hallmark builds new pages by itself and redesigns existing ones when asked by name. A build deals three themes from a catalog of forty-eight materials, each with a picture of a finished page, or derives a world of its own on request. A redesign records what the page says and does before it starts, works at one of three depths (polish, restyle, full), and fails its own sweep if a link, a form field, a handler or a test hook went missing. A Floor of hard rules and a set of Reflex defaults are enforced by a zero-dependency linter that reads HTML, CSS, framework components and Tailwind classes, and with `--render` measures the page itself: the fold at three widths, contrast against the pixels behind the text, focus rings found by tabbing, section rhythm, heads crowding what precedes them, text cramped against its box or painted under another element. Two fresh-context reviews, of the first screen and of the finished page, close every build.+**Where v2 stands.** Hallmark builds new pages by itself and redesigns existing ones when asked by name. A build deals three themes from a catalog of forty-eight materials, each with a picture of a finished page, or designs one from scratch on request. A redesign records what the page says and does before it starts, works at one of three depths (polish, restyle, full), and fails its own sweep if a link, a form field, a handler or a test hook went missing. A Floor of hard rules and a set of Reflex defaults are enforced by a zero-dependency linter that reads HTML, CSS, framework components and Tailwind classes, and with `--render` measures the page itself: the fold at three widths, contrast against the pixels behind the text, focus rings found by tabbing, section rhythm, heads crowding what precedes them, text cramped against its box or painted under another element. Two fresh-context reviews, of the first screen and of the finished page, close every build.---diff --git a/skills/hallmark/SKILL.md b/skills/hallmark/SKILL.mdindex c4d9055..3f8b06a 100644--- a/skills/hallmark/SKILL.md+++ b/skills/hallmark/SKILL.md@@ -1,6 +1,6 @@---name: hallmark-description: "Design skill for new pages, sites, app screens and components that look made, not generated: deals a theme or derives a world, builds on a hard floor, lints and reviews. Use when the user asks to build or design something new, or names Hallmark. Never use it to change an existing design (a restyle, new colours or theme, a polish, a redesign, a small edit) unless the user names Hallmark: `/hallmark redesign <path>` is the explicit full redesign, keeping content and wiring; `/hallmark audit <path>` only reports."+description: "Design skill for new pages, sites, app screens and components that look made, not generated: deals a theme or designs from scratch, builds on a hard floor, lints and reviews. Use when the user asks to build or design something new, or names Hallmark. Never use it to change an existing design (a restyle, new colours or theme, a polish, a redesign, a small edit) unless the user names Hallmark: `/hallmark redesign <path>` is the explicit full redesign, keeping content and wiring; `/hallmark audit <path>` only reports."argument-hint: "<brief> | redesign <path> | audit <path>"version: 2.7.0---@@ -39,7 +39,7 @@ Above the Floor, a **Reflex** gate is a default a model falls into, which a buil0. Pre-flight: read the project before asking anything.1. Ask once: material, audience, use, tone.2. Shape: design the page, then name it.-3. Direction: deal a theme, or derive a world when asked for custom.+3. Direction: deal a theme, or design freely when asked for custom.4. Load the craft, genre and theme files and `gates.md` § 1 to § 4.5. The Picks block, once.6. Build: the hero first, then the page; stamp, `tokens.css`, log.@@ -47,7 +47,7 @@ Above the Floor, a **Reflex** gate is a default a model falls into, which a buil**Verbs,** only when the user names Hallmark: `redesign <target>` (a full redesign keeping content and wiring) and `audit <target>` (a report); read [`references/redesign.md`](references/redesign.md) first. Any other change to an existing design is not a Hallmark run: do it as asked, in the project's own system, with no deal, scaffold, stamp or sweep.-Codex CLI and OpenCode read [`references/flow.md`](references/flow.md) § Harnesses first; other harnesses run this file as written.+Codex CLI and OpenCode read `references/flow.md` § Harnesses first; other harnesses run this file as written.### 0. Pre-flight@@ -73,7 +73,7 @@ Skipped fields are opt-outs: infer them, state the inferences in one line at theDecide the page's shape, how it opens, which composition each section takes, what the nav and footer do, and what carries the hero. You are designing, not filling a form. For a starting point: 21 page shapes in [`references/macrostructures.md`](references/macrostructures.md) (load only the one file you pick), compositions, navs and footers in [`references/layout.md`](references/layout.md), what the page shows in [`references/imagery.md`](references/imagery.md).-**Rotation and the draw.** Run `node <skill-dir>/scripts/theme.mjs draw --material photo|product|words [--theme <slug>] [--log .hallmark/log.json]` each build. From a fresh seed, clear of the log and the theme's picture, it deals a shape, the hero posture, the nav, the footer, the first section after the hero, two compositions to leave out, and what the hero leads with. Take it unless the brief's material refuses a pick, and name any swap in the Picks block: one brief in one theme, built twice, makes two pages. **Mirror test:** would a neighbouring brief in the same category get this exact combination? If yes, change one decision and say which.+**Rotation and the draw.** Run `node <skill-dir>/scripts/theme.mjs draw --material photo|product|words [--theme <slug>] [--log .hallmark/log.json]` each theme build. From a fresh seed, clear of the log and the theme's picture, it deals a shape, the hero posture, the nav, the footer, the first section after the hero, two compositions to leave out, and what the hero leads with. Take it unless the brief's material refuses a pick, and name any swap in the Picks block: one brief in one theme, built twice, makes two pages. **Mirror test:** would a neighbouring brief in the same category get this exact combination? If yes, change one decision and say which.**Signature.** Every page has one thing a visitor would remember, and it is the brief's strongest real thing shown at its best: the photograph that is the place, the product doing its one job, a price or a date set huge because it is the offer, a control that lets the visitor try it. Decide it here, make it in the dealt theme's material, show it on the first screen, and put it in the Picks block and the stamp; the reviewer checks it. A number drawn as marks (one dot a bottle, a dial of the year) is a device, not a signature (82).@@ -84,7 +84,7 @@ Hold all of it; it is said once, at Step 5.Check in order; the first match wins.1. **The user named a theme** → build it (stamp `theme: <name> (by request)`).-2. **The user asked for custom** ("custom", "derive it", "bespoke", "no theme", "a world of its own") → load [`references/direction.md`](references/direction.md) and run the ritual: no deal and nothing from a theme. Silence never takes this route.+2. **The user asked for custom** ("custom", "derive it", "bespoke", "no theme", "a world of its own") → load [`references/direction.md`](references/direction.md): the design is yours. It replaces the draw, the shapes, `layout.md`, the genre file and Step 6's composition and fold rules; the Floor, gates and sweep hold. Silence never takes this route.3. **Everything else deals a theme:**```@@ -97,7 +97,7 @@ A catalog theme is a material, not a plan: it never sets what the page contains### 4. Load-Exactly these, for a page build: [`references/layout.md`](references/layout.md) · [`references/imagery.md`](references/imagery.md) · [`references/craft.md`](references/craft.md) · `references/genres/<genre>.md` · `references/themes/<slug>.md` and its picture, already seen at the deal (a named theme: look at `<slug>.jpg` now): take its palette balance, type voice and surfaces, never its layout (or `direction.md` on a custom run) · [`references/gates.md`](references/gates.md) § 1 to § 4.+Exactly these, for a page build: [`references/layout.md`](references/layout.md) · [`references/imagery.md`](references/imagery.md) · [`references/craft.md`](references/craft.md) · `references/genres/<genre>.md` · `references/themes/<slug>.md` and its picture, already seen at the deal (a named theme: look at `<slug>.jpg` now): take its palette balance, type voice and surfaces, never its layout · [`references/gates.md`](references/gates.md) § 1 to § 4. A custom run loads `direction.md` instead of the layout, genre and theme files.Only when the build needs them, each in `references/`: one macrostructure file (Step 2) · `microinteractions.md` for stateful UI · `interaction-and-states.md` for forms · `responsive.md` for an unusual layout · `texture.md` when the theme earns texture · `scroll-choreography.md` for a scroll story · `dark-mode.md` when both modes are asked for · `data-viz.md` for charts · `fonts.md` on custom runs · `comp.md` on signal 9 · `design-md.md` when asked to lock the system.@@ -120,7 +120,7 @@ The run's only prose recital of its decisions, and the user's five-second redire- **Sweep** · run after build```-A custom run's rows are in `direction.md` R.8. Then one quiet line: *System portable? Say `lock the system` for a `design.md`.* Skip it in component scope or when `design.md` exists.+A custom run's rows are in `direction.md`. Then one quiet line: *System portable? Say `lock the system` for a `design.md`.* Skip it in component scope or when `design.md` exists.On signal 9, `comp.md` runs here.@@ -128,7 +128,7 @@ On signal 9, `comp.md` runs here.Emit code that satisfies the theme and the shape. Always:-- **Start from the scaffold.** `node <skill-dir>/scripts/theme.mjs scaffold <slug>` (with the deal's `--dealt`; `--custom` on a derived run) writes `tokens.css` (the theme's tokens and the shared scale) and `base.css` (the rules the Floor already decided) beside the project's stylesheet, and prints the stamp skeleton and the two imports that open it. Fill the stamp and write only the page.+- **Start from the scaffold.** `node <skill-dir>/scripts/theme.mjs scaffold <slug>` (with the deal's `--dealt`; `--custom` on a custom run) writes `tokens.css` (the theme's tokens and the shared scale) and `base.css` (the rules the Floor already decided) beside the project's stylesheet, and prints the stamp skeleton and the two imports that open it. Fill the stamp and write only the page.- **Read [`references/patterns.md`](references/patterns.md) once:** controls in all eight states, a slot, a missing fact, a form that posts nowhere yet, one reveal, figures that compare, written to pass the gates. Take their shape, never their copy.- **Hero first.** Write the nav and the hero, run `node <skill-dir>/scripts/sloplint.mjs <file> --render --stage hero`, then the hero review in fresh context (`gates.md` § 6). Build the sections only once the hero ships.- **One idea per screen, set big.** Hero: headline (seven words or fewer, 50 characters or fewer), one sentence (twelve words or fewer), one or two actions. A section: an `h2` of six words or fewer and at most one line, then a composition from `layout.md` § 5 that spans ten of twelve columns and has mass (a visual 360px tall, a set of three across, rows, a statement). Six to nine sections, hero and footer included (five on a thin brief); 450 visible words at most. Fullness comes from scale and visuals, never from more words.@@ -137,7 +137,7 @@ Emit code that satisfies the theme and the shape. Always:- **Page invariants.** One primary button style, one container width, one column gap for every multi-column section below the hero, one radius per nesting level, and never more centred heading groups than left-aligned ones.- **Type.** The theme's faces, at most two families (three with one outlier role), set per `craft.md` § 1; body 16px or more; heads roman, one weight and one colour (38iii); labels never mono unless mono is the material (64).- **States and motion.** Eight states on every interactive element; `transform` and `opacity` only; at most one orchestrated reveal per page, none where the theme keeps still, 0.4 to 0.8s, visible by default; exits at 60 to 75% of the enter; nothing bounces.-- **Stamp.** Line 1 of CSS is the scaffold's stamp skeleton with every field filled, then the critique line (`gates.md` § 3), any `waive` and `answered` lines, and a custom run's direction contract. Everything the linter reads sits in the first 40 lines.+- **Stamp.** Line 1 of CSS is the scaffold's stamp skeleton with every field filled, then the critique line (`gates.md` § 3), and any `waive` and `answered` lines. Everything the linter reads sits in the first 40 lines.- **Existing stylesheets are append-only:** the two imports go right after the file's last `@import`, never below a rule or a `@tailwind` directive; reuse the project's own token names ([`references/export-formats.md`](references/export-formats.md), which also refreshes a `design.md`'s `## Exports`); rewrite only on request.- **Log.** `node <skill-dir>/scripts/theme.mjs log --entry '<json>'` puts the build atop `.hallmark/log.json`: `shape`, `theme`, `axes`, `hero`, `nav`, `footer`, `imagery`, `photos` (the library ids used), `entry` (the section opening), `fingerprint` (`Hanging|Asymmetric spans|Hairline|Outlined|Margin-aligned|None`), `sections` (compositions in order), `signature`, `waived`, `brief`; it names any field you left out.diff --git a/skills/hallmark/references/brand-truth.md b/skills/hallmark/references/brand-truth.mdindex 413f77c..b7d4373 100644--- a/skills/hallmark/references/brand-truth.md+++ b/skills/hallmark/references/brand-truth.md@@ -23,7 +23,7 @@ logo: <official asset page URL>attestation: derived from the fetched sources above, not from memory```-5. **Theme from the spec.** Catalog route: the spec's primary anchors the accent conversion (OKLCH clamped per `craft.md` § 2). Custom route: the spec's primary is the anchor `direction.md` § B.1 samples first; the ritual otherwise runs unchanged. The stamp records `brand: <name> (spec <date>)`.+5. **Theme from the spec.** Catalog route: the spec's primary anchors the accent conversion (OKLCH clamped per `craft.md` § 2). Custom route: the spec's primary is the page's anchor colour; everything else in `direction.md` stays free. The stamp records `brand: <name> (spec <date>)`.## Caching and stalenessdiff --git a/skills/hallmark/references/comp.md b/skills/hallmark/references/comp.mdindex a391f82..9058f0b 100644--- a/skills/hallmark/references/comp.md+++ b/skills/hallmark/references/comp.md@@ -27,7 +27,7 @@ Two comps, three when the direction genuinely forks. One is not a choice and founode <skill-dir>/scripts/imagegen.mjs "<prompt>" --size 1280x800 --n 1 --out .hallmark/comps/c1.png```-The prompt is built from the direction contract or the theme line, not from the brief. A prompt that reads like the brief produces the category default in pixels, the rut `direction.md` R.2 refuses. Carry, in this order: the **first viewport** as the contract states it (what sits where, how large), the **idea** in a few plain words, the **ground and accent** as plain colour words, the **display class** (not the face name; no generator knows Erode), and the **macrostructure** as a compositional instruction. Then one negative clause naming what the category does, so the generator is pushed off it too.+The prompt is built from the Picks block and the stamp's idea or theme line, not from the brief. A prompt that reads like the brief produces the category default in pixels, the page `direction.md` sets aside. Carry, in this order: the **first viewport** as you planned it (what sits where, how large), the **idea** in a few plain words, the **ground and accent** as plain colour words, the **display class** (not the face name; no generator knows Erode), and the **macrostructure** as a compositional instruction. Then one negative clause naming what the category does, so the generator is pushed off it too.> *"Web page hero, top 1280x800 only. A rowing club's season set as one large race timetable, the next race the biggest line on the screen. White ground, deep green ink, one signal-yellow mark. Heavy grotesk headline flush left on five columns, two lines; the timetable on the other seven. A thin rule under the headline, nothing else above the fold. Flat, printed, no depth. Not a centred hero, no cards, no gradient, no device mockup."*diff --git a/skills/hallmark/references/craft.md b/skills/hallmark/references/craft.mdindex 00f3461..b0e80da 100644--- a/skills/hallmark/references/craft.md+++ b/skills/hallmark/references/craft.md@@ -1,6 +1,6 @@# Craft-The file every page build reads beside `layout.md` and `imagery.md`. Type, colour, surfaces, motion, copy, section openings, slots and finish, as numbers wherever a number exists; `layout.md` owns the canvas, the sizes, the room, the sections and the hero. The theme file supplies the material; these two files supply the rules it sits in. Gate numbers in parentheses point at `gates.md`.+The file every page build reads, beside `imagery.md` (and `layout.md` on a theme build). Type, colour, surfaces, motion, copy, section openings, slots and finish, as numbers wherever a number exists; `layout.md` owns the canvas, the sizes, the room, the sections and the hero. The theme file supplies the material; these two files supply the rules it sits in. Gate numbers in parentheses point at `gates.md`.## 1. Type@@ -12,7 +12,7 @@ Type carries the page. At most two families, a display face and a body face, whi- **Body:** 16px minimum (14px never for body), line-height 1.5 to 1.65, measure 45 to 75ch (`max-width: 65ch`) (25). Never all-caps body, never justified without hyphenation, never tracking above 0.05em on body.- **Labels, captions, table heads, meta, tags, chips, nav links:** the body face, a step smaller, sentence case (or lowercase on a theme whose voice is lowercase), untracked (67). Never uppercase, never small caps, never letter-spaced. Mono only when the content is code, a figure or a measurement, or when mono is the theme's material (64). Capitals belong to a wordmark and to a theme whose display voice is uppercase; there a control may follow the display's case at 0.04em of tracking or less.- **Headline sizing by copy length.** Count the rendered `h1`: 20 characters or fewer, full display (a single word may grow to 7rem); 21 to 50, display; 51 to 90, one step down (`--text-display-s`) or split at the sense break with `<br>`; over 90, rewrite. Self-written headlines aim for seven words and 50 characters.-- **Heading measure rides on the element**, in `ch`: the scaffold sets `h1` 20ch, `h2` 30ch, `h3` 40ch; a head at display-s takes about 24ch. Never a `max-width` on the heading group's wrapper.+- **Heading measure rides on the element**, in `ch`: a theme's scaffold sets `h1` 20ch, `h2` 30ch, `h3` 40ch (a custom page sets its own); a head at display-s takes about 24ch. Never a `max-width` on the heading group's wrapper.- **Required:** `font-display: swap`; a fallback stack of the same build (a grotesk falls back to `system-ui`, a serif to Georgia), with `size-adjust` and the overrides only where the face's metrics are published, never guessed; `font-variant-numeric: tabular-nums` on any figures that compare; `text-wrap: balance` on heads, `pretty` on ledes and body; curly quotes, a true ellipsis, a non-breaking space inside unit pairs (`10 MB`, `⌘ K`) in a proportional face (in mono the unit sits outside the mono span or takes a plain space, since a mono space is a full cell). No `--` and no em or en dash anywhere in rendered copy; a comma, a colon or a full stop does the work.- **Wordmark.** May take a different face from the body; on tone-rich themes it should. Collapse to one family only when the body voice is the brand (a letter, a manifesto, a long document).- **Load only the weights you use.** Never synthesise bold or italic.diff --git a/skills/hallmark/references/direction.md b/skills/hallmark/references/direction.mdindex b6c829c..747da88 100644--- a/skills/hallmark/references/direction.md+++ b/skills/hallmark/references/direction.md@@ -1,80 +1,52 @@-# Direction: a world of its own+# Custom: a page of its own-The opt-in path. A build takes it only when the user asks (**custom**, "derive it", "bespoke", "no theme", "a world of its own"). The direction is made for one brief and written into the page's own tokens; it never enters the catalog.+The opt-in path, taken only when the user asks for it (**custom**, "bespoke", "no theme", "a world of its own", "derive it"); silence deals a theme. The catalog takes it back when the user names a theme ("custom, something like Newsprint" is that theme with a mood note), when a `design.md` or a real brand already exists (inherit it), in component scope, and under `--fast` (say so).-Left to its own taste a model ships the same few looks per category, and asked to be unusual it reaches for costume: a world painted onto the page (dials, stamps, paper, engraving) instead of a page that knows its subject. The ritual works against both. The idea comes from the client's own material, a seed picks among the candidates, the idea gets one move, and the rest of the page is plain and exact. Every gate fires unchanged; the Picks block shows the idea, the palette and the pairing before code so the user can redirect.+## Yours, all of it-**Nothing from the catalog.** A custom run never deals and never opens a theme file, and its display face is one no theme sets. The reviewer's test: if a fresh reader could name the catalog theme this page resembles, rework it before the sweep.+On a custom run nothing is dealt and nothing is prescribed: no theme, no shape, no section list, no component, no palette recipe, no draw. What the page is, how it is built and how it looks are your decisions, made for this one client. Hallmark keeps three things: the floor, the gates against machine-made pages, and the sweep. SKILL.md calls you a capable designer; here it means it in full.-**The catalog takes it back** when the user names a theme ("custom, something like Newsprint" is a theme pick with a mood note), when a `design.md` or a real brand already exists (inherit it), and in component scope. `--fast` on a custom ask resolves to the catalog; say so.+So aim higher than a good page. Make the one a design lead would bring to a client who has already turned down every template: something you have never made before, that no other brief could have produced, that a designer would stop to look at twice. Be ambitious in the idea and exact in the execution.-## The ritual+- **Unique is specific.** Every large decision belongs to this client: its subject, its place, its materials, its numbers, the way its people talk. Put the nearest competitor's name on the page; if it still works, keep going.+- **Clean is exact, not empty.** A system you can see (a few type sizes far apart, one spacing rhythm, edges that line up), nothing on the page that is not doing a job, and on every screen one thing strong enough to be its reason.+- **Full is the floor.** A custom page is a whole site, not a hero and a sampler: everything the client has to say and show, from the first screen to the footer, usually six to nine sections, each built around something worth looking at (the product working, a photograph, real facts set large, something to try). Less to look at is not cleaner, only thinner; a section that is a head and a paragraph is unfinished.+- **Free is free.** Dark or light, one colour or four, type as the picture or photographs edge to edge, a structure no template has, something the visitor can try: every road is open when the idea asks for it.-In order, before any palette work. Each step is a line or two; the whole reads as a short paragraph of decisions, not a form.+## Before the first line of code-**R.1 Inventory.** Eight to twelve things only this client has: the name and what it means, the place and what it looks like, what the product does (one verb), its real numbers, its one constraint, its rituals and hours, the things its world prints, makes or wears, and the material the brief supplies. Mark each *shown* (a photograph of it exists, or it can be built) or *said* (it lives in words).+1. **Learn the subject.** What only this client has: the name and what it means, the place and how it looks, what it does in one verb, its real numbers, its hours and rituals, what its world makes, prints or wears, the words its customers use, and whatever the brief supplies.+2. **Set aside the page you would make anyway.** Picture the page this brief gets without trying, and its obvious twist; neither ships. Yours is usually a split hero with the head on the left and a picture on the right, three numbered steps, rows of label and value between hairlines, a closing band with a form, a dark footer under a huge wordmark, small grey labels, and a pale ground with one careful accent. Two of those in one plan means the plan is the template: start again from the idea.+3. **Go wide, then choose.** Sketch three directions as far apart as you can make them, two lines each: the idea, how the page is built, how it looks. Build the one a design lead would fight for, never the safest; borrow from the other two only what makes it stronger.+4. **Let the idea run the page.** One thought the whole page grows from, true of this client and no other. It can live in the type, the colour, the structure, the motion, the way the product is shown, or something the visitor does. Let it decide the rest, top to bottom: an idea that stops at the hero is a template with a good hero.+5. **Let the content build the structure.** Decide what a visitor must see, understand and do, and in what order, then give each part the form that shows it best. What the sections are, their order, the nav and the footer are yours; the stamp names what you made.-**R.2 The rut.** Name the page this category always ships and its predictable opposite; both are out. Spent in every family: cream, off-white or greige paper (warm beige is the same rut one step darker; take it only when the subject's own material is that colour, and say so), near-black with one neon accent, pill buttons, an italic or coloured word in a head, numbered or mono labels, a card grid, a centred head over three features. Your own rendition prior is spent too: a warm, bookish or family subject pulls Claude toward cream, serif and lamplight whatever the draw said, so re-read the idea before code and rework from the subject's own colours if the page drifted.+## Spent-**R.3 The slate.** Seven candidates, numbered, one line each, written as *on this page, [an inventory item] becomes [a form]*. A form is a way of laying out information that this audience already knows how to read, taken from the client's own world: a document, a sign, a listing, a notation, a publication. Forms carry their restraint with them; an object that would have to be faked in CSS is not a form. Spread the seven across shown and said items, and give the brief's own noun one seat at most. Test each with the nearest real competitor: if the line still fits with their name in it, it belongs to the category, so rewrite it.+What every model ships, refused on sight:-**R.4 The draw.** The model never picks its favourite:+- cream, off-white or beige paper with a high-contrast serif and a clay accent (65); near-black with one neon accent; a pale ground with one timid accent; purple into blue (2a); a hue picked for the category, such as blue for software or green for health;+- the faces you reach for first (`fonts.md`, its banned and saturated lists) and any face a catalog theme sets;+- a centred head over three cards, or the run of hero, features, call to action and footer (3, 8); a stock second action;+- a subject painted on instead of known: paper or grain as a surface, a stamp, a dial or a knob as ornament, bevels, an engraving, a drawing of the thing (47c, 80);+- an eyebrow, tracked capitals, mono labels, one coloured word in a head, middle-dot strings (54, 67, 64, 38iii, 63).-```-node <skill-dir>/scripts/seed.mjs --brief "<the brief, as the user wrote it>" --n 7 --material photo|product|words-```+## Pictures-It prints `draw: n/7 (seed <slug>·<date>·r0)` (build slate line n), the faces for § C, and one **discipline**: a system rule about how far colour commits, how the grid holds, how the type steps or how pictures sit. Take it unless the material refuses it, and give a refusal one line in the Picks block. Re-roll only when the user asks (`--reroll 1`). Without Node: entry (letters in the brief, mod 7) + 1, no discipline; stamp `seed: fallback-<letters>·<date>·r<n>`.+Only when the subject has something to show. A place, food, people at work, an object, a craft: photographs, few and large, the user's or the library's (`imagery.md` § 2), credited. Software: the product itself, built and working (`imagery.md` § 4). A service, an idea or a body of words: type and colour can carry the whole page, and often should. Every picture passes the deletion test: take it away and the page loses a fact. A picture for mood alone goes.-**R.5 Reach.** The idea owns three things: the palette, the type voice and one signature move, on the first screen and echoed once at most. Everything else is plain and exact: the nav, the buttons, the forms, the section anatomy and every state are conventional, in the idea's colours and faces, and the regions around the signature hold still. Painted physicality (a bevel, an emboss, an engraving, paper or grain as a surface, a knob or a dial as ornament, a stamp) is costume: the page knows its subject, it does not dress up as it.+## Words-**R.6 The page plan.** The sections as claims, one line each with the proof it shows and the composition it takes (`layout.md` § 5): no composition twice, the signature in the hero, the strongest real material next. Number stages only when they are a real sequence, and set rows only for a real list; a run of Steps, Rows and a closing Band is the template whatever paints it.+The copy is half the design, and the first place a generated page gives itself away. `craft.md` § 6 binds in full: the owner's own nouns, a fact in every head, no line a competitor could use unchanged, about 80 words a screen. Give the headline a shape of its own: two clipped fragments in a row is the one every model reaches for. Then read the headings alone: they should tell this client's story and no one else's.-**R.7 Colour posture.** Exactly one, with a reason: Restrained (accent under 5%), Committed (one colour carries 30 to 60% of the page as whole fields), Full palette (three or four named roles with jobs), Drenched (the ground is the colour). The stamp and the log carry it; gate 23 reads it.+## What still binds-**R.8 The contract.** Five lines, 120 words or fewer, a comment directly below the stamp and critique line:+The Floor, every gate in `gates.md` (44a and 44c leave a custom hero free), `craft.md` wherever it states a rule (its sizes and its Restrained default are a theme's starting point, not yours), the facts rule (46a), licensed pictures, the stamp, the log, the sweep and both reviews. Not `layout.md`, the genre file, the shape catalog or the draw. `patterns.md` shows how states, slots and forms work, never how they look.-```-/* direction contract · seed <key>- * THESIS: the position the page takes, and the category default it refuses.- * IDEA: on this page, <inventory item> becomes <form>; the signature move.- * FIRST VIEWPORT: what sits where, how large, and where the action is.- * SYSTEM: ground, ink and accent with where each came from; display and body; the three sizes.- * ANTI: the page it must not be mistaken for (a real site or a familiar template) and the two moves that would make it that. */-```+## Mechanics-A line that reads like a mood is undecided. The stamp adds `theme: custom · idea: "<the drawn line, n/7>" · vibe: "<4 to 8 words>" · paper: oklch(…) · accent: oklch(…) · display: <face> · body: <face> · axes: <triple> · posture: <posture> · seed: <key> · discipline: <the dealt rule, or refused: why> · contract: kept (5/5)`, the last field written only after the finish review; the log entry carries the same fields. The Picks block replaces its Theme row with **Idea** (the drawn line, the discipline) and **System** (the palette with its sources, the pairing).--## A. Pictures--They come from R.1, never from a mood. A shown item with a real photograph (the place, the food, the people at the work) leads, as `imagery.md` § 1 says, and one decisive photograph beats five. Software and ideas show the product built, or let type and colour carry the page: a first screen of type alone is a full answer. Every picture passes the deletion test: take it away and the page loses a fact. A city at night, a laptop on a desk or an office building on a software page fails it.--## B. Palette: sample, converge, argue--1. **Sample.** The first source that exists: the anchor colour the user gave (a real brand's from `.hallmark/brand-spec.md`, never memory); the colours of the photographs the page will show (the hero's dominant and its one strong hue); the subject's own materials (its interface, its paint, its packaging, its landscape). Never a hue for the category, such as blue for software or green for health.-2. **Converge.** A ground, an ink and one accent; under Committed or Drenched, one field colour beside them. Two chromatic colours at most, plus neutrals.-3. **Argue.** One clause per colour in the SYSTEM line saying where it came from. A colour with no source is a default.-4. **Ground.** Its lightness follows when and where the page is read: light L 95 to 99 (white with `surface: absolute` in the stamp, 7b), mid L 30 to 85, dark L 12 to 20. Cream, ivory, parchment and blue-black only when the subject pins them.-5. **Ink and neutrals.** Ink L 16 to 24 on a light ground, 88 to 96 on a dark one; the rule, the muted text and the second ink step toward the ground, tinted toward the accent at chroma 0.005 to 0.012 (22).-6. **Accent.** Chroma 0.12 to 0.20 and a stated role (the actions, focus, the one mark). The focus ring takes its hue at chroma 0.18 to 0.22; accent-ink reaches 4.5:1.-7. **Check** gates 7, 22, 23 and 65 before code. Texture only where a photograph is the ground; never paper, grain or noise as a surface.--## C. Type--One family or two, three with an outlier that carries one role (a wordmark, a figure, code). The display face is one no catalog theme sets: run `node <skill-dir>/scripts/theme.mjs check --face "<face>"`. Take the class the idea calls for from `fonts.md`; the draw's `faces` line deals one face per class and a body face of each kind, so start from those, and swap one only when it fails on the real headline, judged by its shape and never its name (a subject association is not a reason); the Picks block says why. Three sizes carry the page, far apart: the display at least four times the body and the section head between them; titles and leads stay one step from the body. Labels take the body face, sentence case, untracked (64, 67); a head is one weight and one colour (38iii). Free faces only unless the user confirms a licence.--## D. Axes--Declare the triple so Rotation reads it like a catalog theme's: paper band (dark under 30% L, mid 30 to 85, light over 85), display class (`fonts.md`), accent band (warm 10 to 60°, cool 200 to 300°, neutral under 0.05 chroma, chromatic-<name>), plus the posture. `node <skill-dir>/scripts/theme.mjs check --axes "<triple>" --face "<face>" --hue <h> --log .hallmark/log.json` names any catalog theme or recent build on the same coordinates. Then look at that theme's picture beside the page you are planning: move a coordinate only if the two would read alike, and say which in one line. Specificity, not distance on a chart, is what separates a custom page from the catalog.--## Bespoke depth--The brief's structure itself is the ask and no shape fits (a scroll-assembled poem, an index that is the whole page). The ritual runs as written; the build may drop the shape catalog, the genre routing and the rotation. It keeps every gate, the font and OKLCH discipline, one orchestrated motion, the Picks block, the stamp and the log. It is rare: on a vanilla brief it is over-reach.--## The finish review--The fresh-context reviewer gets the contract (`review-finish.md` has what a custom run adds). Before the sweep, re-read the contract yourself, promise by promise: an unkept promise is a revision, not a ship.--## What derivation does not do--It does not lower the floor, extend the catalog, invent facts (46a binds hardest where a fresh world makes invented proof feel at home) or skip the draw. It does not mean more decoration: a derived system is a tighter argument than a catalog theme, not a louder one.+- **Scaffold:** `theme.mjs scaffold --custom`. Fill every `--color-*` and `--font-*`; the scale it writes is a start, not a style, so set the sizes, spacing, widths and gaps the design needs and keep the names.+- **Faces:** one family or two, three with an outlier that carries one role; free faces unless the user confirms a licence; the display face is one no catalog theme sets (`node <skill-dir>/scripts/theme.mjs check --face "<face>"`). `fonts.md` lists faces no theme uses: a start, not a menu.+- **Colour:** OKLCH, any posture (`craft.md` § 2), declared in the stamp with its reason (23); contrast and focus unchanged (40, 41, 26a).+- **Picks block:** Shape and Theme become **Idea** (one sentence) and **Look** (ground, ink, accent and faces, each with where it came from); every other row says what you decided.+- **Stamp and log:** `theme: custom · idea: "<one sentence>" · vibe: "<4 to 8 words>"`, the paper, accent and faces, `hero:` in your own words, and `axes` and `posture` as on any build. The finish reviewer reads the idea where a theme build has its theme (`review-finish.md`).diff --git a/skills/hallmark/references/flow.md b/skills/hallmark/references/flow.mdindex 6d1c768..09cef49 100644--- a/skills/hallmark/references/flow.md+++ b/skills/hallmark/references/flow.md@@ -30,7 +30,7 @@ The cache is the same block as JSON: `{ "scanned": "<date>", "findings": { "fontSignals: the brief names one element (button, input, form, card, modal, dropdown, tooltip, select, checkbox, switch, tab strip, chip, badge, banner, snackbar, popover, slider, date picker, avatar, a single nav or footer); the brief is short and refers to one element; the target file is one component; the user says "just the X". Two signals: component. Ambiguous ("a pricing section"): ask once, *One pricing card, or the whole pricing page?*, defaulting to component.-**Keeps:** pre-flight, the Step 1 questions (once), genre detection, existing tokens (otherwise the theme deal, since one component needs no derived world), the two-family type discipline, and a stricter state rule: every interactive component ships all eight states (default, hover, `:focus-visible`, `:active`, disabled, loading, error, success) per `interaction-and-states.md`.+**Keeps:** pre-flight, the Step 1 questions (once), genre detection, existing tokens (otherwise the theme deal, since one component needs no custom design), the two-family type discipline, and a stricter state rule: every interactive component ships all eight states (default, hover, `:focus-visible`, `:active`, disabled, loading, error, success) per `interaction-and-states.md`.**Skips:** macrostructure, nav and footer, hero, imagery, the multi-section preview, and the log append (components do not rotate).@@ -96,7 +96,7 @@ On Claude Code, `node <skill-dir>/scripts/install-hook.mjs` wires sloplint as a## Comp before build (signal 9)-Fires only when `TOGETHER_API_KEY` is set. After the Picks block, load `comp.md`: two comps of the first viewport at 1280 x 800, built from the direction contract or the theme line rather than the brief, varied on one compositional axis, one approval, then a medium inventory naming how each region gets built. Reproduction is checked against the comp at its own size before anything below the fold exists. The comp never overrides the Floor (an image generator has read no gates; take its composition, not its compliance) and never blocks: two comp rounds is the ceiling, then build unconstrained and say so.+Fires only when `TOGETHER_API_KEY` is set. After the Picks block, load `comp.md`: two comps of the first viewport at 1280 x 800, built from the idea or the theme line rather than the brief, varied on one compositional axis, one approval, then a medium inventory naming how each region gets built. Reproduction is checked against the comp at its own size before anything below the fold exists. The comp never overrides the Floor (an image generator has read no gates; take its composition, not its compliance) and never blocks: two comp rounds is the ceiling, then build unconstrained and say so.## Harnessesdiff --git a/skills/hallmark/references/fonts.md b/skills/hallmark/references/fonts.mdindex e9d2c0f..642319b 100644--- a/skills/hallmark/references/fonts.md+++ b/skills/hallmark/references/fonts.md@@ -2,7 +2,7 @@Loaded on a custom run. A catalog theme has already named its faces; do not read this to second-guess it.-**Needs before reading:** the drawn idea and the material it shows. **Gives:** a display face, a body face, an optional outlier, and the load rules.+**Needs before reading:** the page's idea and what it shows. **Gives:** a display face, a body face, an optional outlier, and the load rules.## The rule@@ -48,7 +48,7 @@ The wordmark in the nav and footer may take a different face from the body, and.wordmark { font-family: var(--font-outlier); font-weight: 600; letter-spacing: -0.015em; }```-Collapse to one family only when the body voice is the brand (a letter, a manifesto, a long document) or a one-family discipline was dealt; then the wordmark takes the family's display cut or its heaviest weight. A product page whose wordmark is the body face at 600 is the un-designed default.+Collapse to one family only when the body voice is the brand (a letter, a manifesto, a long document); then the wordmark takes the family's display cut or its heaviest weight. A product page whose wordmark is the body face at 600 is the un-designed default.## Loadingdiff --git a/skills/hallmark/references/gates.md b/skills/hallmark/references/gates.mdindex 14a3635..880c09f 100644--- a/skills/hallmark/references/gates.md+++ b/skills/hallmark/references/gates.md@@ -93,9 +93,9 @@ One line each. `a`/`b` clauses share a number and carry their own tier. Genre no| 24a | Floor | M | Raw `padding`, `margin` or `gap` length where a `--space-*` token exists for it | the token || 24b | Reflex | M | Off-scale spacing values. Guard: at most three, each an optical nudge | the scale || 34 | Floor | M/R | Horizontal scroll at any width 320 to 1920; `overflow-x` missing on `html` and `body`; `100vw` widths | `overflow-x: clip` on both, `width: 100%` |-| 44a | Reflex | R/J | Hero content off centre for its posture, measured on what is painted: from the nav's bottom to the hero's first content, against the hero's last content to the next section's first. Settled, Banner, Corridor and Stage want the second 1.0 to 1.5 times the first; Ledge inverts; Poster waives when anchored | centre the content in its screen (`layout.md` § 6) |+| 44a | Reflex | R/J | Hero content off centre for its posture, measured on what is painted: from the nav's bottom to the hero's first content, against the hero's last content to the next section's first. Settled, Banner, Corridor and Stage want the second 1.0 to 1.5 times the first; Ledge inverts; Poster waives when anchored; a custom hero (`theme: custom`) is free | centre the content in its screen (`layout.md` § 6) || 44b | Floor | R/J | Headline, lede, primary CTA and the visual's focal point not all visible at 1280 x 800 without scrolling | pull the display clamp down, tighten leading, two-line lede, trim padding |-| 44c | Reflex | R/J | At 1440 x 900 the next section starts above y 760 or below y 900, or the hero visual's vertical centre is more than 60px from the text block's, or its left edge more than 120px from the text, or it is pinned to the viewport edge. Guard: Poster, Ledge or Banner posture, a Stage visual bleeding off the outer edge (the edge clause only), or a stamped full-bleed E1 | visual beside the text, hero fills its screen and only its screen |+| 44c | Reflex | R/J | At 1440 x 900 the next section starts above y 760 or below y 900, or the hero visual's vertical centre is more than 60px from the text block's, or its left edge more than 120px from the text, or it is pinned to the viewport edge. Guard: Poster, Ledge or Banner posture, a Stage visual bleeding off the outer edge (the edge clause only), a stamped full-bleed E1, or a custom run | visual beside the text, hero fills its screen and only its screen || 44d | Floor | M/R | At 1920 x 1080 the container has no `max-width`, gutters under 120px, a grid gains columns, or the hero no longer fits | cap 1360 to 1520 and centre; hold column counts; cap `vw` visuals || 50 | Floor | M | Image-bearing grid track using bare `1fr`; display head without `overflow-wrap: break-word; min-width: 0` | `minmax(0, 1fr)`; `break-word`, never `anywhere` || 53 | Floor | M | CSS-only radio tabs at `position: absolute; top: 0` with no JS guard (scroll-jumps on every click) | radios in flow at zero size, or a handler with `preventScroll` |@@ -191,7 +191,7 @@ The gates above that a script cannot settle, with enough to judge them well.**38iii, the accented word.** One word in the accent colour, one word in bold, one word on a highlighter band: the calibration guides name it beside the eyebrow as the machine-made head. A head is one weight, one style and one colour. Three themes carry an accented word as their signature (Manifesto's red word, Lumen's coloured verb, Riso's misregistered word); they stamp the waiver and place it once, in the hero.-**44, the fold.** Three widths, one question each: at 1280 x 800 is everything the hero has to say inside the screen; at 1440 x 900 is the hero exactly one screen, its content centred in it, with its visual beside the text; at 1920 x 1080 does the container hold and the hero still fit. Fill a short hero with the visual or the headline, never with more copy.+**44, the fold.** Three widths, one question each: at 1280 x 800 is everything the hero has to say inside the screen; at 1440 x 900 is the hero exactly one screen, its content centred in it, with its visual beside the text; at 1920 x 1080 does the container hold and the hero still fit. A custom hero answers the first and the last. Fill a short hero with the visual or the headline, never with more copy.**46b, the bare number.** A figure is a headline only when the page is built around it and it carries its unit and its source.@@ -205,7 +205,7 @@ The gates above that a script cannot settle, with enough to judge them well.**63, template punctuation.** The middle dot as a universal separator, the arrow as a universal suffix and the coloured dot as a universal prefix are the punctuation of generated pages. One dot in a byline, a marquee's separator and a dot that conveys live state are legal.-**65, the named look.** Cream, high-contrast serif, terracotta. Every published calibration of generated design names this triple first, and a warm, bookish or family brief pulls a model toward it hardest. A catalog theme that carries it was vetted as a material and is dealt only when the brief's keywords ask for it, so the gate reads custom and unthemed builds; there the ritual's spent table refuses it first.+**65, the named look.** Cream, high-contrast serif, terracotta. Every published calibration of generated design names this triple first, and a warm, bookish or family brief pulls a model toward it hardest. A catalog theme that carries it was vetted as a material and is dealt only when the brief's keywords ask for it, so the gate reads custom and unthemed builds; there `direction.md` refuses it first.**66, decoration text.** The agency-portfolio tics: rotated labels, scroll cues, version pills, city-and-weather strips, mono-caps strips under the hero, credit lines under stock images. Each says "designed" without carrying a fact. A fact stays; a decoration goes.@@ -223,7 +223,7 @@ The gates above that a script cannot settle, with enough to judge them well.## 6. The reviews, in fresh context-The thread that built the page is its weakest reviewer. Two reviews run with no inherited transcript (a subagent in Claude Code): the **hero review** once at Step 6, before any section below the fold exists, and the **finish review** at Step 7. When a subagent can run them, do not read their briefs yourself: start the reviewer with *Read `<skill-dir>/references/review-hero.md` (or `review-finish.md`) and follow it* and pass these, files as paths and lines as quoted text. The hero review: the four `hero-*` screenshots, the stamp's first two lines, the Picks block's Material and Signature rows, the theme's picture. The finish review: the render tier's screenshots, the page's HTML or component source, the stamp's theme line or direction contract, the theme's picture, the hero review's findings with how each was settled, `gates.md` § 4, and on a redesign the `before` screenshots. Run it in the foreground, since the build waits on its first word (in Claude Code, `run_in_background: false`), never behind a timer or a wake-up.+The thread that built the page is its weakest reviewer. Two reviews run with no inherited transcript (a subagent in Claude Code): the **hero review** once at Step 6, before any section below the fold exists, and the **finish review** at Step 7. When a subagent can run them, do not read their briefs yourself: start the reviewer with *Read `<skill-dir>/references/review-hero.md` (or `review-finish.md`) and follow it* and pass these, files as paths and lines as quoted text. The hero review: the four `hero-*` screenshots, the stamp's first two lines, the Picks block's Material and Signature rows, the theme's picture. The finish review: the render tier's screenshots, the page's HTML or component source, the stamp's theme or idea line, the theme's picture, the hero review's findings with how each was settled, `gates.md` § 4, and on a redesign the `before` screenshots. Run it in the foreground, since the build waits on its first word (in Claude Code, `run_in_background: false`), never behind a timer or a wake-up.Act on its first word. `recapture` means the screenshots were wrong (a fallback face, a blank frame): retake them and start the review again; it does not use up the one round. Otherwise fix what is real, recapture the same shots (`--stage hero` for the hero), and score each finding yourself against its recapture: `resolved`, `partial` or `unresolved`, with a reason. Send the recaptures back for one scoring round only when the first word was `rebuild` or a finding named a Floor gate; scoring is not a second review. Record the outcome in the stamp, hero first: `hero-review: fix · 4 findings · 4 resolved`, then `finish-review: subagent · 5 findings · 4 resolved 1 unresolved · gap: none`. No subagents: then, and only then, read the brief, re-read the artifact cold, run the brief against yourself, and record `in-thread`.diff --git a/skills/hallmark/references/genres/atmospheric.md b/skills/hallmark/references/genres/atmospheric.mdindex 3855acd..4f507c4 100644--- a/skills/hallmark/references/genres/atmospheric.md+++ b/skills/hallmark/references/genres/atmospheric.md@@ -4,7 +4,6 @@ The AI-creative and after-dark product page: generative music, video, image, voi## Voice-- **Faces** (a theme names its own; this is for a custom run): a weighty sans or a roman serif for display, tight tracking; the same family at 400 for the body, light ink on dark paper.- **Accent:** one hue, used in the canvas treatment, on focus rings and on small tags; never on display text unless the theme's type names an accented word (Lumen).- **Layout:** a centred hero is the normal answer when the type is the visual (a Poster or Banner posture); with a visual, it stands beside the text (44c). The canvas is the design and the type sits on it.- **Motion:** fade only; the atmosphere does the work.diff --git a/skills/hallmark/references/genres/editorial.md b/skills/hallmark/references/genres/editorial.mdindex de14c1c..5dc29f5 100644--- a/skills/hallmark/references/genres/editorial.md+++ b/skills/hallmark/references/genres/editorial.md@@ -4,7 +4,6 @@ Content-led briefs: portfolios, manifestos, type specimens, agency sites, magazi## Voice-- **Faces** (a theme names its own; this is for a custom run): a roman serif, a condensed sans or a display-heavy face at an extreme weight (300, or 700 and up), never a default sans; a workhorse serif or a plain non-default sans for the body.- **Accent:** one hue, held to the posture's footprint.- **Layout:** asymmetric; hairlines, not card borders; type set large enough to hold its screen.- **Motion:** quiet, one orchestrated entrance.diff --git a/skills/hallmark/references/genres/modern-minimal.md b/skills/hallmark/references/genres/modern-minimal.mdindex 719e918..6d6da8f 100644--- a/skills/hallmark/references/genres/modern-minimal.md+++ b/skills/hallmark/references/genres/modern-minimal.md@@ -4,7 +4,6 @@ The polished product page: SaaS, enterprise, API, platform, developer tool, infr## Voice-- **Faces** (a theme names its own; this is for a custom run): a grotesk or geometric sans at 500 to 700, tracked -0.02 to -0.035em; the body in the same family at 400 or one plain sans beside it.- **Accent:** ink, or one hue on focus rings and one control; colour floods only under a declared posture.- **Layout:** two-column heroes (the title and its line beside a big slot), wide product visuals, thin visible borders rather than hairlines.- **Motion:** minimal; reveals off; the page is composed.diff --git a/skills/hallmark/references/genres/playful.md b/skills/hallmark/references/genres/playful.mdindex 5d35fd2..b7ea8b8 100644--- a/skills/hallmark/references/genres/playful.md+++ b/skills/hallmark/references/genres/playful.md@@ -4,7 +4,6 @@ Pages that should feel alive rather than tidy: a brief that asks for playful, fu## Voice-- **Faces** (a theme names its own; this is for a custom run): a rounded or geometric sans at 600 to 700, tight tracking, or a heavy display face on the loud end; friendly, never childish. The body a plain sans in a slightly muted ink.- **Accent:** soft and low-chroma by default; a declared Full-palette or Drenched posture lifts chroma to 0.24 across three or four named roles, each with a job.- **Layout:** rounded surfaces (12px cards, 8px inputs, pills, unless the theme sets its radius), soft offset shadows, tinted alternating bands.- **Motion:** responsive to the pointer; one small entrance on the page, its one reveal (`craft.md` § 5); a spring only under a declared spring posture, on the primary CTA and one character moment (gate 12's exception).diff --git a/skills/hallmark/references/layout.md b/skills/hallmark/references/layout.mdindex 49a2e4a..9a7ec16 100644--- a/skills/hallmark/references/layout.md+++ b/skills/hallmark/references/layout.md@@ -1,6 +1,6 @@# Layout-The one file every page build reads for space. A page looks made when every screen is full of one idea set at the right size, and generated when it is either crowded or a few small things adrift on a wide canvas: a 36px heading, one line and a small object in a 1300px container, under a hero with a dead band at its foot. This file sets the canvas, the sizes, how a section is built and how full it must be. The theme supplies the material; this file supplies the room. Numbers are at 1440 x 900 unless a line says otherwise; gate numbers in parentheses point at `gates.md`.+The one file every theme build reads for space; a custom run designs its own (`direction.md`). A page looks made when every screen is full of one idea set at the right size, and generated when it is either crowded or a few small things adrift on a wide canvas: a 36px heading, one line and a small object in a 1300px container, under a hero with a dead band at its foot. This file sets the canvas, the sizes, how a section is built and how full it must be. The theme supplies the material; this file supplies the room. Numbers are at 1440 x 900 unless a line says otherwise; gate numbers in parentheses point at `gates.md`.## 1. The canvasdiff --git a/skills/hallmark/references/microinteractions.md b/skills/hallmark/references/microinteractions.mdindex 5ee75c8..c1344ce 100644--- a/skills/hallmark/references/microinteractions.md+++ b/skills/hallmark/references/microinteractions.md@@ -68,7 +68,7 @@ catch { item.done = prev; render(); toast({ tone: "error", message: "Could not s## Motion character-Every system declares one: a catalog theme in its Motion section, a derived direction in its contract's FORM block. The same press is louder in a severe system than in a calm one.+Every system declares one: a catalog theme in its Motion section, a custom page in its own stylesheet. The same press is louder in a severe system than in a calm one.| Character | Duration scale | Feels like || --- | --- | --- |diff --git a/skills/hallmark/references/review-finish.md b/skills/hallmark/references/review-finish.mdindex d00cc0d..00941b1 100644--- a/skills/hallmark/references/review-finish.md+++ b/skills/hallmark/references/review-finish.md@@ -1,16 +1,16 @@# Finish review-You are reviewing a built page against a fixed list. You did not build it and will not be told why anything is the way it is. Read the page, not the intent. Your inputs, and nothing else: the screenshots the render tier wrote (the folds at 1280 x 800, 1440 x 900 and 1920 x 1080, the full page at 1440 and at 375), the page's HTML or component source, the direction contract or theme line from the stamp, on a theme build the theme file and its picture, the hero review's findings with how each was settled, and `gates.md` § 4. Look at the screenshots first; open the HTML only to quote copy or to locate a finding; the linter has already read the CSS. A pinned pane shows once in a full-page shot: the column beside its later screens is the pin, not an empty half. Batch your reads; stop reading by the tenth turn and write.+You are reviewing a built page against a fixed list. You did not build it and will not be told why anything is the way it is. Read the page, not the intent. Your inputs, and nothing else: the screenshots the render tier wrote (the folds at 1280 x 800, 1440 x 900 and 1920 x 1080, the full page at 1440 and at 375), the page's HTML or component source, the theme or idea line from the stamp, on a theme build the theme file and its picture, the hero review's findings with how each was settled, and `gates.md` § 4. Look at the screenshots first; open the HTML only to quote copy or to locate a finding; the linter has already read the CSS. A pinned pane shows once in a full-page shot: the column beside its later screens is the pin, not an empty half. Batch your reads; stop reading by the tenth turn and write.-First line: one of `recapture` (a screenshot is missing, blank or shows the wrong thing; list what to recapture and stop), `rebuild` (the first viewport fails the contract or the theme wholesale), `fix` (findings follow), `ship` (nothing owed).+First line: one of `recapture` (a screenshot is missing, blank or shows the wrong thing; list what to recapture and stop), `rebuild` (the first viewport fails the idea or the theme wholesale), `fix` (findings follow), `ship` (nothing owed).Then the findings, ranked by cost to the page, at most eight, one line each: the gate or the plain defect, where it is, what you would do. Not findings: a direction you would not have chosen; what the theme file prescribes or refuses (its blooms, a glow on a theme with none); an element the hero review settled, unless you name a new reason. The theme's picture is the bar for finish and never a model: is this page as finished as that one, in a composition of its own?Scroll the 1440 full page one screen at a time before ranking: a screen with nothing big enough to be its reason (a head and a line adrift, a narrow column beside an empty half, a section head under 40px, an empty coloured box or a drawn illustration where a photograph or the product should be, a row of counting marks) outranks every detail finding (`layout.md` § 8). Then the copy: name any head that would pass unchanged on a competitor's page (`craft.md` § 6).-Then one answer to the question no gate can: does the stamp's contract or theme describe the page in front of you? Name the largest gap, or say there is none.+Then one answer to the question no gate can: does the stamp's idea or theme describe the page in front of you? Name the largest gap, or say there is none.-On a custom run (`theme: custom`), before you read the contract, write four lines of your own from the screenshots: what the page is about, its palette and type, each section's composition in one word, and the one move a visitor would remember. Then three checks, each a finding when it fails. **Costume:** painted physicality (a bevel, an emboss, an engraving, paper or grain as a surface, a knob or a dial as ornament) or one device repeated more than twice. **Template:** two sections with the same composition, or a run of numbered steps, hairline rows and a closing band. **Swap:** put the nearest competitor's name on the page; if it still works, the idea is the category's, and say which section gives it away. Last, the contract's ANTI line: does the page read as the lookalike it names?+On a custom run (`theme: custom`) the page owes no shape, composition or hero layout: it was designed from nothing, so judge it as a design, never against `layout.md`. Before the idea line, write two lines of your own from the screenshots: what the page is about, and the one thing a visitor would remember. Then three findings when they fail. **Seen before:** the page, or a section, reads as a template, a catalog theme or a familiar site; name which and where. **Clean:** something is on the page without a job (a device repeated, a decoration, a box around nothing), or a screen has nothing worth looking at. **Carried:** the idea lives in the hero and stops there.On a redesign you also get the `before` screenshots, and the content is fixed: never ask for copy, an action or a visual the old page did not have. Add one answer: what did the old page do better? Name anything a visitor could do, read or find before that is harder now; if nothing, say so. On a polish you get only the full pages at 1440, before and after: the layout was kept on purpose, so ask one thing, whether anything still reads as machine-made, in at most five findings.diff --git a/skills/hallmark/references/review-hero.md b/skills/hallmark/references/review-hero.mdindex b1a0729..de4bd83 100644--- a/skills/hallmark/references/review-hero.md+++ b/skills/hallmark/references/review-hero.md@@ -13,6 +13,8 @@ Then at most five findings, one line each, worst first. Ask:- Does the type carry the theme at this size?- With the theme's picture: is this first screen as finished as its first screen, in a composition of its own?+On a custom run (`theme: custom`) the composition is free: skip the centred, beside-the-text and 60% questions, and ask instead whether this screen is one you would expect a model to make for this brief. If it is, say what gives it away.+On a redesign the page's content is fixed and what sits below the first screen is the old page, not yet rebuilt: neither is a finding. Never ask for copy, an action or a visual the page does not have; say in one line what the owner could supply.What the theme file prescribes (its blooms, its control pair) or refuses is not a finding. Where the theme file and its picture disagree, the theme file wins over its picture. Do not fix anything.diff --git a/skills/hallmark/scripts/refcheck.mjs b/skills/hallmark/scripts/refcheck.mjsindex 97869a5..7f18bcc 100644--- a/skills/hallmark/scripts/refcheck.mjs+++ b/skills/hallmark/scripts/refcheck.mjs@@ -283,14 +283,6 @@ for (const target of clean) {else if (s.fails || s.reflex || s.warns) add('error', target, 1, 'lint', `must lint clean, has ${s.fails} FAIL, ${s.reflex} REFLEX, ${s.warns} WARN`);}-// the custom draw deals its faces from fonts.md's own table; a reformatted table must not empty the deal-{- const out = spawnSync(process.execPath, [join(ROOT, 'scripts', 'seed.mjs'), '--brief', 'refcheck', '--material', 'photo'], { encoding: 'utf8' }).stdout || '';- const dealt = ((/^faces: (.*)$/m.exec(out) || [])[1] || '').split(' · ').filter(Boolean);- if (dealt.length < 10 || !dealt.some((f) => f.startsWith('body sans ')) || !dealt.some((f) => f.startsWith('body serif '))) add('error', join(ROOT, 'scripts', 'seed.mjs'), 1, 'faces', `seed.mjs dealt ${dealt.length} faces from fonts.md; the display table or the body paragraph no longer parses`);- if (!/^discipline: /m.test(out)) add('error', join(ROOT, 'scripts', 'seed.mjs'), 1, 'faces', 'seed.mjs printed no discipline');-}-const FIX = join(ROOT, 'scripts', 'fixtures');const lintJson = (t) => { const r = spawnSync(process.execPath, [join(ROOT, 'scripts', 'sloplint.mjs'), t, '--json'], { encoding: 'utf8' }); try { return JSON.parse(r.stdout); } catch { return null; } };const gatesOf = (j) => new Set(j.findings.map((x) => String(x.gate)));diff --git a/skills/hallmark/scripts/seed.mjs b/skills/hallmark/scripts/seed.mjsdeleted file mode 100644index 9557119..0000000--- a/skills/hallmark/scripts/seed.mjs+++ /dev/null@@ -1,90 +0,0 @@-#!/usr/bin/env node-// The custom path's draw (references/direction.md R.4). From a seed made of the brief, the date and the re-roll count it-// picks which of the model's seven slate lines gets built, so the model never builds its own favourite, and deals one-// discipline: a system rule (colour, grid, type steps, pictures, motion) the page adopts unless its material refuses it.-// A discipline never brings a device, a material or a face: it can only make the page plainer and more exact. It also-// deals one display face per class and one body face of each kind from references/fonts.md, so the model starts from a-// dealt face instead of its favourite (left alone it set four custom pages of eight in the same grotesk).-// node seed.mjs --brief "<the brief>" [--n 7] [--reroll 0] [--material photo|product|words]-import { readFileSync } from 'node:fs';-import { fileURLToPath } from 'node:url';-import { dirname, join } from 'node:path';--function fnv1a(str) {- let h = 0x811c9dc5;- for (let i = 0; i < str.length; i++) {- h ^= str.charCodeAt(i);- h = Math.imul(h, 0x01000193) >>> 0;- }- return h >>> 0;-}--// [the rule, the material it suits: any, photo, product or words]-const DISCIPLINES = [- ['One field colour: a single colour carries about a third of the page as whole sections edge to edge, never as boxes; everything else sits on the ground.', 'any'],- ['The ground is the colour: one deep or saturated ground for the whole page, ink and one accent on it, nothing else.', 'any'],- ['One family: display and body come from one type family, and hierarchy comes from size and weight alone.', 'any'],- ['Three sizes carry the page: display, section head and body, far apart (the display at least five times the body); titles take the one small step above the body and nothing else gets a size of its own.', 'any'],- ['No boxes: no cards and no shadows, and no border except on an input; space and alignment part every group.', 'any'],- ['Flush left: no centred head and no centred block; every left edge sits on one of three lines down the page.', 'any'],- ['Dense, then empty: every dense section is followed by one that holds a single line in a lot of air.', 'any'],- ['One rule system: hairlines are the only structure (under the nav, between rows, above the footer), one weight and one colour.', 'any'],- ['Still: nothing moves except the signature; no reveal, no lift on hover, only colour changes on hover.', 'any'],- ['The grid shows: every element starts and ends on the twelve columns, and the page breaks the grid exactly once, on purpose.', 'any'],- ['Photographs bleed: every picture runs to the edge of its column or of the screen; none is framed, rounded or shadowed.', 'photo'],- ['One decisive photograph: the page shows a single picture, very large, and lets type carry everything else.', 'photo'],- ['Pictures in pairs: below the hero, photographs come two at a time at unequal sizes, each pair making one point.', 'photo'],- ['The product at full width: the interface runs the width of the container with real data, no device frame and no tilt.', 'product'],- ['The product up close: each section crops one part of the interface large enough to read, with one line beside it.', 'product'],- ['A reading page: one long measure of 60 to 70 characters, generous leading, few sections, the type doing the work.', 'words'],- ['Type is the picture: the first screen is set in type alone, and the largest line on it is the offer itself.', 'words'],-];--const args = process.argv.slice(2);-const flag = (name, dflt) => {- const i = args.indexOf(`--${name}`);- return i !== -1 && args[i + 1] !== undefined && !String(args[i + 1]).startsWith('--') ? args[i + 1] : dflt;-};-const ASK = new Set(['build', 'make', 'create', 'design', 'need', 'want', 'please', 'page', 'site', 'website', 'landing', 'called', 'for', 'and', 'the', 'with', 'that', 'this', 'our', 'your', 'custom', 'theme']);-const briefFlag = flag('brief', null);-if (!briefFlag && (args.length === 0 || args[0].startsWith('--'))) {- console.error('usage: node seed.mjs --brief "<the brief>" [--n 7] [--reroll 0] [--material photo|product|words]');- process.exit(2);-}-const slug = briefFlag- ? briefFlag.toLowerCase().replace(/[^a-z0-9\s-]/g, ' ').split(/\s+/).filter((w) => w.length > 2 && !ASK.has(w)).slice(0, 4).join('-') || 'brief'- : args[0].toLowerCase().replace(/[^a-z0-9]+/g, '-').replace(/^-|-$/g, '');--const n = Math.max(2, parseInt(flag('n', '7'), 10) || 7);-const reroll = Math.max(0, parseInt(flag('reroll', '0'), 10) || 0);-const material = flag('material', '');-if (material && !['photo', 'product', 'words'].includes(material)) { console.error('--material is photo, product or words'); process.exit(2); }-const date = new Date().toISOString().slice(0, 10);--const seedKey = `${slug}·${date}·r${reroll}`;-const index = (fnv1a(seedKey) % n) + 1;-const pool = DISCIPLINES.filter(([, m]) => m === 'any' || !material || m === material);-const discipline = pool[fnv1a(`${seedKey}·discipline`) % pool.length][0];--// fonts.md is the one list: its display table (class | faces) and its body paragraph (Sans: ... Serif: ...)-const names = (txt) => txt.replace(/\([^)]*\)/g, '').split(/[;,]/).map((f) => f.trim()).filter((f) => f && !/only with an argument/.test(f));-let faces = [];-try {- const src = readFileSync(join(dirname(fileURLToPath(import.meta.url)), '..', 'references', 'fonts.md'), 'utf8');- const table = (src.split('## Display faces the catalog does not use')[1] || '').split('\n## ')[0];- for (const line of table.split('\n')) {- const m = /^\|\s*([^|]+?)\s*\|\s*([^|]+?)\s*\|\s*$/.exec(line);- if (!m || m[1] === 'Class' || /^-+$/.test(m[1])) continue;- const list = names(m[2]);- if (list.length) faces.push(`${m[1].toLowerCase()} ${list[fnv1a(`${seedKey}·${m[1]}`) % list.length]}`);- }- const body = (src.split('## Body faces')[1] || '').split('\n## ')[0];- for (const [kind, re] of [['sans', /Sans:([^.]*)\./], ['serif', /Serif:([^.]*)\./]]) {- const list = names((re.exec(body) || [])[1] || '');- if (list.length) faces.push(`body ${kind} ${list[fnv1a(`${seedKey}·body ${kind}`) % list.length]}`);- }-} catch { faces = []; }--console.log(`draw: ${index}/${n} (seed ${seedKey})`);-console.log(`discipline: ${discipline}`);-if (faces.length) console.log(`faces: ${faces.join(' · ')}`);diff --git a/skills/hallmark/scripts/sloplint-render.mjs b/skills/hallmark/scripts/sloplint-render.mjsindex d841b5f..01d5b04 100644--- a/skills/hallmark/scripts/sloplint-render.mjs+++ b/skills/hallmark/scripts/sloplint-render.mjs@@ -141,7 +141,7 @@ export async function renderCheck(htmlFiles, metaIn) {const field = (/hero:\s*([^·*\n]+)/i.exec(stamp) || [])[1] || '';let route = ''; try { route = new URL(file).pathname.replace(/\/$/, '') || '/'; } catch {}const own = new RegExp(`(settled|banner|poster|ledge|corridor|stage)\\s*\\(${route.replace(/[.*+?^${}()|[\]\\]/g, '\\$&')}\\)`, 'i').exec(field);- meta.heroPostureByFile[file] = ((own || /(settled|banner|poster|ledge|corridor|stage)\b/i.exec(field) || [])[1] || '').toLowerCase();+ meta.heroPostureByFile[file] = /theme:\s*custom\b/i.test(stamp) ? 'custom' : ((own || /(settled|banner|poster|ledge|corridor|stage)\b/i.exec(field) || [])[1] || '').toLowerCase();}const pageMeta = { genre: meta.genre, posture: meta.postureByFile[file] || 'restrained' };const prefix = heroOnly ? 'hero-' : '';@@ -667,7 +667,7 @@ function observe(checkFold, meta) {}function observeSpace(atLaptop, heroOnly, heroPosture) {- const freeFold = /^(poster|ledge|banner)$/.test(heroPosture || '');+ const freeFold = /^(poster|ledge|banner|custom)$/.test(heroPosture || '');const out = [];const push = (gate, grade, evidence, fix) => out.push({ gate: String(gate), grade, evidence, fix });const vw = window.innerWidth, vh = window.innerHeight;@@ -847,7 +847,7 @@ function observeSpace(atLaptop, heroOnly, heroPosture) {const after = secs.find((x) => x !== hero && !hero.contains(x) && abs(x).top >= hb.bottom - 4);const bottomEdge = after ? Math.min(content(after).top, hb.bottom + 240) : hb.bottom;const topPad = cTop - navBottom, bottomPad = bottomEdge - cBottom;- if (isFinite(topPad) && isFinite(bottomPad) && topPad > 24 && bottomPad < topPad - 8) push('44a', 'REFLEX', `hero content sits low: ${Math.round(topPad)}px above it, ${Math.round(bottomPad)}px below`, 'Centre the content in its screen: the space below 1.0 to 1.5 times the space above (a Ledge sits low on purpose; say Ledge in the stamp)');+ if (heroPosture !== 'custom' && isFinite(topPad) && isFinite(bottomPad) && topPad > 24 && bottomPad < topPad - 8) push('44a', 'REFLEX', `hero content sits low: ${Math.round(topPad)}px above it, ${Math.round(bottomPad)}px below`, 'Centre the content in its screen: the space below 1.0 to 1.5 times the space above (a Ledge sits low on purpose; say Ledge in the stamp)');heroFoot = { cBottom, navBottom };}if (heroEnd != null && !freeFold) {diff --git a/skills/hallmark/scripts/sloplint.mjs b/skills/hallmark/scripts/sloplint.mjsindex 9ce8f3f..4f81594 100644--- a/skills/hallmark/scripts/sloplint.mjs+++ b/skills/hallmark/scripts/sloplint.mjs@@ -4089,7 +4089,8 @@ function buildContext(key, cssList, docList) {...docs.flatMap((d) => d.styles.map((st) => head40(st.css))),].join('\n');const posture = (/posture:\s*(restrained|committed|full-palette|drenched)/i.exec(stampText)?.[1] || 'restrained').toLowerCase();- const heroPosture = (/hero:\s*(settled|banner|poster|ledge|corridor|stage)\b/i.exec(stampText)?.[1] || '').toLowerCase();+ // a custom page designs its own hero: 44a and 44c read it as free+ const heroPosture = /theme:\s*custom\b/i.test(stampText) ? 'custom' : (/hero:\s*(settled|banner|poster|ledge|corridor|stage)\b/i.exec(stampText)?.[1] || '').toLowerCase();for (const d of docs) { postureByFile[d.file] = posture; heroPostureByFile[d.file] = heroPosture; }const allCss = cssFiles.map((c) => c.raw).join('\n') + '\n'+ docs.map((d) => d.styles.map((st) => st.css).join('\n')).join('\n');diff --git a/skills/hallmark/scripts/theme.mjs b/skills/hallmark/scripts/theme.mjsindex b404233..bd23cd6 100644--- a/skills/hallmark/scripts/theme.mjs+++ b/skills/hallmark/scripts/theme.mjs@@ -461,6 +461,9 @@ button, input, select, textarea { font: inherit; }@media (max-width: 40rem) { :root { --gutter: 16px; --section-gap-s: 56px; --section-gap: 72px; --section-gap-l: 96px; --gap-columns: 16px; } }@media (prefers-reduced-motion: reduce) { *:not(.keep-motion), *:not(.keep-motion)::before, *:not(.keep-motion)::after { animation-duration: 0.01ms !important; animation-iteration-count: 1 !important; transition-duration: 0.01ms !important; scroll-behavior: auto !important; } }`;+// A custom run sets its own type: its base keeps the Floor's rules and drops the heading sizes, weight, leading and measure.+const BASE_CUSTOM = BASE.replace(/^h1, h2, h3 \{[^}]*\}$/m, 'h1, h2, h3 { margin: 0; font-family: var(--font-display); font-synthesis: none; overflow-wrap: break-word; min-width: 0; text-wrap: balance; }').replace(/^h1 \{ max-width[^\n]*\n/m, '').replace(/^\.lead \{[^\n]*\n/m, '');+const SLOTS_JS = `window.hallmarkSlots = (m) => { for (const [k, v] of Object.entries(m)) { const s = document.querySelector(\`[data-slot="\${k}"]\`); if (!s) continue; const im = new Image(); im.src = typeof v === 'string' ? v : v.src; im.alt = (typeof v === 'object' && v.alt) || s.dataset.alt || ''; s.querySelectorAll(':scope > img').forEach((o) => o.remove()); s.prepend(im); } };\ndocument.querySelectorAll('[data-slot] img').forEach((i) => { if (i.complete && !i.naturalWidth) i.remove(); else i.addEventListener('error', () => i.remove(), { once: true }); });`;function scaffold() {@@ -503,7 +506,7 @@ function scaffold() {: `:root {\n${scheme}${scale}\n${tokens}\n}\n`;writeFileSync(out, css);const own = !custom && /## Build hint[\s\S]*?(::selection\s*\{[^}]*\})/.exec(readFileSync(join(THEMES, `${slug}.md`), 'utf8'));- const base = own ? BASE.replace(/::selection \{[^}]*\}/, own[1].replace(/\s+/g, ' ')) : BASE;+ const base = own ? BASE.replace(/::selection \{[^}]*\}/, own[1].replace(/\s+/g, ' ')) : custom && !brand ? BASE_CUSTOM : BASE;const steps = base.split('\n').filter((l) => /^@media[^{]*\{\s*:root/.test(l));const photo = custom ? '' : treatmentOf(header.photo, tokensOf(readFileSync(join(THEMES, `${slug}.md`), 'utf8'), slug)).css;writeFileSync(baseOut, (tw ? base.split('\n').filter((l) => !steps.includes(l)).join('\n') : base) + (photo ? `\n/* photographs: ${header.photo} */\n${photo}` : '') + '\n');@@ -519,9 +522,9 @@ function scaffold() {: brand? `/* Hallmark · shape: <shape, or kept> · genre: <genre> · theme: brand${tail}${made} · hero: <posture, or kept> · nav: <shape, or kept> · footer: <shape, or kept> · signature: <the one move, or kept>\n * axes: ${axes} · contrast: pass · fold: pass · v${VERSION} */`: custom- ? `/* Hallmark · shape: <shape> · genre: <genre> · theme: custom${tail} · idea: "<the drawn line, n/7>" · vibe: "<4 to 8 words>"${made} · hero: <posture> · nav: <shape> · footer: <shape> · imagery: <photographs, the product, or none> · signature: <the one move>\n * axes: ${axes} · seed: <key> · discipline: <the dealt rule, or refused: why> · contract: <after the finish review> · contrast: pass · fold: pass · v${VERSION} */`+ ? `/* Hallmark · shape: <your name for the structure> · genre: <genre> · theme: custom${tail} · idea: "<one sentence>" · vibe: "<4 to 8 words>"${made} · hero: <in your own words> · nav: <shape> · footer: <shape> · imagery: <photographs, the product, or none> · signature: <the one thing a visitor remembers>\n * axes: ${axes} · contrast: pass · fold: pass · v${VERSION} */`: `/* Hallmark · shape: <shape${kept}> · genre: ${header.genre} · theme: ${theme}${tail}${depth ? '' : ' · draw: <seed>'}\n * hero: <posture${kept}> · nav: <shape${kept}> · footer: <shape${kept}> · imagery: <photographs, the product, or none> · signature: <the one move>${dial ? ` · ${dial[1]}: <the dials>` : ''}\n * axes: ${axes} · contrast: pass · fold: pass · v${VERSION} */`;- console.log(`wrote ${out} (${brand ? 'the shared scale; fill every --color-* and --font-* from the palette and faces the pre-flight found' : custom ? 'the shared scale; fill every --color-* and --font-* from direction.md § B and § C before building' : `${name} tokens plus the shared scale`}) and ${baseOut} (the base rules the Floor already decided)${sheet && !flag('dir', '') ? `, beside ${sheet}` : ''}`);+ console.log(`wrote ${out} (${brand ? 'the shared scale; fill every --color-* and --font-* from the palette and faces the pre-flight found' : custom ? 'a starting scale, yours to rewrite; fill every --color-* and --font-* before building' : `${name} tokens plus the shared scale`}) and ${baseOut} (the base rules the Floor already decided)${sheet && !flag('dir', '') ? `, beside ${sheet}` : ''}`);if (!custom && !flag('dealt', '')) {const pic = join(THEMES, `${slug}.jpg`);if (existsSync(pic)) console.log(`look at ${pic}: the material at full size${header.pictured ? `, from a page built as ${header.pictured}` : ''}. Take its palette balance, type voice and surfaces, never its layout; the room and the sections are layout.md.`);