@litfamily/litgrok 1.0.26 → 1.0.28

package/.grok/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/.grok/skills/lit-pptx/fonts/jetbrains-mono/provenance.json

@@ -0,0 +1 @@
+{"files": [{"bytes": 273900, "coverage": "static TTF; Latin coverage checked", "file": "JetBrainsMono-Regular.ttf", "sha256": "a0bf60ef0f83c5ed4d7a75d45838548b1f6873372dfac88f71804491898d138f"}, {"bytes": 277828, "coverage": "static TTF; Latin coverage checked", "file": "JetBrainsMono-Bold.ttf", "sha256": "5590990c82e097397517f275f430af4546e1c45cff408bde4255dad142479dcb"}, {"bytes": 4399, "file": "OFL.txt", "sha256": "30f0c136e3c88e422d0791acd97238870f9054a9729bc34cf2ff0d4ed8cac4ad"}], "license": "SIL Open Font License 1.1", "release": "v2.304", "releaseArchive": "https://github.com/JetBrains/JetBrainsMono/releases/download/v2.304/JetBrainsMono-2.304.zip", "repository": "https://github.com/JetBrains/JetBrainsMono", "sourcePath": "fonts/ttf/JetBrainsMono-Regular.ttf, fonts/ttf/JetBrainsMono-Bold.ttf"}

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

@@ -1,15 +1,17 @@
 # Direction step
 
 A deck's look is decided once, before the first slide is written, and it is decided as data: one of
-the eight tonality packs in `templates/tonalities/<id>/pack.yaml`. The pack fixes the palette roles,
+the thirteen tonality packs in `templates/tonalities/<id>/pack.yaml`. The pack fixes the palette roles,
 the type ramp, the title treatments each slide role may take, the layout families the engine will
 draw, the cover, section and closing variants, and the density and variance dials. Skipping this
 step leaves the engine without a design and the deck without a reason for looking the way it does.
 
 The step produces three things: a direction card in the build log, a `tonality:` line in the deck
-frontmatter, and two or three sentences in the reply that name the choice and two alternatives. A
-bare request (`lit 발표자료 만들어줘`, "make me a deck on X") asks the user nothing. The skill
-infers what it needs, writes the inference on the card, and lets the user correct it afterwards.
+frontmatter, and two or three sentences in the reply that name the choice and two alternatives.
+Before building, ask the user to choose the tonality with a numbered choice in the reply
+(recommended first); skip only when the brief names it or says you choose. When the brief leaves
+the look open on purpose, also render a compare strip of the first three slides under the chosen
+tonality and both alternatives and build the rest under the one picked.
 
 ## What to settle first
 
@@ -23,9 +25,10 @@ and the sources when it does not.
 | Delivery | Presented live, read alone, or both? | "미리 배포", "보고서형", "circulate" → read; "keynote", "demo day" → presented |
 | Language | Korean, English or mixed? | the language of the request, unless the sources or the user say otherwise |
 
-Pretendard Regular and Bold are the only faces this skill ships. Every pack draws with them, so the
+Pretendard Regular and Bold are the faces every pack draws with, so the
 direction never depends on a font the machine might lack. Hierarchy comes from size, weight, colour
-and placement.
+and placement. One pack adds a second face: Computational Brutalism sets Latin titles, labels and
+figures in the bundled JetBrains Mono (Hangul stays Pretendard); body text stays Pretendard in every pack.
 
 ## Candidates by deck type
 
@@ -34,9 +37,14 @@ Start from the row for the deck type. The first name is the default when no sign
 | Deck type | First choice | Second | Third, and when |
 |---|---|---|---|
 | Pitch (투자·제안) | signal | studio | atlas, when the product is a physical thing to show |
+| Launch, demo day or campaign (런칭·데모데이·캠페인) | neo-brutalism | signal | studio |
+| Engineering or developer review (아키텍처·인프라·장애 리뷰) | computational-brutalism | night, for a stage screen | ledger, when it is read alone |
 | Business review (실적 보고) | ledger | gazette, when circulated in Korean before the meeting | night, when shown on a stage screen |
 | Research talk (연구 발표) | paper | night, for a keynote hall | chalk, for a tutorial |
 | Lecture (강의·교육) | chalk | paper | studio, for a public lecture |
