@litfamily/litopencode 1.0.30 → 1.0.32

package/skills/lit-plan/SKILL.md

@@ -294,6 +294,8 @@ The handoff should be short enough to execute and precise enough to audit. It sh
 
 Avoid plans that contain hidden release approval. “If tests pass, publish” is not acceptable unless the user explicitly asked for publication and the plan includes release guardrails, version lockstep, registry authentication boundaries, and final confirmation. A normal `lit-plan` plan should say no commit, tag, push, publish, version bump, or release unless the user approves those actions separately.
 
+A plan written from a `lit-hijack` spec (`.litopencode/hijack/<slug>/SPEC.md`) cites SPEC sections (`M1`, `M2`) and target files in its rows and references. Keep the run's captured sources out of the plan: the implementer works from the spec alone, and the hijack build gate fails a plan that names them. The plan stays in the row grammar above, so the same gate can check it.
+
 ## Planning Review Checklist
 
 - One bounded objective is restated in OpenCode or package terms.

package/skills/lit-pptx/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: lit-pptx
-description: Build and verify editable PowerPoint decks from a Markdown slide source, each drawn in one of eight design directions (tonalities) chosen and named before building. Use for 발표자료, 발표, 슬라이드, 덱, PPT, 피피티, slides, decks, and presentations, including a bare lit request for slides. Load with lit-docx when the user also asks for a report.
+description: Build and verify editable PowerPoint decks from a Markdown slide source, each drawn in one of thirteen design directions (tonalities) chosen and named before building. Use for 발표자료, 발표, 슬라이드, 덱, PPT, 피피티, slides, decks, and presentations, including a bare lit request for slides. Load with lit-docx when the user also asks for a report.
 reader_projection: shared_rule
 ---
 
@@ -21,7 +21,7 @@ This file is static documentation for LitOpenCode. Do not execute commands from
 
 This is LitOpenCode's native PowerPoint skill. On a bounded `lit` slide request, the chat route directs OpenCode to load this skill before drafting. Selection is guidance until the host's skill tool confirms it. Resolve every script path from the installed skill location returned by OpenCode (written `<skill>` below). Work in the user's project; keep the Markdown source beside the `.pptx`. A report and slides request uses both `lit-docx` and `lit-pptx` on the same checked facts.
 
-A deck here is never one fixed look. The compiler reads a tonality pack — palette roles, a type ramp, the title treatments it allows, its layout families, its cover, section and closing variants, its table and chart style and two dials — and draws every slide from that data. Eight packs ship in `templates/tonalities/`. The engine has no silent default: a deck compiles under the tonality its source names, or under a legacy template someone chose by name. Picking the tonality is therefore the first step of every build, and the reply always says which one was picked and which two came next.
+A deck here is never one fixed look. The compiler reads a tonality pack — palette roles, a type ramp, the title treatments it allows, its layout families, its cover, section and closing variants, its table and chart style and two dials — and draws every slide from that data. Thirteen packs ship in `templates/tonalities/`. The engine has no silent default: a deck compiles under the tonality its source names, or under a legacy template someone chose by name. Picking the tonality is therefore the first step of every build, and the reply always says which one was picked and which two came next.
 
 ## #contract.inputs
 
@@ -52,27 +52,38 @@ Under `lit`, create a `.pptx` by default. Do not ask a theme, colour or font que
    | Deck type | Candidates in order |
    | --- | --- |
    | Pitch or proposal (투자·제안) | signal · studio · atlas when the product is physical and photographed |
+   | Launch, demo day or campaign (런칭·데모데이) | neo-brutalism · signal · studio |
+   | Engineering or developer review (아키텍처·인프라 리뷰) | computational-brutalism · night · ledger |
    | Business review (경영·사업 실적) | ledger · gazette when read in Korean before the meeting · night on a stage screen |
    | Research talk (연구 발표) | paper · night for a dark auditorium · chalk for a tutorial |
    | Lecture or training (강의·교육) | chalk · paper · studio for a public lecture with pictures |
+   | Design or culture lecture (디자인·건축·전시) | bauhaus · studio · atlas |
    | Data-heavy review | night · ledger · paper for a written analysis |
    | Image-led (product, site, portfolio) | atlas · studio · signal for a launch |
    | Korean text briefing (보고서형 덱) | gazette · ledger |
    | Status update (주간·월간 보고) | ledger · gazette · night |
+   | Community, culture or education programme (커뮤니티·문화·교육 프로그램) | riso · studio · bauhaus for a design programme |
+   | Data story for the public (주민·독자 대상 데이터 브리핑) | newsroom · gazette when read alone · ledger |
 
    | Signal on the outline | Effect |
    | --- | --- |
    | The brief names a tonality or a legacy template | use it; the card still names two alternatives |
+   | The brief names a style: 네오 브루탈리즘 / neo-brutalism; 컴퓨테이셔널 브루탈리즘 / computational brutalism / 레트로 퓨처 / terminal; 바우하우스 / Bauhaus; 리소 / risograph / zine; 뉴스룸 / data journalism / explainer | that pack; a bare 브루탈리즘 / brutalist takes neo-brutalism for a pitch or launch and computational-brutalism for a technical deck |
    | The deck is read rather than presented | gazette (Korean) or ledger moves to the front |
    | A third or more of the slides carry a table / a chart / a picture | ledger or gazette / ledger, night or paper / atlas or studio move up one place |
    | Long slide bodies / short slide bodies | gazette or ledger up / signal or studio up |
    | Citations or a references slide / a definition or a three-step mechanism / a dark room | paper up / chalk or paper up / night up |
