@litfamily/litopencode 1.0.7 → 1.0.9

package/skills/lit-typographic-motion/references/style-bibles.md

@@ -0,0 +1,88 @@
+# Style bibles
+
+A style bible is the one page you write before any scene exists. It fixes the palette, the three
+type voices, the motion vocabulary, the pass stack, the layout grid, what to avoid and what must be
+original. The engine reads the preset data in `engine/constants.mjs`; this page is the reasoning a
+scene author applies on top of it. Every preset below is expressed in this product's own words.
+
+## Template (fill one per film)
+
+| Field | What to write | Why it matters |
+| --- | --- | --- |
+| Idea | One sentence: the film's single visual metaphor for this brief | Stops a film becoming a slideshow of effects |
+| Preset | `swiss-signal`, `terminalcore` or `tidal`, and the reason (keyword hit or user choice) | The report states the pick and why (MO-B-00) |
+| Palette | The preset's named colours; which one is the signal, which the rare accent | One signal hue plus at most one accent cluster (MO-C-29) |
+| Voices | Display, machine and body voice, with the fonts each script resolves to | Hangul always uses the lit-pptx pair; Latin display may step width |
+| Motion | The named tokens used (slam, hold, snap-cut, drift, surge-punch, type-in) | No ad hoc curves; the engine only knows named tokens (MO-A-08) |
+| Passes | The pass order from the preset | GLSL coverage on every frame is a gate rule (MO-C-01) |
+| Grid | Columns, gutter, margin, baseline | Everything glyph-shaped stays inside title-safe (96 px / 54 px) |
+| Anti-slop | Three things this film will not do | Reviewed at the Look step |
+| Originality | Where this film's shapes and copy come from | Nothing is reused from another film |
+
+## Auto-pick (MO-B-00)
+
+Whole-word match over the brief's own text, first row wins, and an explicit style always wins.
+Latin words match at word boundaries; Korean words match at the start of a token, never inside a
+longer word.
+
+| Brief mentions | Preset |
+| --- | --- |
+| 터미널, CRT, 해커, terminal, hacker | `terminalcore` |
+| 물결, 파도, 잔잔한, 흐름, gradient, wave, tide, calm | `tidal` |
+| anything else | `swiss-signal` |
+
+`system`, `status`, 시스템 and a bare `flow` are deliberately not keywords: they appear in briefs
+about payment systems, design systems and workflows that want nothing terminal-like.
+
+## `swiss-signal` (default)
+
+- Palette: ink `#0C0E13` background, bone `#E9EBE4` type, teal signal `#0F7A82`, amber accent
+  `#D9A441` for exactly one moment, graphite `#4B5058` for hairlines.
+- Contrast facts: bone on ink is about 16:1. Teal on ink is about 3.8:1, so teal is a rule, a bar or
+  large type (32 px and up, or 25 px bold) only, never body copy.
+- Voices: Archivo display (static width x weight instances; width steps are Latin-only), MesloLGS NF
+  for small machine annotations, the lit-pptx LitOpenCode Sans pair for Hangul running text.
+- Motion: `slam` (180 ms on the proven deceleration curve) lands a title on a downbeat, `hold`
+  keeps it still, `snap-cut` changes scene with no easing. Nothing bounces.
+- Passes: `swiss-grid` hairline rules, then a low-strength Bayer `dither` as a print texture, then
+  the engine's post chain (grain, halation, vignette).
+- Grid: 12 columns, 24 px gutter, 96 px margin, 8 px baseline; asymmetric placement, generous
+  negative space, small annotations beside large type rather than under it.
+- Avoid: every word fading in at centre, one ease for everything, glitch with no reason, any
+  multi-hue gradient, bloom on anything but the signal, a hold so long it reads as a stall.
+
+## `terminalcore`
+
+- Palette: navy `#05070A` background, panel `#0C1116` window fill, phosphor green `#39FF6A` as the
+  one signal (the blue `#2FB6FF` alternate is never mixed in the same film), dim grey `#7C8B93`.
+- Voices: Galmuri9 for Korean pixel display (the outline build; the bitmap-strike build renders
+  blank), VT323 for Latin pixel display, Silkscreen for chrome labels, MesloLGS NF for readouts.
+  Galmuri and VT323 never share one readout line.
+- Motion: `type-in` at the terminal's character rate (a Hangul 어절 appears whole), `boot-flicker`
+  bursts bounded by the CRT flicker cap, `hard-cut` on beats.
+- Passes: `terminal-ui` (window chrome, meters, caret on one Canvas2D layer), then `crt`
+  (scanlines, curvature, persistence, capped flicker), then `dither`, then rare `glitch` hits.
+  Glitch hits and boot bursts share the two-events-per-second ceiling per shot (MO-SH-03).
+- Grid: 1.5 px window chrome on a flat grid; text aligned to the character cell.
+- Avoid: falling code rain, neon purple haze, glitch as constant texture, both signal hues at once,
+  pixel type set below its grid floor (Galmuri9 at multiples of 9 px, at least 45 px).
+
+## `tidal`
+
+- Palette: indigo `#0E1420` background, off-white `#E8ECEF` type, deep teal `#124559` and violet
+  `#4C3B6E` gradient stops, coral `#E07856` for one punctuation moment.
+- Contrast facts: off-white clears 8:1 on every stop, so type sits directly on the flow.
+- Voices: Archivo display used calmly (little width or weight motion), LitOpenCode Sans for Hangul,
+  MesloLGS NF for small timestamps.
+- Motion: `drift` (a slow in-out curve over seconds, matched to the flow speed) and a short
+  `surge-punch` tied to a gradient surge. No hold-then-snap rhythm as the default.
+- Passes: `tidal-gradient` (domain-warped noise flow, seeded per shot), then `swiss-grid` for
+  layout discipline, then at most one rare `glitch` hit per shot.
+- Avoid: a rainbow ramp, bloom on the gradient itself, glitch as texture, a flow so fast that held
+  type smears under motion blur.
+
+## Originality rules for every preset
+
+Invent this brief's own visual idea for each shot. Never reuse another film's palette values, scene
+concepts, motifs, lyric text or plate imagery. The palette pattern (one signal, one rare accent)
+transfers; specific colours from elsewhere do not.