+| Design or culture lecture (디자인·건축·전시·워크숍) | bauhaus | studio | atlas, when the works are the deck |
+| Community, culture or education programme (커뮤니티·문화·교육 프로그램) | riso | studio | bauhaus, for a design programme |
+| Data story for the public (주민·독자 대상 데이터 브리핑) | newsroom | gazette, when it is read alone | ledger |
 | Data-heavy review (데이터 리뷰) | night | ledger | paper, for a written analysis |
 | Image-led (제품·현장·포트폴리오) | atlas | studio | signal, for a launch |
 | Korean briefing (보고서형 덱) | gazette | ledger | — |
@@ -53,6 +61,7 @@ choice.
 |---|---|---|
 | User's choice | the brief or an earlier turn names a tonality | use it, still write the card |
 | Named template | the brief names an enrolled template such as AZURE-PRO | use that template, offer two tonalities as alternatives |
+| Named style | the brief names a style rather than a pack id: 네오 브루탈리즘, neo-brutalism; 컴퓨테이셔널 브루탈리즘, computational brutalism, 레트로 퓨처, retro-futurist, 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 |
 | Read, not presented | the brief says the file is sent ahead or filed | gazette (Korean) or ledger (any language) moves to first |
 | Tables | 30 % or more of content slides hold a table | ledger and gazette up one place |
 | Charts | 30 % or more hold a chart | ledger, night and paper up one place |
@@ -62,6 +71,12 @@ choice.
 | Citations | numbered references, DOIs or a references slide | paper up one place |
 | Teaching structure | definitions, a formula, or a sequence of three or more steps taught in order | chalk up one place, paper up one |
 | Dark room | keynote, stage, demo day | night up one place |
+| Metrics, versions or identifiers | p99, rps, v3 or endpoint names on a third of the content slides | Computational Brutalism up one place |
+| Young or consumer audience | a sign-up or launch ask, stated in the brief | Neo-Brutalism up one place |
+| Works, makers or periods | the subject of a third of the content slides | Bauhaus up one place |
+| Participants, sessions and dates | a community or a class, on a third of the content slides | Riso up one place |
+| One-point charts for outsiders | charts with one point each for readers outside the field, stated in the brief | Newsroom up one place |
+| Board, finance or sensitive topic | a board, investor committee, finance or public-sector reader, or a sensitive topic (loss, safety, HR), stated in the brief | Neo-Brutalism, Computational Brutalism, Bauhaus and Riso drop out |
 | Coverage gap | a pack has no family for a slide the outline needs | drop that pack |
 
 The coverage row decides more often than it seems. Read `--list-layouts <id>` against the outline:
@@ -76,6 +91,11 @@ The coverage row decides more often than it seems. Read `--list-layouts <id>` ag
 | gazette | charts, pictures |
 | studio | tables |
 | night | tables (KPI rows and charts only), pictures, running text |
+| computational-brutalism | pictures, agenda, timelines |
+| neo-brutalism | timelines, running text |
+| bauhaus | picture-led decks (image-split only), dashboard grids |
+| riso | dashboard grids, reference appendices |
+| newsroom | agenda, process steps |
 
 A ten-slide deck with four charts cannot be a chalk or gazette deck, however well the rest fits. A
 deck with a 2×2 option matrix needs ledger or gazette.
@@ -174,7 +194,7 @@ pick becomes the card's reason ("chosen from the comparison"); then build the fu
 ## Enrolled templates
 
 The templates in `templates/enrolled/` keep their single fixed look. `--list-tonalities` lists them
-as legacy templates after the eight packs. Use one only when the user names it or an existing source
+as legacy templates after the thirteen packs. Use one only when the user names it or an existing source
 already says `template:`. The card names the template, the reply still offers two tonalities, and
 the gate reports its variety and band checks as advisories, because a named template asks for one
 look on purpose.
@@ -191,7 +211,7 @@ look on purpose.
 
 ## Example decks
 