+   | Metrics with units, versions or identifiers (p99, rps, v3) / a young or consumer audience with a sign-up ask / works, makers and periods | computational-brutalism up / neo-brutalism up / bauhaus up |
+   | Participants, sessions and dates for a community / charts with one point each for readers outside the field | riso up / newsroom up |
+   | A board, finance, public-sector or sensitive topic | neo-brutalism, computational-brutalism, bauhaus and riso drop out |
    | A pack has no family or title treatment for one of the planned slides | that pack drops out |
 
    The first candidate after reordering wins; the next two are the alternatives. Ties keep the deck-type order, so one source always gets one choice.
+   - **Ask the user to pick the look before step 3.** Unless the prompt already names a tonality or a legacy template, or leaves the look to you ("you choose", "알아서", "아무거나"), call OpenCode's `question` tool once: one question, the winner first labelled `(Recommended)`, then the two alternatives (two to four options in all), each with its one-line character from the tonality table below. Build under the answer and write it on the card. When the session cannot ask (a non-interactive `opencode run`, no `question` tool, or the permission is denied), take the recommended option and say so in one line of the reply. Missing facts are never part of this question; they still get a labelled realistic example.
    - Write the card into the build log beside the source: deck type, reader, the tonality and two alternatives, a one-sentence reason tied to the signals that fired, the dials (density and variance, any move from the pack default; at most 2 per dial without asking), the title treatments by slide role, one layout family per slide, and the line that would make the choice wrong ("if the file is read alone before the meeting, gazette fits better"). Put the tonality in the source frontmatter (`tonality: ledger`).
    - Say it in the reply in two or three plain sentences: the tonality, why, and the two alternatives.
    - **Compare strip.** Only when the user asks to compare, or leaves the look open on purpose ("어떤 느낌이 좋을지 모르겠어", "show me options"): compile the first three slides under the chosen tonality and both alternatives, render and show the three rows, and finish under the one the user picks.
+   - **One slide grid.** Every tonality sets titles, headers and the body on the same zones (`scripts/lib/slide-grid.js`): a content title in columns 1-10 at y 36, the body from y 120 to 486, the footer at y 498, and fixed display and cover zones. A tonality and its treatments change how a zone looks (face, size, colour, rules, bands, fills), never where it is, so switching the tonality never moves the content. A bold register (`register: bold`) sets larger type inside the same zones.
    - **Legacy templates.** `AZURE-PRO`, `AZURE-A2Z`, `BOILERPLATE-PRETENDARD` and `BOILERPLATE-A2Z` keep their names and their single look. Use one only when the user names it or an existing source says `template:`; the reply still offers two tonalities.
 
    | Tonality | Character | Sheet |
@@ -85,8 +96,13 @@ Under `lit`, create a `.pptx` by default. Do not ask a theme, colour or font que
    | `gazette` | Korean briefing pages: header band, boxed summary, itemised evidence | `references/tonalities/gazette.md` |
    | `studio` | editorial grid, asymmetric splits, side titles, part numbers | `references/tonalities/studio.md` |
    | `night` | dark ground and light type for data and technical keynotes | `references/tonalities/night.md` |
+   | `computational-brutalism` | retro-futurist computing: mono titles and figures, grid marks and slide index, ruled tables, a terminal field | `references/tonalities/computational-brutalism.md` |
+   | `neo-brutalism` | loud on purpose: thick black borders, hard offset shadows, flat yellow, blue and pink fills | `references/tonalities/neo-brutalism.md` |
+   | `bauhaus` | elementary geometry on the cover and statements, quiet content pages in black and one red | `references/tonalities/bauhaus.md` |
+   | `riso` | two spot inks on warm paper: teal fields on display slides and data titles, pink for the one figure that matters | `references/tonalities/riso.md` |
+   | `newsroom` | a newspaper graphics desk: black masthead titles, grey charts with one orange series, a source under every figure | `references/tonalities/newsroom.md` |
 
-   `node <skill>/run.mjs compile --list-tonalities` prints the eight beside the legacy templates; `node <skill>/run.mjs compile --list-layouts <tonality>` prints that pack's families with the title treatments each allows there, and its cover, section and closing variants.
+   `node <skill>/run.mjs compile --list-tonalities` prints the thirteen beside the legacy templates; `node <skill>/run.mjs compile --list-layouts <tonality>` prints that pack's families with the title treatments each allows there, and its cover, section and closing variants.
 
 3. **Outline before prose.** One message per slide. A slide title is a topic label that names subject, measure and period ("분기별 방문·대출 추이", "Conversion by feed rate, runs 1-12"), never a sentence ("방문은 늘었고 대출은 제자리다", "Revenue grew 12%") and never a bare "현황". The claim is the first line of the body. A cover title names the topic or product, never a slogan, and a cover subtitle is a label too. Typical shape: cover · where things stand · evidence · options compared · recommendation · next steps · closing; each deck type's sequence is in `references/direction-step.md`. Split a slide that needs more than four groups or about eight lines. Name one layout family per slide by the slide's job (`references/layout-families.md`), never by what the previous slide used; the treatment comes from the pack per slide role (`references/title-treatments.md`), and a per-slide `title:` key may pick another treatment the pack allows when a layout repeats too often.
 