package/skills/lit-typographic-motion/references/treatment.md

@@ -0,0 +1,143 @@
+# Treatment: the film before any frame
+
+Every film starts here. Write `treatment.json` in the run's output directory (the `--out` directory)
+before any render. The render validates it first, on both paths and in `--stills-only` too, and stops
+with exit 16 (`BLOCKED_TREATMENT_INVALID`) naming the first field that fails. A treatment is a
+director's decision record: what the film is about, what the viewer sees in each beat, how it moves
+and sounds, and what would make it excellent. Load the path reference only after `path` is set.
+
+## Fields
+
+"Normalized" below means NFC, lowercase, then every space and punctuation mark removed. Before any
+comparison with `request`, every quoted span (`"…"`, `“…”`, `'…'`, `「…」`) is removed from it.
+
+| Field | Rule |
+| --- | --- |
+| `request` | The user's words, verbatim, including the `lit` word if present. |
+| `genre` | One of `announcement`, `brand-mood`, `event`, `explainer`, `motion-graphics`, `type-led`, `other`. |
+| `path`, `pathReason` | `type` or `stage` by the path rule below; `pathReason` says why in one line. |
+| `idea` | One sentence: the film's own idea. It may not share a normalized run of min(10, half the normalized request length) characters with the request. |
+| `audience`, `channel` | Who watches, and where it plays. |
+| `format`, `formatReason` | `16:9` (1920x1080) or `9:16` (1080x1920), with a reason tied to `channel`. |
+| `durationSec` | 4-90. Unless the user asked for a length, `announcement`, `event`, `explainer` and `motion-graphics` run at least 10 s. |
+| `beats[]` | `{t0, t1, purpose, onScreen, motion, sound}` in order, each at least 1.2 s, covering 0 to `durationSec` with no gap over 0.25 s. At least as many beats as the genre's arc has stages; `type-led` has one beat per supplied line. |
+| `subject` | `{name, source: user or invented, specifics[]}` with at least 2 concrete specifics: what it is or does, for whom, one distinctive detail. `source: user` only when the request names it. |
+| `visualDevices[]` | `{kind, role: subject, support or texture, beats[]}`; `beats` lists beat indices (from 0). Kinds: `illustration`, `diagram`, `chart`, `icon`, `shape`, `path`, `mask`, `depth3d`, `particles`, `grid`, `gradient`, `photo-texture`. |
+| `typePlan` | `{faces[], hierarchy, maxWordsOnScreen}`; faces come from `Archivo`, `LitOpenCode Sans`, `VT323`, `Silkscreen`, `MesloLGS NF`, `Galmuri9`. Optional `showIndex: true` prints a shot index on the type path. |
+| `palette[]` | 3-6 entries `{hex: "#rrggbb", role}`. |
+| `sound` | `{mode, plan, ...}`. `mode` is `generated`, `supplied`, `authored` or `none`. |
+| `copy` | `{source: user or invented, lines[]}`. |
+| `inventions[]` | Every invented name, line, number and fact. Required when `copy.source` or `subject.source` is `invented`, and it must contain `subject.name`. |
+| `ambition` | 1-2 sentences, in craft terms, on what would make this film excellent for this request. |
+| `seed`, `fps` | Optional. `seed` fixes every random value on the stage (`Math.random` and the kit's `rand`); `fps` is 60 by default, 30 when the treatment says so. |
+
+### Path rule
+
+- `type` when the words themselves are the film: the user asked for kinetic type, a lyric or quote
+  video, a title sequence or typographic motion, or supplied words with no other subject, at 16:9.
+  The validator accepts `type` only with `copy.source: user` or a type-led cue in the request, and
+  only at `16:9`.
+- `stage` for every other film, including any film that needs shapes, drawn objects, diagrams or
+  imagery beyond type. Supplied words on the stage path become stage copy.
+- A 9:16 film always takes the stage path.
+
+### Subject and devices
+
+- On the stage path at least one device has `role: subject`: a drawn depiction of what the film is
+  about, never a background. That device's beats cover at least half of `durationSec`.
+- The stage path also needs at least 2 distinct counting kinds. `grid`, `gradient`, `particles` and
+  `photo-texture` are always `role: texture` and never count.
+- When the request names no subject, words or facts, invent one: a name, what it is or does, for
+  whom, and one distinctive detail. List every invented part in `inventions[]` and label it in the
+  reply. Write the copy from `subject.specifics`, never from the request's own wording.
+
+### Copy
+
+- `source: user`: every normalized line is a substring of the normalized request (quoted spans kept).
+  Keep the user's words; do not polish them.
+- `source: invented`: no line may share the idea's substring limit with the request. A line that
+  could be pasted unchanged into a film about another subject is too generic; rewrite it from the
+  specifics.
+
+### Sound
+
+- `generated` (the default under bare `lit`, on both paths): the product builds a deterministic bed
+  from the treatment. It needs `palette` (`glass`: bell partials over a soft pad; `warm`: rounded saw
+  pad and sub; `pulse`: plucked square arpeggio; `air`: sine pad with breath noise), `key` such as
+  `"D minor"` or `"F# major"`, and `tempo` 60-180 BPM. Each beat's `sound` field may ask for an
+  accent: a `hit` on its cut, a `rise` into the next beat, a `cadence` to close, or `thin` to pare
+  the bed back for that beat. The reply labels the bed as generated.
+- `supplied`: the user's file, `file` relative to the output directory or absolute.
+- `authored`: a WAV you wrote into `stage/`, `file` such as `"stage/score.wav"`.
+- `none`: only when the user asked for silence, or `mutedByDesign: true` when the channel plays muted.
+
+Every track that is not `none` is muxed, padded or trimmed to the film with a 50 ms fade.
+
+## Placeholder example
+
+The values below only show each field's shape. They are placeholders, so this example never
+validates, and a treatment whose free-text fields match half or more of it is refused as a copy
+(`copiedExample`). Write every value for this film.
+
+```json
+{
+  "request": "<the user's words, verbatim>",
+  "genre": "<one genre>",
+  "path": "<type or stage>",
+  "pathReason": "<why this path, one line>",
+  "idea": "<one sentence>",
+  "audience": "<who watches>",
+  "channel": "<where it plays>",
+  "format": "<16:9 or 9:16>",
+  "formatReason": "<tied to the channel>",
+  "durationSec": "<4-90>",
+  "beats": [
+    { "t0": "<start s>", "t1": "<end s>", "purpose": "<arc stage>", "onScreen": "<what is drawn>", "motion": "<how it moves>", "sound": "<what the ear gets>" }
+  ],
+  "subject": { "name": "<name>", "source": "<user or invented>", "specifics": ["<what it is or does>", "<for whom>", "<one distinctive detail>"] },
+  "visualDevices": [{ "kind": "<kind>", "role": "<subject, support or texture>", "beats": ["<beat index>"] }],
+  "typePlan": { "faces": ["<face>"], "hierarchy": "<what reads first, second, third>", "maxWordsOnScreen": "<count>" },
+  "palette": [{ "hex": "<#rrggbb>", "role": "<role>" }],
+  "sound": { "mode": "<mode>", "plan": "<the sound's arc>", "palette": "<timbre palette>", "key": "<key>", "tempo": "<BPM>" },
+  "copy": { "source": "<user or invented>", "lines": ["<line>"] },
+  "inventions": ["<each invented name, line or fact>"],
+  "ambition": "<1-2 sentences in craft terms>"
+}
+```
+
+## Genre arcs
+
+A beat is one stage of the arc; a long film gives a stage more than one beat. Length comes from the
+arc, not from a word count.
+
+- **announcement:** hook → context → key moment → details → close.
+- **brand-mood:** motif → variation → peak → resolve.
+- **event:** hook → what, when, where → highlight → close.
+- **explainer:** question → steps → result → recap.
+- **motion-graphics:** opening motif → set piece → set piece → peak → resolve.
+- **type-led:** one breath per line, with emphasis and pause.
+- **other:** at least three stages you name in `purpose`.
+
+## Craft rules
+
+- Show the subject; do not only name it. With the sound muted and every word hidden, the drawn
+  subject alone should still suggest what the film is about.
+- Aim for professional motion-design craft in every film: varied transitions (match cuts, masks,
+  morphs), rhythm locked to the sound, layered depth, clear hierarchy, deliberate easing. Every beat
+  shows something new. Length comes from the arc; never shorten the film or merge beats to pass a
+  check.
+- Put the subject's specifics on screen as drawn things, not as captions about them.
+- Plan each cut against the sound: a hit lands on the cut, a rise leads into it, and the close has a
+  cadence.
+- The brief's or the request's own title never prints on screen unless it is the film's name and is
+  in `copy.lines`; never print a file name, a preset name or a word such as path, beat or treatment.
+
+## After the treatment
+
+- Stage path: load `stage.md`.
+- Type path: load `authoring.md`, `type-craft.md` and `style-bibles.md`.
+- Both: `craft-loop.md` holds the look questions, rounds, done rules and reply; `runtime.md` holds the
+  exit codes.
+- The first valid treatment is kept. If a later one shortens the film by more than 20 %, removes
+  subject beats, silences the sound without a user request or moves a stage film to the type path,
+  the done check records it as `downgraded` and the reply must say so.

package/skills/lit-typographic-motion/references/type-craft.md

@@ -0,0 +1,55 @@
+# Type craft for Korean and Latin in motion
+
+## Fonts and who ships them
+
+| Voice | Latin | Hangul | Source |
+| --- | --- | --- | --- |
+| display | Archivo, static instances at widths 75/100/125 x weights 400/700/900 | LitOpenCode Sans Regular/Bold | Archivo instanced at development time from the pinned variable font (OFL); Hangul pair reused by path from `../lit-pptx` |
+| body | Archivo 400/700 | LitOpenCode Sans Regular/Bold | as above |
+| machine | MesloLGS NF | LitOpenCode Sans | Meslo fetched at pre-warm with its Apache-2.0 notice, the Apache text and the Vera/Arev notices |
+| pixel | VT323 | Galmuri9 (outline build) | VT323 bundled; Galmuri9 fetched at pre-warm with its OFL text, unmodified |
+| chrome | Silkscreen Regular/Bold (labels only) | none | bundled |
+| stroke | EMS Allure, Felix, Osmotron, Readability, Tech (single-stroke SVG) | none | bundled with the OFL 1.1 text and a CREDITS file |
+
+Every glyph is drawn from its font's outline data, positioned with the font's own advances and
+kerning pairs. The type kit reports each drawn element (bbox after the scene transform and the post
+chain's shake/zoom, font file, size, cap height, weight, fill and per-script runs) so the gate can
+check title-safe, contrast, tracking and Hangul rules without reading pixels.
+
+## Hard rules (the gate enforces the measurable ones)
+
+1. Per-glyph layout (MO-A-32). When a word is drawn in pieces (a karaoke split, a per-letter
+   reveal) piece *i* starts at the glyph position from the whole run's layout. Measuring the prefix
+   substring instead drops the kerning pair between the two pieces.
+2. Hangul is never condensed, stretched or faux-bolded (MO-A-33). Weight steps only between the two
+   static files of the lit-pptx pair, 400 and 700. Width animation is Latin-only.
+3. No Latin-style tracking or width motion on a Hangul script run, even inside a mixed line
+   (MO-FT-04). Script runs split at the script boundary; digits, spaces and punctuation join the
+   adjacent run, falling back to the run on their left between two scripts (so "2026년" is one Hangul
+   run and "LIT팀" is "LIT" plus "팀").
+4. Line breaks and reveal steps fall only between 어절 (MO-A-13, MO-FT-05).
+5. No outlined or haloed type, ever (MO-A-35). Legibility comes from contrast and placement.
+6. Typographic punctuation (MO-A-34): straight quotes and `...` in the brief become curly quotes and
+   an ellipsis; a typed-input voice may switch back.
+7. Tracking (MO-C-25, provisional): display type may tighten to -0.04em and no further; machine and
+   body voices stay at 0 or looser.
+8. Line height (MO-C-26): a block showing two or more lines at once holds at least 1.5 (Latin) or 1.6
+   (Hangul), and at least 1.4 at three or more lines.
+9. Measure (MO-C-27): a Latin paragraph card runs 60-75 characters per line; a Korean paragraph card
+   outside 30-45 characters is an advisory note, not a failure.
+10. Contrast (MO-C-06): body type at least 4.5:1, large type (32 px, or 25 px at weight 700) at least
+    3:1, measured on the rendered frame under the glyph mask against its surroundings; a gradient fill
+    uses its darkest and lightest percentiles.
+11. Title-safe (MO-C-04): every glyph bbox inside 96 px left/right and 54 px top/bottom. Non-glyph
+    elements stay inside the 95% action-safe box (MO-C-05, provisional).
+
+## Guidance (craft defaults, not gate rules)
+
+- Held Hangul body copy at or under about 32 px cap height uses Regular; large kinetic Hangul slams
+  use Bold so thin strokes survive motion blur.
+- Galmuri9 renders crisp at multiples of its 9 px grid and at least 45 px on screen; below that use
+  a Latin pixel voice or plain body type.
+- Keep Galmuri and VT323 on separate lines of a readout; they are never mixed cell for cell.
+- Annotations sit beside large display type, not stacked under it; one idea per shot.
+- The reading floor sets the minimum. A shot that must be read slowly gets more beats, not a smaller
+  font.