-Twelve complete decks live in `examples/`, each verified to compile and pass the gate under its
+Seventeen complete decks live in `examples/`, each verified to compile and pass the gate under its
 pack. Open the one whose deck type and language match the job before drafting. The picture slides name `assets/example-a.png`, `assets/example-b.png` and
 `assets/example-c.png`; put real images at those paths, or change the paths, before compiling.
 
@@ -208,4 +228,10 @@ pack. Open the one whose deck type and language match the job before drafting. T
 | `09-pitch-studio-en.md` | pitch for a physical product | studio | signal, atlas |
 | `10-image-led-studio-ko.md` | image-led portfolio | studio | atlas, signal |
 | `11-business-review-night-en.md` | business review on a stage screen | night | ledger, gazette |
+| `12-status-update-gazette-ko.md` | status update | gazette | ledger, night |
+| `13-engineering-review-computational-brutalism-ko.md` | engineering review | computational-brutalism | night, ledger |
+| `14-launch-pitch-neo-brutalism-ko.md` | launch pitch | neo-brutalism | signal, studio |
+| `15-design-lecture-bauhaus-ko.md` | design lecture | bauhaus | studio, atlas |
+| `16-community-programme-riso-ko.md` | community programme | riso | studio, bauhaus |
+| `17-public-data-briefing-newsroom-ko.md` | data story for residents | newsroom | gazette, ledger |
 | `12-status-update-gazette-ko.md` | status update, circulated in Korean | gazette | ledger, night |

package/.grok/skills/lit-pptx/references/tonalities/bauhaus.md