@@ -94,15 +110,15 @@ Under `lit`, create a `.pptx` by default. Do not ask a theme, colour or font que
 
 5. **Write dense, sourced content.** Every pack defaults to density 10, the compact step: 24 pt margins, body 13 pt, table cells 11 pt, sources 9 pt, never below those floors. Each content slide carries its basis, a comparison, the period, and an implication or next action; data slides end with a `출처:` / `Source:` line (and a `주:` / `Note:` line where a definition matters), which the engine sets as a strip on the body floor. Write a real uncertainty once, as a fact about the data or method beside the number it affects; what the deck is not for goes in the reply. References run eight to ten entries. `references/density-and-fill.md` lists what each family needs to fill its body and what the fill policies do when it does not.
 
-6. **Write the Markdown source** as `<name>.md` beside the output, with `tonality:`, `title:` and, for sample content, `notice:` in its frontmatter. `specs/markdown-slide-spec-v2.md` is the dialect contract; open the worked example in `references/examples/` closest to the job before writing. Twelve examples cover all eight tonalities in Korean and English and each compiles and passes the gate as shipped. Pictures are referenced by path from the source folder; the skill ships no images. For a chart or diagram picture on a dark tonality, put its dark variant beside it (`flow.png` and `flow.dark.png`); a dark ground draws the variant. Korean text runs and charts with Korean labels are written as ko-KR, so a renderer applies Korean spacing rules.
+6. **Write the Markdown source** as `<name>.md` beside the output, with `tonality:`, `title:` and, for sample content, `notice:` in its frontmatter. `specs/markdown-slide-spec-v2.md` is the dialect contract; open the worked example in `references/examples/` closest to the job before writing. Seventeen examples cover all thirteen tonalities and the deck types in Korean and English, and each compiles and passes the gate as shipped. The five newest (13 to 17) are Korean decks for the hard-edge and editorial packs. Pictures are referenced by path from the source folder; the skill ships no images. For a chart or diagram picture on a dark tonality, put its dark variant beside it (`flow.png` and `flow.dark.png`); a dark ground draws the variant. Korean text runs and charts with Korean labels are written as ko-KR, so a renderer applies Korean spacing rules.
 
 7. **Compile.** `node <skill>/run.mjs compile deck.md --pptx deck.pptx` (the tonality comes from the frontmatter; `--tonality <id>` overrides it, `--faces a2z` or `faces: a2z` swaps in the bundled A2Z display faces). The log prints the tonality and the treatment chosen for each slide. Faces default to the bundled official Pretendard Regular and Bold; hierarchy comes from size, weight, colour and placement.
 