@@ -0,0 +1,140 @@
+# Bauhaus
+
+Bauhaus is the direction for a talk about making things: design, architecture, craft, art history,
+culture. Its display slides carry an elementary composition, a yellow square, a red circle, a black
+bar and a blue triangle set on the grid, beside a heavy title on an off-white ground. The content
+slides are quiet on purpose: black type, a short red rule under each title, open tables and one red
+accent. The geometry is the voice, so it appears where the deck speaks (the cover and the
+statements) and stays out of the pages where the audience reads.
+
+## When to use it
+
+Reach for Bauhaus for a design or architecture lecture, a museum or exhibition opener, a workshop on
+brand or product design, a culture programme, a portfolio review for a design school, or a talk on
+the history of a style. The content signals that point here are images and few numbers, a sequence
+of ideas or periods, quotations from makers, and words such as 디자인, 건축, 전시, 워크숍, 바우하우스,
+Bauhaus, modernism or "primary colours". It is the first candidate for a design or culture lecture,
+before Studio, and the second for a creative workshop.
+
+## When it is the wrong choice
+
+It fails for a data-heavy business review, finance, a public-sector report and any deck where tables
+make up a third of the slides: the display geometry has nothing to say about a ledger. It is wrong
+for grief, safety or financial-loss topics, where primary colours read as careless. For a deck that
+is mostly pictures, Atlas or Studio frames them better; for a pitch, Signal or Neo-Brutalism.
+
+## Tokens
+
+The values below come from the pack file and are what the engine draws.
+
+| Token | Value |
+|---|---|
+| ground / surface | #F4F1EA / #E8E3D6 |
+| ink / ink-muted / line | #141414 / #4A4740 / #141414 |
+| accent / accent-deep / accent-tint | #C8261C / #7A140E / #F2C230 (the yellow of the geometry) |
+| field / on-field | #1F3C99 / #FFFFFF |
+| positive / negative | #1E6B3A / #141414 |
+| series | #C8261C, #1F3C99, #141414, #9E7700 |
+| faces | Pretendard Bold for display, title, labels and numerals, Pretendard Regular for body; `faces: a2z` swaps to A2Z Black display, titles and numerals |
+| ramp / hero | compact (body 13 pt, labels 11, sources 9) / hero step (60 pt) on cover and statement titles that fit, off with `hero: false`; figures at most title size |
+| density / variance | 10 / 7 |
+| radius / edge | 0 / fill |
+| decoration | a short accent rule under top titles, kicker numerals, colour fields |
+| table | open, no header fill, a rule under the header, bold totals |
+| chart | no gridlines, direct labels, the accent on the highlighted series over muted ones |
+
+Density 10 sets the lecture on the compact grid (24 pt side margins), body 13 pt and no step-up, as
+every pack in the family. The fourth series colour
+is the geometry's yellow darkened to an ochre so a bar still holds 3:1 on the ground; the bright
+yellow itself is kept for fills (the square, the notice tag, a highlighted table row), never for text.
+A loss uses ink with a ▼ sign.
+
+## QA allowances
+
+Red, blue and yellow sit side by side on a cover, statement or content slide inside the default
+OF-101 limit (four hue families; a fifth fails), so this pack needs no `qa:` allowance.
+
+## Treatments by slide role
+
+Content, data and reference slides take `top-rule` (the title over a short red rule); data with a
+takeaway and definitions take `side-rail`; sequences `kicker-numeral`; image slides `bottom-anchor`;
+statements `statement`. The engine lays out every treatment the family allows, keeps the role's own
+when the body fills, and otherwise takes the one that leaves the least empty band. Force one with
+`title: <id>` on the line after `layout:`.
+
+## Families and variants
+
+- `asymmetric-feature` and `image-split` pair a work or a building with what to see in it.
+- `timeline` places periods, schools or projects in order.
+- `process` and `step-diagram` set a making process in three to five steps.
+- `comparison` and `text-two-column` read two works, two periods or two methods side by side.
+- `big-number`, `kpi-row`, `chart-insight` and `table-insight` carry the few figures such a talk has.
+- `quote` sets a maker's sentence; `statement` holds one idea at display size.
+- `agenda` opens a workshop with its sessions.
+
+Covers are `cover-typographic`, `cover-split-field` and `cover-numeral`; sections are
+`section-field` and `section-numeral`; closings are `closing-ask`, `closing-summary-list` and
+`closing-statement`.
+
+Display slides. The typographic cover sets the topic at display size on the left half and the
+composition on the right half: the yellow square and red circle above, the black bar and blue
+triangle below, each in its own grid cell. A statement sets its sentence on the left and a narrower
+composition from column 10 to the edge. A big number is a blue field panel. A closing's next step
+stands between two rules; a closing statement takes the statement's composition.
+
+## Do
+
+- Keep the geometry on the cover and the statements; content slides carry type, images and data.
+- Use one statement per section at most, so the composition stays an event.
+- Caption every work with maker, year and source.
+- Let red mark one word or one figure on a content slide.
+
+## Avoid
+
+- Circles, squares or triangles as bullets, icons or frames on content slides.
+- Yellow text on the off-white ground.
+- A fifth hue family beside the three primaries and the ink.
+- This direction for a ledger, a finance review or a sensitive topic.
+
+## Two worked slides
+
+A lecture slide pairs a building with what to see in it, and lets the caption carry the source.
+
+```markdown
+---
+layout: image-split
+
+## 데사우 교사(校舍)의 세 가지 설계 원칙
+
+![도 1. 데사우 교사 전경 | 출처: 예시 이미지](assets/example-a.png)
+
+- **기능별 동** 공방, 교실, 기숙사를 각각의 동으로 나눠 다리로 잇는다
+- **유리 커튼월** 공방 동의 외벽 전체가 유리라 작업이 밖에서 보인다
+- **비대칭 배치** 정면이 없어, 걸으며 돌아봐야 전체가 읽힌다
+- 출처: 예시 건축사 강의 자료, 2026년 (예시)
+---
+```
+
+A timeline places the school's three sites in order, with what changed at each.
+
+```markdown
+---
+layout: timeline
+
+## 학교의 세 시기, 1919-1933년
+
+| 시점 | 장소 | 무엇이 바뀌었나 |
+|---|---|---|
+| 1919년 | 바이마르 | 공방 중심 교육, 표현주의의 영향이 강하다 |
+| 1925년 | 데사우 | 산업 생산과의 협업, 표준화된 제품 디자인 |
+| 1932년 | 베를린 | 사립 학교로 축소, 이듬해 문을 닫는다 |
+
+> 표 1. 바우하우스의 세 시기 (예시 자료)
+
+- 출처: 예시 디자인사 강의 노트, 2026년 (예시)
+---
+```
+
+## Examples
+
+`15-design-lecture-bauhaus-ko.md`