-8. **Gate.** `node <skill>/run.mjs qa deck.pptx` must exit 0. It reads everything from the OOXML: the layout inventory (text measured with the bundled Pretendard faces against its frame, objects off the canvas), WCAG contrast on the real fill and slide ground (body 4.5:1, large 3:1), overlaps and occlusion, composition (an empty outlined box, a thin body, a table-only deck), anti-slop terms, evidence captions, OOXML integrity, and the craft floor. `scripts/craft_extras.py` checks each slide for one accent colour, a readable measure, right-aligned numeric columns, concentric nested frames, card spacing, gradient text, glow, emoji bullets and empty bands (OF-101 to OF-109). `scripts/deck_output.py` checks the deck as a whole: at least three title treatments on eight or more slides, each drawn as it is named (OF-110); composition variety across content slides (OF-111); the body used, with a deck median empty band of at most 0.20 (OF-112); one title frame per treatment, a bottom title keeping its bottom edge (OF-113); titles and the cover subtitle written as labels, not sentences (OF-114); no region left empty beside a full one, so a bottom title ends on the body floor, a side rail carries the slide's criteria, takeaways or source, a takeaway column runs as long as the visual beside it, no text or picture column of a two-column body leaves more than 40 % of the body empty inside it beside a longer column (a source strip at its foot does not hide the band above it), a title panel is as tall as its text and no plate leaves the page above it open (OF-115); no mostly-white figure picture on a dark ground (OF-117); no bold run-in label running into its sentence without a separator (OF-118; the compiler adds the colon, so a finding means a label set by hand); no count numeral beside an agenda title (OF-119). When two tonalities of one source are offered, run `node <skill>/run.mjs qa deck.pptx --sibling other.pptx`: their skeletons (title zone and column partition per content slide) must differ on at least two content slides, one on a deck of fewer than four (OF-116). HIGH findings fail the gate; MEDIUM findings are advisory; on a legacy template the variety checks are advisory. Every deck-level finding carries a hint. Fix the Markdown source and recompile; never edit a generated deck only to evade the gate. A checker pass is not a visual verdict.
+8. **Gate.** `node <skill>/run.mjs qa deck.pptx` must exit 0. It reads everything from the OOXML: the layout inventory (text measured with the bundled Pretendard faces against its frame, objects off the canvas), WCAG contrast on the real fill and slide ground (body 4.5:1, large 3:1), overlaps and occlusion, composition (an empty outlined box, a thin body, a table-only deck), anti-slop terms, evidence captions, OOXML integrity, and the craft floor. `scripts/craft_extras.py` checks each slide for accent colours (up to four hue families pass, five fail; a pack's `qa:` allowance only widens that), a readable measure, right-aligned numeric columns, concentric nested frames, card spacing, gradient text, glow, emoji bullets and empty bands (OF-101 to OF-109), and that a hard offset shadow appears only in a pack that draws one, never beside soft ones (OF-120). `scripts/deck_output.py` checks the deck as a whole: at least three title treatments on eight or more slides, each drawn as it is named (OF-110); composition variety across content slides (OF-111); the body used, with a deck median empty band of at most 0.20 (OF-112); one title frame for every content title and one for every display title, whatever the treatment (OF-113); titles and the cover subtitle written as labels, not sentences (OF-114); no region left empty beside a full one, so a takeaway column runs as long as the visual beside it, no text or picture column of a two-column body leaves more than 40 % of the body empty inside it beside a longer column (a source strip at its foot does not hide the band above it), a title panel is as tall as its text and no plate leaves the page above it open (OF-115); no mostly-white figure picture on a dark ground (OF-117); no bold run-in label running into its sentence without a separator (OF-118; the compiler adds the colon, so a finding means a label set by hand); no count numeral beside an agenda title (OF-119). When two tonalities of one source are offered, run `node <skill>/run.mjs qa deck.pptx --sibling other.pptx`: both must set every title frame and the body's top-left corner in the same place on every slide (OF-116), because a tonality changes the look, never the place. HIGH findings fail the gate; MEDIUM findings are advisory; on a legacy template the variety checks are advisory. Every deck-level finding carries a hint. Fix the Markdown source and recompile; never edit a generated deck only to evade the gate. A checker pass is not a visual verdict.
 
 9. **Fonts for travel.** When the deck must open on machines without Pretendard, run `node <skill>/run.mjs embed deck.pptx` and rerun the gate. The post-embedding integrity check reopens the deck and verifies ZIP data, content types and relationship targets.
 
-10. **Look at the pages.** Render with LibreOffice when available: `soffice -env:UserInstallation=file:///tmp/<unique-profile> --headless --convert-to pdf --outdir <output-dir> deck.pptx`, convert the PDF to PNG, and open every slide at presentation size. Check hierarchy, Hangul line breaks, numbers against the source, cramped or hollow areas, and whether each treatment suits its slide. Check the card's "wrong if" line: if it came true, rebuild under the alternative and update the card and reply. Three full compile → gate → look rounds is the budget; a defect that survives is named in the reply, not written onto a slide. Without soffice, report that structural QA ran and visual preview was unavailable; never claim render verification.
+10. **Look at the pages.** Render with `node <skill>/run.mjs render deck.pptx --out-dir <output-dir>` when LibreOffice is available: it converts in a private profile, installs the faces the deck embeds (LibreOffice ignores embedded font parts, so JetBrains Mono and Pretendard show only when the helper places them), and writes `<output-dir>/deck.pdf` and `page-01.png` onward when `pdftoppm` is on PATH. Open every slide at presentation size. Check hierarchy, Hangul line breaks, numbers against the source, cramped or hollow areas, and whether each treatment suits its slide. Check the card's "wrong if" line: if it came true, rebuild under the alternative and update the card and reply. Three full compile → gate → look rounds is the budget; a defect that survives is named in the reply, not written onto a slide. Without soffice, report that structural QA ran and visual preview was unavailable; never claim render verification.
 
 11. **Deliver.** The `.pptx`, its Markdown source, the build log with the direction card and, when useful, the rendered PNGs sit in the user's project. The reply names the tonality and the two alternatives. Never leave generated files inside the skill.
 
@@ -114,16 +130,16 @@ For a deck that matters, iterate once before the final compile. The guidance in
 
 ### Design laws for every tonality and template
 
-- One accent colour per slide; a second only when it carries a real pair (a delta, a status).
+- Build a rich slide from the pack's own roles: its accent, series and field colours, a hero step on cover and statement titles that fit, and the pack's decoration. Up to four accent hue families per slide pass and five fail (OF-101); one colour keeps one meaning across the deck. `hero: false` in the front matter is the calm opt-out, and `decoration: numeral, column-hairlines` adds kinds from the shared set.
 - Titles and subtitles are labels; claims live in the body.
-- No hero numerals and no exaggerated figures; every number has its basis and period.
-- Pretendard unless the user asks otherwise; at most the two bundled weights, plus A2Z on request.
+- No exaggerated figures; every number has its basis and period. Only a bold pack (`register: bold`, today neo-brutalism) sets presented type and big figures, inside the same zones; every other figure sits at title size at most.
+- Pretendard unless the user asks otherwise; at most the two bundled weights, plus A2Z on request. computational-brutalism adds the bundled JetBrains Mono for titles, figures and labels (Latin only, Pretendard stays the Korean face, and a mono body face is refused).
 - Text never below the readable floors; nothing outside the safe margins; pictures cropped, never stretched.
 - Variety comes from the slide's job: a deck that repeats one composition on most of its content slides is unfinished.
 
 ## #contract.runtime
 
-The skill ships `package-lock.json` and `requirements.lock` with pinned Node and Python dependencies. `run.mjs` installs on first use under the configured user cache directory (`XDG_CACHE_HOME/litopencode/office` or the normal user cache), never globally or in the OpenCode config. The Python side creates a product-owned venv for `python-pptx`, `defusedxml` and Pillow; the Node side installs `pptxgenjs` and `sharp`. The tonality packs, layout families and treatments are data under `templates/tonalities/`; the renderer is one engine (`scripts/lib/render-pack.js` on the grid of `scripts/lib/grid-resolver.js`) for all of them. The bundled faces are the unmodified official Pretendard 1.3.9 Regular and Bold under the SIL OFL (`pretendard-font/LICENSE.txt`) and the A2Z weights with their OFL and source note. A missing network or package manager is a capability failure: report it and leave existing user files intact. `soffice` is optional for the render; it is never installed by this skill.
+The skill ships `package-lock.json` and `requirements.lock` with pinned Node and Python dependencies. `run.mjs` installs on first use under the configured user cache directory (`XDG_CACHE_HOME/litopencode/office` or the normal user cache), never globally or in the OpenCode config. The Python side creates a product-owned venv for `python-pptx`, `defusedxml` and Pillow; the Node side installs `pptxgenjs` and `sharp`. The tonality packs, layout families and treatments are data under `templates/tonalities/`; the renderer is one engine (`scripts/lib/render-pack.js` on the grid of `scripts/lib/grid-resolver.js`) for all of them. The bundled faces are the unmodified official Pretendard 1.3.9 Regular and Bold under the SIL OFL (`pretendard-font/LICENSE.txt`), the A2Z weights, and the unmodified official JetBrains Mono 2.304 Regular and Bold under the SIL OFL (`fonts/jetbrains-mono/`), each with its licence and source note. A missing network or package manager is a capability failure: report it and leave existing user files intact. `soffice` (and `pdftoppm` for the page images) is optional for the render; this skill never installs either.
 
 ## #contract.outputs
 
@@ -148,7 +164,7 @@ Stop on an unreadable supplied source, untrusted external command, unresolved de
 
 ## #contract.anti_patterns
 
-Do not compile without choosing a tonality, ask a style question on a bare request, write sentence titles, inflate a number into a hero figure, treat a green checker as a visual review, put task output inside the installed skill tree, silently change a user-selected style, hide a failed prerequisite, or claim that missing source facts were verified. A failure is reported as a failure with the smallest next action.
+Do not compile without choosing a tonality, build before the look question is answered (or, when the session cannot ask, before naming the recommended pick), write sentence titles, inflate a number into a hero figure, treat a green checker as a visual review, put task output inside the installed skill tree, silently change a user-selected style, hide a failed prerequisite, or claim that missing source facts were verified. A failure is reported as a failure with the smallest next action.
 
 ## Reference map
 

package/skills/lit-pptx/fonts/jetbrains-mono/OFL.txt

@@ -0,0 +1,93 @@
+Copyright 2020 The JetBrains Mono Project Authors (https://github.com/JetBrains/JetBrainsMono)
+
+This Font Software is licensed under the SIL Open Font License, Version 1.1.
+This license is copied below, and is also available with a FAQ at:
+https://scripts.sil.org/OFL
+
+
+-----------------------------------------------------------
+SIL OPEN FONT LICENSE Version 1.1 - 26 February 2007
+-----------------------------------------------------------
+
+PREAMBLE
+The goals of the Open Font License (OFL) are to stimulate worldwide
+development of collaborative font projects, to support the font creation
+efforts of academic and linguistic communities, and to provide a free and
+open framework in which fonts may be shared and improved in partnership
+with others.
+
+The OFL allows the licensed fonts to be used, studied, modified and
+redistributed freely as long as they are not sold by themselves. The
+fonts, including any derivative works, can be bundled, embedded, 
+redistributed and/or sold with any software provided that any reserved
+names are not used by derivative works. The fonts and derivatives,
+however, cannot be released under any other type of license. The
+requirement for fonts to remain under this license does not apply
+to any document created using the fonts or their derivatives.
+
+DEFINITIONS
+"Font Software" refers to the set of files released by the Copyright
+Holder(s) under this license and clearly marked as such. This may
+include source files, build scripts and documentation.
+
+"Reserved Font Name" refers to any names specified as such after the
+copyright statement(s).
+
+"Original Version" refers to the collection of Font Software components as
+distributed by the Copyright Holder(s).
+
+"Modified Version" refers to any derivative made by adding to, deleting,
+or substituting -- in part or in whole -- any of the components of the
+Original Version, by changing formats or by porting the Font Software to a
+new environment.
+
+"Author" refers to any designer, engineer, programmer, technical
+writer or other person who contributed to the Font Software.
+
+PERMISSION & CONDITIONS
+Permission is hereby granted, free of charge, to any person obtaining
+a copy of the Font Software, to use, study, copy, merge, embed, modify,
+redistribute, and sell modified and unmodified copies of the Font
+Software, subject to the following conditions:
+
+1) Neither the Font Software nor any of its individual components,
+in Original or Modified Versions, may be sold by itself.
+
+2) Original or Modified Versions of the Font Software may be bundled,
+redistributed and/or sold with any software, provided that each copy
+contains the above copyright notice and this license. These can be
+included either as stand-alone text files, human-readable headers or
+in the appropriate machine-readable metadata fields within text or
+binary files as long as those fields can be easily viewed by the user.
+
+3) No Modified Version of the Font Software may use the Reserved Font
+Name(s) unless explicit written permission is granted by the corresponding
+Copyright Holder. This restriction only applies to the primary font name as
+presented to the users.
+
+4) The name(s) of the Copyright Holder(s) or the Author(s) of the Font
+Software shall not be used to promote, endorse or advertise any
+Modified Version, except to acknowledge the contribution(s) of the
+Copyright Holder(s) and the Author(s) or with their explicit written
+permission.
+
+5) The Font Software, modified or unmodified, in part or in whole,
+must be distributed entirely under this license, and must not be
+distributed under any other license. The requirement for fonts to
+remain under this license does not apply to any document created
+using the Font Software.
+
+TERMINATION
+This license becomes null and void if any of the above conditions are
+not met.
+
+DISCLAIMER
+THE FONT SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND,
+EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTIES OF
+MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT
+OF COPYRIGHT, PATENT, TRADEMARK, OR OTHER RIGHT. IN NO EVENT SHALL THE
+COPYRIGHT HOLDER BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY,
+INCLUDING ANY GENERAL, SPECIAL, INDIRECT, INCIDENTAL, OR CONSEQUENTIAL
+DAMAGES, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING
+FROM, OUT OF THE USE OR INABILITY TO USE THE FONT SOFTWARE OR FROM
+OTHER DEALINGS IN THE FONT SOFTWARE.

package/skills/lit-pptx/fonts/jetbrains-mono/SOURCE.md

@@ -0,0 +1,17 @@
+# JetBrains Mono: bundled font source
+
+- Face: JetBrains Mono, Regular 400 and Bold 700, used by the computational-brutalism tonality for Latin text only.
+- Release: v2.304 (official release archive, files shipped unmodified).
+- Repository: https://github.com/JetBrains/JetBrainsMono
+- Release asset: https://github.com/JetBrains/JetBrainsMono/releases/download/v2.304/JetBrainsMono-2.304.zip
+- Archive sha256: `6f6376c6ed2960ea8a963cd7387ec9d76e3f629125bc33d1fdcd7eb7012f7bbf`
+- License: SIL Open Font License 1.1, no Reserved Font Name (`OFL.txt` is the upstream file).
+
+| File | bytes | sha256 |
+|---|---|---|
+| `JetBrainsMono-Regular.ttf` | 273900 | `a0bf60ef0f83c5ed4d7a75d45838548b1f6873372dfac88f71804491898d138f` |
+| `JetBrainsMono-Bold.ttf` | 277828 | `5590990c82e097397517f275f430af4546e1c45cff408bde4255dad142479dcb` |
+| `OFL.txt` | 4399 | `30f0c136e3c88e422d0791acd97238870f9054a9729bc34cf2ff0d4ed8cac4ad` |
+
+The face carries no Hangul. Every mono run is written with `<a:ea typeface="Pretendard">`, so Hangul inside a mono run is set in the
+bundled Pretendard (never subset), and a pack whose `faces.body` is mono is refused by the pack loader.