package/.grok/skills/lit-pptx/references/tonalities/computational-brutalism.md

@@ -0,0 +1,150 @@
+# Computational Brutalism
+
+Computational Brutalism is the direction for a deck about a system, told to the people who build or
+run it. It borrows from terminals, plotter paper and engineering drawings: the twelve-column grid is
+marked in the top margin with numbered ticks, every content slide carries its index as `[03/08]`,
+titles, labels and figures are set in a monospaced face, tables are ruled on every edge, and one
+electric-blue signal colour marks the figure that matters. The structure is shown on purpose. What
+keeps it readable is that body text stays in Pretendard and every mark sits on the grid it shows.
+
+## When to use it
+
+Reach for Computational Brutalism for an architecture review, an infrastructure or reliability
+report, a developer-tool or AI-system launch given to engineers, a benchmark write-up, an incident
+retrospective or a hackathon demo. The content signals that point here are metrics with units
+(p99 latency, throughput, error budget, GPU hours), version numbers and identifiers, code or
+command names in the text, before-and-after measurements, and an audience that reads a table
+faster than a sentence. It is the first candidate for an engineering review or a developer launch,
+and the second for a data review that an engineering team will read.
+
+## When it is the wrong choice
+
+It fails for a board, an investor committee, finance or a public-sector report, where the grid marks
+read as unfinished work rather than as a style. It fails for a long Korean reading deck: the mono
+face sets only Latin and figures, so a page of Hangul titles loses most of the look while keeping
+its cost in width. It also fails for consumer marketing, for grief, safety or HR topics, and for a
+deck under a corporate brand guide. For a quiet data review choose Ledger or Night; for a pitch to
+investors, Signal or Neo-Brutalism.
+
+## Tokens
+
+The values below come from the pack file and are what the engine draws.
+
+| Token | Value |
+|---|---|
+| ground / surface | #EEEDE7 / #E2E1D9 |
+| ink / ink-muted / line | #111111 / #4D4C47 / #9A988F |
+| accent / accent-deep / accent-tint | #1F43E0 / #14267A / #D9DEF2 |
+| field / on-field | #111111 / #8CF5A6 (phosphor green on the terminal field) |
+| positive / negative | #1C6B35 / #B3261E |
+| series | #1F43E0, #111111, #7A786F |
+| faces | JetBrains Mono Bold for display, title and numerals, JetBrains Mono Regular for labels, Pretendard Regular for body; Hangul inside a mono run is set in Pretendard; there is no A2Z map, so `faces: a2z` keeps these faces |
+| ramp / hero | compact (body 13 pt, labels 11, sources 9) / hero step (60 pt) on cover and statement titles that fit, off with `hero: false`; figures at most title size |
+| density / variance | 10 / 7 |
+| radius / edge | 0 / border, 1 pt, in ink |
+| decoration | hairline rules, column hairlines, outlined boxes, grid marks, kicker numerals |
+| table | ruled grid on every cell edge, header in the label face, bold totals |
+| chart | hairline gridlines, direct labels, the accent on the highlighted series over muted ones |
+
+Density 10 sets the deck on the compact grid (24 pt side margins), body 13 pt and no step-up, as
+every pack in the family: an engineering review is read again after the meeting, so each slide keeps
+its basis and its source. The mono face is wider than Pretendard, so the engine measures
+every mono title at its own width before it chooses a treatment; a long Latin title moves to a
+treatment with a wider frame rather than shrinking.
+
+The fonts ship with the skill: JetBrains Mono is under the SIL Open Font License 1.1 with no Reserved
+Font Name, and the official Regular and Bold files are embedded unmodified with `--embed-fonts`.
+
+## Treatments by slide role
+
+Content, data, sequence and reference slides take `top-rule`; data with a takeaway takes
+`bottom-anchor`; image slides `bottom-anchor`; definitions `side-rail`; statements `statement`. The
+pack also pins a family's own title: `chart-insight` under `top-rule`, `table-insight` under
+`bottom-anchor`, `comparison` as a spec sheet under a `side-rail` title, and `step-diagram`
+under a large mono headline (`top-plain-large`). The engine lays out each allowed treatment, keeps
+the pinned or role treatment when the body fills, and otherwise takes the one that leaves the least
+empty band. Force one with `title: <id>` on the line after `layout:`.
+
+## Families and variants
+
+- `dashboard-grid` and `kpi-row` carry measured results: value, unit, label and basis in each cell.
+- `chart-insight` and `full-chart` show a measured series with one highlighted line or bar.
+- `table-insight` and `ledger-table` hold benchmark or capacity tables, ruled on every edge.
+- `method` sets a pipeline or procedure as numbered stages with their inputs and outputs.
+- `step-diagram` is a rollout or migration in three to five steps.
+- `matrix-2x2` places options on two measured axes.
+- `comparison` reads before and after, or two designs, across shared rows.
+- `text-two-column` and `references-appendix` carry specifications and links.
+- `quote` and `statement` hold one line an engineer said or one decision.
+
+Covers are `cover-typographic`, `cover-index` and `cover-figures`; sections are `section-numeral`
+and `section-rule`; closings are `closing-decision-box`, `closing-ask` and `closing-summary-list`.
+
+Display slides. The typographic cover is the terminal field from edge to edge: black, with the
+topic in phosphor green at display size, anchored low, and the date line above it. A statement sets
+its sentence in phosphor on the same black field. A big number is an outlined panel on the ground.
+A closing's decision sits in an outlined box. The grid marks and the slide index run on content
+slides only; a drenched statement goes without them.
+
+## Do
+
+- Give every figure its unit and its basis: `p99 182 ms`, `2026년 9월 기준`.
+- Keep identifiers, versions and commands in the text as they are written; the mono face is for them.
+- Put one blue figure on a slide; everything else stays ink.
+- Rule a table on every edge and right-align its numbers.
+- End on a decision box or an ask with the owner and the date.
+
+## Avoid
+
+- Body paragraphs in the mono face (the pack refuses a mono body).
+- Fake code, fake terminal prompts or decorative binary strings; show real identifiers or none.
+- Grid marks or the slide index in the accent colour.
+- A second accent colour; the phosphor green belongs to the black field only.
+- This direction for a board pack, a finance report or a sensitive topic.
+
+## Two worked slides
+
+A latency review shows the measured result with its basis, and lets the table carry the detail.
+
+```markdown
+---
+layout: kpi-row
+
+## API 게이트웨이 v3 전환 결과, 2026년 9월
+
+| p99 지연 | 처리량 | 오류율 | 노드 수 |
+|---|---|---|---|
+| 182 ms | 41k rps | 0.07% | 24 |
+| v2 410 ms | v2 18k rps | v2 0.31% | v2 40 |
+
+> 운영 클러스터 4주 평균, 2026년 9월 (예시)
+
+- 지연은 절반 아래로 줄었고, 노드는 40대에서 24대로 줄었다
+- 오류율 0.07%는 SLO 0.1% 안쪽이다
+- 출처: 예시 관측 대시보드, 2026년 9월 (예시)
+---
+```
+
+A migration plan reads as a sequence with the condition each step must meet.
+
+```markdown
+---
+layout: step-diagram
+
+## Cut-over plan for the v3 gateway
+
+- **1. Shadow** mirror 5% of traffic to v3 and compare responses
+  (1) Exit: 0 mismatches over 72 h
+- **2. Canary** route 10% of live traffic to v3 in one region
+  (1) Exit: p99 under 250 ms, error rate under 0.1%
+- **3. Ramp** move to 50%, then 100%, one region a day
+  (1) Exit: no rollback for 7 days
+- **4. Retire** drain v2 and remove its 40 nodes
+  (1) Owner: example platform team
+- Source: example rollout runbook, October 2026 (example)
+---
+```
+
+## Examples
+
+`13-engineering-review-computational-brutalism-ko.md`