package/skills/lit-pptx/references/density-and-fill.md

@@ -121,6 +121,12 @@ The second line is the important one. It means the slide is short because the so
 no policy can help. Add the facts the slide is missing (next section) or move the content to a
 family that suits its amount; `layout-families.md` lists what each family expects.
 
+The title treatment never buys the body room: every treatment draws in the slide grid's one title
+zone over the same body (y 120-486), so a short body is filled by its own layout, never by moving the
+title. The engine never pads cards with filler. Decoration (the pack's list plus the deck's
+`decoration:` kinds) adds texture and structure to a full slide; it never stands in for missing
+content.
+
 Some families also spread on their own when the body is short: headed points become rows, agenda
 rows spread down to the floor, timeline room is shared above and below the axis, table takeaways
 move under the table, references spread with rules. These moves never add words.
@@ -231,9 +237,9 @@ takeaway is a bare claim (`늘었음`) with no figure.
 
 ### Numbers stay honest
 
-- No hero numerals. The engine caps every number it sets (KPI values, big-number panels, cover
-  figures, closing keys, section numerals) at the title size of the ramp; do not try to get around
-  that with a `box` or `shape`.
+- No hero numerals. The hero step belongs to cover, section and statement titles that fit it. The engine
+  caps every number it sets (KPI values, big-number panels, cover figures, closing keys, section
+  numerals) at the title size of the ramp; do not try to get around that with a `box` or `shape`.
 - A figure is never larger than the title, and a figure without a basis is not a KPI.
 - Signed deltas carry their sign and unit (`+4.1%`, `−3.6%`, `+0.5%p`, `▲ 12%`). In signal, where
   the accent is red, losses keep the ink colour and rely on the `▼` sign.

package/skills/lit-pptx/references/direction-step.md

@@ -2,7 +2,7 @@
 
 A LitOpenCode deck is drawn from a tonality pack: palette roles, a type ramp, the title treatments
 the pack allows, the layout families it lists, its cover, section and closing variants, and two
-dials. Eight packs ship in `templates/tonalities/`. The engine never guesses a look on its own, so
+dials. Thirteen packs ship in `templates/tonalities/`. The engine never guesses a look on its own, so
 the first decision of every build is which pack to compile under. This file is the procedure for
 making that decision quickly, recording it, and telling the user what was chosen.
 
@@ -42,7 +42,7 @@ can correct it later.
 
 | Fact | What to settle | Why it matters |
 |---|---|---|
-| Deck type | One of the eight types below, or the nearest one | Gives the starting candidate order |
+| Deck type | One of the thirteen types below, or the nearest one | Gives the starting candidate order |
 | Delivery | Spoken in a room, sent ahead and read alone, or both | Read decks favour Gazette and Ledger; stage decks favour Signal and Night |
 | Room | Lit office, screen share, dark hall, printed handout | A dark hall pulls Night forward; print rules Night out |
 | Language | Korean, English or mixed | Korean glyphs take about twice the width of Latin letters, which tightens title budgets |
@@ -50,18 +50,23 @@ can correct it later.
 ## Step 2: start from the deck type
 
 Each deck type has an ordered shortlist. The first entry wins when no signal in step 3 moves it.
-All eight packs default to density 10; the variance shown is each pack's own default.
+All thirteen packs default to density 10; the variance shown is each pack's own default.
 
 | Deck type | First choice | Second | Third |
 |---|---|---|---|
 | Pitch or proposal (투자·제안) | signal (v6) | studio (v8) | atlas (v7) when the product is physical and photographed |
+| Launch, demo day or campaign (런칭·데모데이·캠페인) | neo-brutalism (v7) | signal (v6) | studio (v7) |
+| Engineering or developer review (아키텍처·인프라·장애 리뷰) | computational-brutalism (v7) | night (v6) for a stage | ledger (v5) when it is read alone |
 | Management review (경영·사업 실적) | ledger (v5) | gazette (v4) when circulated in Korean before the meeting | night (v6) when presented on a stage screen |
 | Research talk (연구 발표) | paper (v5) | night (v6) for a large dark auditorium | chalk (v6) for a tutorial-style talk |
 | Lecture or training (강의·교육) | chalk (v6) | paper (v5) | studio (v8) for a public lecture with images |
+| Design or culture lecture (디자인·건축·전시·워크숍) | bauhaus (v7) | studio (v8) | atlas (v7) when the works are the deck |
 | Data review (데이터·지표 리뷰) | night (v6) | ledger (v5) | paper (v5) when the review is a written analysis |
 | Image-led showcase (제품·현장·포트폴리오) | atlas (v7) | studio (v8) | signal (v6) for a launch moment |
 | Korean reading brief (보고서형 덱) | gazette (v4) | ledger (v5) | none |
 | Status update (주간·월간 보고) | ledger (v5) | gazette (v4) | night (v6) |
+| Community, culture or education programme (커뮤니티·문화·교육 프로그램) | riso (v7) | studio (v7) | bauhaus (v7) for a design programme |
+| Data story for the public (주민·독자 대상 데이터 브리핑) | newsroom (v6) | gazette (v4) when it is read alone | ledger (v5) |
 
 A request that fits none of these takes the nearest type, and the card says "other, treated as
 status update" or similar.
@@ -75,6 +80,7 @@ in this order; ties keep the deck-type order, so the same source always lands on
 | Rule | Fires when | Move |
 |---|---|---|
 | Named by the user | The brief or an earlier turn names a tonality | Use it. Still write the card and still name two alternatives |
+| Named by style | 네오 브루탈리즘, neo-brutalism; 컴퓨테이셔널 브루탈리즘, computational brutalism, 레트로 퓨처, terminal look; 바우하우스, Bauhaus; 리소, risograph, zine; 뉴스룸, data journalism, explainer | That pack, as if named. A bare 브루탈리즘 or brutalist takes neo-brutalism for a pitch or launch and computational-brutalism for a technical deck, and the card says which reading it took |
 | Legacy template named | The brief names AZURE-PRO, AZURE-A2Z, BOILERPLATE-PRETENDARD or BOILERPLATE-A2Z | Compile with `--template` as named; offer two tonalities as alternatives |
 | Read, not presented | "미리 배포", "보고서", "sent ahead", "for the board pack" | gazette to the front for Korean, ledger otherwise |
 | Table-heavy | 30 % or more of slides hold a table | ledger or gazette up one place |
@@ -85,6 +91,12 @@ in this order; ties keep the deck-type order, so the same source always lands on
 | Citations | numbered references, DOIs, a references slide | paper up one place |
 | Teaching shape | definitions, equations, or a how-it-works sequence of three or more steps | chalk or paper up one place |
 | Dark room | keynote hall, demo day, stage | night up one place |
+| Technical metrics | units, versions or identifiers (p99, rps, v3, endpoint names) on a third of the content slides | computational-brutalism up one place |
+| Young or consumer audience | stated in the brief, or a sign-up or launch ask | neo-brutalism up one place |
+| Works and makers | works, makers, periods or schools as the subject, on a third of the content slides | bauhaus up one place |
+| Programme facts | participants, sessions, dates and places for a community or a class, on a third of the content slides | riso up one place |
+| Readers outside the field | charts with one point each for residents, members or the press | newsroom up one place |
+| Sensitive reader | a board, investor committee, finance or public-sector reader, or a topic such as loss, safety or HR | neo-brutalism, computational-brutalism, bauhaus and riso drop out |
 | Missing carrier | the pack has no family or title that can carry a planned slide | drop that pack from the shortlist |
 
 The last rule overrides taste. The packs differ in what they can draw:
@@ -186,7 +198,7 @@ word. `node <skill>/run.mjs compile` prints the dials it used on its first line
 
 Two neighbouring keys are not dials but belong to the same decision:
 
-- `canvas: 4:3` switches every pack to its 4:3 grid (all eight list both canvases);
+- `canvas: 4:3` switches every pack to its 4:3 grid (all thirteen list both canvases);
 - `faces: a2z` (or `--faces a2z`) switches the display and numeral faces to A2Z. Pretendard is the
   default in every pack, and A2Z is used only when the user asks for it.
 
@@ -245,5 +257,8 @@ reply still names two tonalities as alternatives.
 - `layout-families.md`: what each family holds and what the source must contain for it.
 - `density-and-fill.md`: the density steps, readable floors, fill policies and what to write per
   slide so the gate passes on substance rather than padding.
-- `examples/`: twelve compiled decks across all eight packs, each passing
-  `node <skill>/run.mjs qa`.
+- `examples/`: seventeen compiled decks across all thirteen packs, each passing
+  `node <skill>/run.mjs qa`. The newest five are Korean decks: `13-engineering-review-computational-brutalism-ko.md`
+  (alternatives night, ledger), `14-launch-pitch-neo-brutalism-ko.md` (signal, studio),
+  `15-design-lecture-bauhaus-ko.md` (studio, atlas), `16-community-programme-riso-ko.md` (studio,
+  bauhaus) and `17-public-data-briefing-newsroom-ko.md` (gazette, ledger).

package/skills/lit-pptx/references/examples/04-lecture-chalk-ko.md

@@ -49,17 +49,14 @@ layout: method
 ΔT = K · W / (M · (100 − W))
 
 - **ΔT** 하이드레이트 생성 온도가 내려가는 폭, 단위 °C