package/.grok/skills/lit-pptx/references/tonalities/neo-brutalism.md

@@ -0,0 +1,161 @@
+# Neo-Brutalism
+
+Neo-Brutalism is the loud direction, and it is loud on purpose. Every card is a flat yellow block
+with a thick black border and a hard black shadow offset down and to the right, with no blur at all.
+Titles are heavy and tight, the topic band is saturated blue, one pink-red accent marks the figure
+the slide is for, and the ground is a warm cream. Nothing is soft: no gradients, no rounded corners,
+no glow. It reads like a poster or a product sticker, so it suits a room that should feel energy,
+and it stays legible because every colour pair still meets the contrast floor.
+
+## When to use it
+
+Reach for Neo-Brutalism for a startup pitch at a demo day, a consumer product launch, a campaign
+kick-off, a creator or community event, a hackathon final or an education deck for a young audience.
+The content signals that point here are a short body (one claim and two or three facts per slide),
+three or four headline numbers, a launch or sign-up ask, and words such as 런칭, 출시, 데모데이,
+캠페인, 크리에이터, or the user asking for something bold, punchy or "brutalist". It is the second
+candidate for the pitch deck type, after Signal, and the first when the user asks for a bold or
+playful look.
+
+## When it is the wrong choice
+
+It fails for a formal report, an academic talk, a board or finance review and any deck read alone
+later: the blocks take space a reader needs for detail, and a slide of long paragraphs between thick
+borders reads as noise. It is wrong for grief, safety, HR or financial-loss topics, and
+for a deck under a corporate brand guide. When the brief says "clean" or "minimal", Signal or Studio
+fits; when it says "report", Ledger or Gazette.
+
+## Tokens
+
+The values below come from the pack file and are what the engine draws.
+
+| Token | Value |
+|---|---|
+| ground / surface | #FFF5E1 / #FFD43B (the yellow card) |
+| ink / ink-muted / line | #111111 / #3A3A3A / #111111 |
+| accent / accent-deep / accent-tint | #D81B5C / #6B0F2E / #FFC9DA |
+| field / on-field | #2F4BFF / #FFFFFF |
+| positive / negative | #137A43 / #111111 |
+| series | #D81B5C, #2F4BFF, #111111, #137A43 |
+| faces | Pretendard Bold for display, title, labels and numerals, Pretendard Regular for body; `faces: a2z` swaps to A2Z Black display, titles and numerals |
+| register / ramp / hero | bold / presented (body 18 pt, labels 14, sources 12, titles 32, display 44) / allowed: a statement and a big figure may take the 72 pt hero step |
+| type voice | titles tracked −2, display −3 |
+| density / variance | 10 / 7 |
+| radius / edge | 0 / fill and border, 2.5 pt in ink |
+| shadow | 6 pt offset at 45°, ink, fully opaque, no blur |
+| table | yellow header, ruled grid, protagonist row in pink tint, bold totals |
+| chart | no gridlines, direct labels, series in order (pink, blue, black) |
+
+This is the family's bold register (`register: bold`): it sets presented type and the 72 pt hero step, so
+titles, figures and statements run large, but they fill the same slide-grid zones as every other
+pack. A title still sits in the one title zone and the body still starts at y 120; the register
+changes the size inside a zone, never the zone. The registry refuses presented type in a pack without
+`register: bold`, so a report pack cannot drift into this size by accident; every pack takes its own
+hero step on the cover and statements. A KPI
+row keeps its bordered cards, because the card is this direction's figure. The pink accent was darkened until a pink figure on a yellow card still holds 3:1 at title
+size. Losses use ink with a ▼ sign, because pink already means "look here".
+
+The shadow is written into the file as a real outer shadow with a blur of zero, so PowerPoint,
+Keynote and LibreOffice all draw the same hard edge. Every block of the blue field (a band, a
+section page, a cover plate) carries the black border too.
+
+## QA allowances
+
+The yellow card, the blue band and the pink accent share a content slide inside the default OF-101
+limit (four hue families; a fifth fails). The gate reads this pack's `qa:` block:
+`offset-shadow: true` lets OF-120 pass the hard shadow; a shadow with any blur still fails, and the
+same shadow in any pack without this allowance fails. Contrast floors are unchanged.
+
+## Treatments by slide role
+
+Content slides and data with a takeaway take `top-plain-large`; data, sequence, reference and
+definition slides take `band` (the title in white on the blue band); image slides `bottom-anchor`;
+statements `statement`. `kicker-numeral` is the third option for a sequence. The engine lays out
+every treatment the family allows, keeps the role's own when the body fills, and otherwise takes the
+one that leaves the least empty band. Force one with `title: <id>` on the line after `layout:`.
+
+## Families and variants
+
+- `kpi-row` sets two to four results as yellow cards, each with value, label and basis.
+- `big-number` is a blue panel of related figures beside the facts that explain them.
+- `comparison` reads before and after across shared rows.
+- `process` and `step-diagram` show three to five steps with a numeral in the accent.
+- `chart-insight` carries one growth chart with its takeaway beside it.
+- `table-insight` holds the one table a pitch needs, usually unit economics.
+- `image-split` pairs a product shot with three short points.
+- `summary-box-list` sets two to four bordered boxes of one claim each.
+- `agenda`, `quote` and `statement` keep the type loud and the page open.
+
+Covers are `cover-typographic`, `cover-split-field` and `cover-numeral`; sections are
+`section-field` and `section-numeral`; closings are `closing-ask`, `closing-decision-box` and
+`closing-statement`.
+
+Display slides. The typographic cover sets the topic in white on a blue plate across the lower
+half, bordered in black. A statement drenches the page in blue with the sentence in white. A big
+number is a blue field panel. A closing's next step sits in a bordered box with its shadow.
+
+## Do
+
+- Keep one claim per slide and write it in the first body line, in plain words.
+- Give every figure its label and its basis in the card.
+- Let the yellow cards carry figures and short labels, never paragraphs.
+- End on `closing-ask` with the amount, its uses and the next meeting.
+
+## Avoid
+
+- Blurred or soft shadows, rounded corners and gradients; the look is flat and hard.
+- Thin hairlines beside the 2.5 pt borders.
+- More than three fill colours on one slide.
+- Muted grey text on the yellow surface.
+- This direction for formal reports or sensitive topics.
+
+## Two worked slides
+
+A launch deck opens its traction slide with four results as cards and two facts under them.
+
+```markdown
+---
+layout: kpi-row
+
+## 베타 8주 성과, 2026년 10월
+
+| 가입자 | 주간 재방문 | 추천 가입 | 유료 전환 |
+|---|---|---|---|
+| 1만 2천 명 | 46% | 38% | 7.4% |
+| 목표 1만 명 | 업계 평균 25% | 광고비 0원 | 목표 5% |
+
+> 베타 운영 기록, 2026년 8-10월 (예시)
+
+- 광고 없이 가입자 목표를 넘겼다: 셋 중 하나 이상이 친구 추천으로 왔다
+- 유료 전환 7.4%는 목표 5%를 넘었고, 연 결제가 그중 60%다
+- 출처: 예시 서비스 운영 대시보드, 2026년 10월 (예시)
+---
+```
+
+The closing states the ask, shows where the money goes and names the next step.
+
+```markdown
+---
+layout: closing-ask
+
+## 시드 15억 원 사용 계획
+
+| 쓰임 | 금액 | 시점 |
+|---|---|---|
+| 앱 개발 인력 4명 | 7억 원 | 2027년 상반기 |
+| 크리에이터 제휴 200곳 | 4억 원 | 2027년 1분기 |
+| 마케팅 실험 | 3억 원 | 상시 |
+| 운영 예비비 | 1억 원 | 필요 시 |
+| 합계 | 15억 원 | 12개월 |
+
+> 투자금 쓰임 (예시 데이터)
+
+- 요청: 시드 15억 원 투자 승인
+- 기대 성과: 12개월 뒤 가입자 10만 명, 월 매출 2억 원
+- 다음 단계: 11월 첫째 주 후속 미팅, 담당 예시 대표
+---
+```
+
+## Examples
+
+`14-launch-pitch-neo-brutalism-ko.md`