-  (1) 무억제 생성 온도에서 운전 온도를 뺀 값에 안전 여유 2~3°C를 더함
+  (1) 무억제 생성 온도에서 운전 온도를 뺀 값에 여유 2~3°C를 더함
   (2) 예: 생성 14°C, 운전 4°C, 여유 0°C이면 ΔT는 10°C
 - **K** 억제제 상수
-  (1) 메탄올과 글라이콜 모두 1,297을 흔히 사용
-  (2) 교재에 따라 1,228~2,335까지 다른 값을 쓰므로 출처를 함께 적음
+  (1) 메탄올과 글라이콜 모두 1,297을 흔히 사용, 출처를 함께 적음
 - **W** 수용액 속 억제제 질량 백분율, 단위 wt%
-  (1) 수상 기준 값이며 기상으로 날아가는 양은 포함하지 않음
-  (2) 약 25wt% 이하에서 오차 10% 안쪽
+  (1) 수상 기준 값이며 약 25wt% 이하에서 오차 10% 안쪽
 - **M** 억제제 분자량
   (1) 메탄올 32.04, MEG 62.07, DEG 106.12
-  (2) 분자량이 클수록 같은 ΔT에 더 높은 농도가 필요
 - **적용 한계** 식이 맞는 범위
   (1) 농도 25wt% 이하, 압력 20MPa 이하의 메탄 위주 가스
   (2) 염분이 섞인 생산수는 염의 효과를 따로 더해야 함

package/skills/lit-pptx/references/examples/05-research-talk-paper-en.md

@@ -33,17 +33,13 @@ layout: method
 r = k · p_CO2^a · p_H2^b / (1 + K_H2O · p_H2O)
 
 - **r** CO2 consumption rate
-  (1) mol per gram of surface Ni per second
-  (2) measured below 10% conversion so the bed stays differential
+  (1) mol per gram of surface Ni per second, below 10% conversion
 - **k** rate constant
   (1) Arrhenius form, k = A · exp(−Ea / RT)
-  (2) apparent Ea compared across the five catalysts
 - **a, b** reaction orders in CO2 and H2
   (1) a between 0.21 and 0.34, b between 0.48 and 0.62
-  (2) fitted at fixed temperature, varying one partial pressure at a time
 - **K_H2O** water adsorption term
   (1) accounts for product inhibition above 220 °C
-  (2) held at one value per catalyst across temperatures
 - **Fit** least squares over 42 runs at 180-260 °C
   (1) R² = 0.97, residuals without trend in temperature
 - Note: rates are normalised by surface Ni from H2 chemisorption

package/skills/lit-pptx/references/examples/08-reliability-keynote-night-en.md

@@ -114,16 +114,12 @@ budget = (1 − SLO) × total requests in the window
 
 - **SLO** service level objective
   (1) 99.95% of checkout requests succeed over a rolling 28 days
-  (2) a request fails on a 5xx response or a response slower than 3 s
 - **Window** rolling 28 days
   (1) about 410M checkout requests at current volume
-  (2) recomputed every five minutes from the request log
 - **Budget** failed requests the window may hold
   (1) 0.05% of 410M, about 205,000 requests
-  (2) the May incident alone used 31% of one window
 - **Burn rate** speed of spending the budget
   (1) failed requests per hour divided by the hourly budget
-  (2) a burn rate of 1 spends the budget exactly at the window's end
 - **Alert** paging rule
   (1) page when the 1-hour burn rate exceeds 14 or the 6-hour rate exceeds 6
 - Source: Example Commerce SLO policy v3, February 2026

package/skills/lit-pptx/references/examples/09-status-update-ledger-en.md

@@ -1,6 +1,6 @@
 ---
 tonality: ledger
-title: Finance system migration, week 40 status
+title: Finance migration, week 40 status
 subtitle: Cutover readiness, open defects and budget to date
 date: 2026-10-06
 department: Example Manufacturing finance programme
@@ -9,7 +9,7 @@ notice: Sample data for illustration only
 ---
 layout: cover-typographic
 
-# Finance system migration, week 40 status
+# Finance migration, week 40 status
 ---
 layout: kpi-row
 

package/skills/lit-pptx/references/examples/11-forecast-review-night-ko.md

@@ -99,21 +99,18 @@ layout: big-number
 - 출처: 예시 전력거래 분석팀 사후 분석 보고(2026년 7월 28일)
 ---
 layout: method
-title: band
+title: side-rail
 
 ## 앙상블 가중치 산정 방식
 
 ŷ = w1 · 기온회귀 + w2 · 부스팅 + w3 · 신경망
 
 - **기온회귀** 기온·습도·요일 변수 회귀
-  (1) 폭염과 한파 구간에서 안정적이지만 평상시 정밀도가 낮음
-  (2) 가중치 0.2~0.5
+  (1) 폭염과 한파 구간에서 안정적, 가중치 0.2~0.5
 - **부스팅** 그래디언트 부스팅 모델
-  (1) 평일 평상 기온에서 오차가 가장 작음
-  (2) 가중치 0.3~0.6
+  (1) 평일 평상 기온에서 오차가 가장 작음, 가중치 0.3~0.6
 - **신경망** 순환 신경망 모델
-  (1) 공휴일 전후 패턴 학습에 강점
-  (2) 가중치 0.1~0.3
+  (1) 공휴일 전후 패턴 학습에 강점, 가중치 0.1~0.3
 - **가중치 갱신** 최근 28일 오차로 매주 월요일 재계산
   (1) 가중치 합은 항상 1, 한 번에 0.1 이상 바꾸지 않음
   (2) 폭염 특보가 있는 날은 기온회귀 가중치를 0.5로 고정