@litfamily/litclaude 1.0.19 → 1.0.21

package/plugins/litclaude/skills/lit-pptx/references/authoring-guide.md

@@ -1,64 +1,102 @@
 # Authoring Guide (Markdown → PPTX)
 
-How to author a deck in the constrained Markdown dialect that `scripts/compile-deck.js` compiles. Template-agnostic — the enrolled template owns fonts, palette, dimensions, and decorations. The full contract is `specs/markdown-slide-spec-v1.md`; this guide is the working reference.
+How to author a deck in the constrained Markdown dialect that `scripts/compile-deck.js` compiles. The tonality pack (or a named legacy template) owns fonts, palette, dimensions and decoration. The full contract is `specs/markdown-slide-spec-v1.md`; this guide is the working reference.
+
+## 1. Pick a direction
+
+A deck compiles under a tonality (a design direction read from a pack) or under a legacy template
+the user named. Choose it with the direction step (`direction-step.md`) before writing slides, and
+put it in the frontmatter so the source carries its own look:
 
-## 1. Pick a template (and font)
 ```bash
-node "$SKILL_ROOT/scripts/compile-deck.js" --list-templates
-node "$SKILL_ROOT/scripts/compile-deck.js" --list-layouts <TEMPLATE>   # blocks + regions per layout
+node "$SKILL_ROOT/scripts/compile-deck.js" --list-tonalities              # eight tonalities and the legacy templates
+node "$SKILL_ROOT/scripts/compile-deck.js" --list-layouts <tonality>      # families, the titles each allows, variants
+node "$SKILL_ROOT/scripts/compile-deck.js" --list-templates               # legacy and learned templates
 ```
-Bundled templates:
-| Template | Canvas | Font | Use |
-|----------|--------|------|-----|
-| `AZURE-PRO` (default) | 16:9 (13.333×7.5in) | Pretendard | Blue and white designed decks: geometric cover, tinted numbered cards, KPI badges, navy dividers |
-| `AZURE-A2Z` | 16:9 (13.333×7.5in) | 에이투지체 (A2Z) | Same design, A2Z typography |
-| `BOILERPLATE-PRETENDARD` | 4:3 (10×7.5in) | Pretendard | Plain professional/technical decks (no `section` layout) |
-| `BOILERPLATE-A2Z` | 4:3 (10×7.5in) | 에이투지체 (A2Z) | Same layout, A2Z typography |
-| *(learned)* | from source | from source | `scripts/learn_template.py <your.pptx> --name <NAME>` to enroll your own brand |
 
-Font note: **Pretendard** is one weighted family (bold via weight). **에이투지체** and **Brand Sans** ship one family *per weight* (`에이투지체 7 Bold`, `Brand Sans Bold`) — weight is chosen by family name, never a bold flag. The template encodes this; you just write content.
+| Tonality | One line |
+|---|---|
+| `ledger` | numbers first, dense, tabular; business reviews and status updates |
+| `signal` | short, bold slides with one hot accent; pitches and launches |
+| `atlas` | pictures carry the deck, titles on panels or under images |
+| `chalk` | teaching: numbered steps, worked examples, marked terms |
+| `paper` | ink on white, figures and booktabs tables, citations |
+| `gazette` | Korean briefing pages: header band, boxed summary, 개조식 evidence |
+| `studio` | editorial grid, asymmetric splits, side titles, large real numerals |
+| `night` | dark ground for data and technical keynotes |
+
+Legacy templates (`AZURE-PRO`, `AZURE-A2Z`, `BOILERPLATE-PRETENDARD`, `BOILERPLATE-A2Z`, or one
+learned from the user's deck) keep their single look and are used only when the user names one.
+Each tonality sheet in `tonalities/` lists its tokens, title treatments, families and two worked
+slides; `examples/` holds complete decks.
+
+Font note: every tonality sets the deck in **Pretendard** Regular and Bold by default; hierarchy
+comes from size, weight, colour and placement. The **에이투지체** (A2Z) faces are used only when the
+user or the source asks for them: `faces: a2z` in the frontmatter (or `--faces a2z`) applies the
+pack's `faces-a2z` map. A2Z ships one family *per weight* (`에이투지체 7 Bold`), so weight is chosen
+by family name, never a bold flag. The pack encodes this; you write content.
 
 ## 2. Deck skeleton
 ```markdown
 ---
-template: AZURE-PRO
+tonality: ledger
 title: Deck Title
 date: 2026-06-29
+notice: 예시 데이터 — 실제 수치로 바꿔 주세요
 ---
 
 ---
-layout: cover
+layout: cover-figures
 
 # Deck Title
 ---
 
 ---
-layout: content
+layout: chart-insight
+
+## The title names the topic as a label
 
-## Section title
+::: chart type=column unit="억 원"
+| 분기 | 매출 | 계획 |
+|---|---|---|
+| 1Q | 1,120 | 1,100 |
+| 2Q | 1,184 | 1,140 |
+> 분기별 매출과 계획, 2026년 (예시 데이터)
+:::
 
-- **Bold section header**
-  (1) sub-item with a concrete detail
-  (2) another sub-item
-- **Second header**
+- The claim the chart supports, as the first takeaway
+- What it compares with, and over which period
+- What it implies or what happens next
 ---
 
 ---
-layout: closing
+layout: closing-ask
+
+## The decision you ask for
 
-# 감사합니다
+| 안건 | 금액 | 결정 시점 |
+|---|---|---|
+| … | … | … |
+
+- 다음 단계: who does what, by when
 ---
 ```
 **Separator rule (critical):** a `---` line, then a blank line, then `---` + the next `layout:`. This is how slides are split — see the spec.
 
-## 3. Layouts (the 5 approved)
-- `cover` — title + metadata + date
-- `content` — title + body (bullets/numbered/sections), optional table + image + captions
-- `main` — content + an optional bordered `main-box` callout
-- `summary` — two grouped blocks (top/bottom) + optional image/table
-- `closing` — single centered title
+Frontmatter keys for the direction: `tonality:`, and `density:` / `variance:` only when the card
+moves a dial. Slide keys after `layout:`: `title: <treatment>` pins one slide's title treatment
+(`title-treatments.md`); `variant:` belongs to legacy templates.
+
+## 3. Layout families
 
-Each layout supports a fixed set of blocks per template — check `--list-layouts`. Tables use standard Markdown pipes; images use `![alt](path)`; captions follow the spec.
+Under a tonality, `layout:` names a family (the slide's job) or a cover, section or closing variant.
+`layout-families.md` lists all of them with the source each one reads; `--list-layouts <tonality>`
+shows which the chosen pack carries. Write the source so the slide fills (`density-and-fill.md`):
+a takeaway under every table, evidence under a big number, the next step under an ask.
+
+Under a legacy template the five original layouts remain: `cover`, `content`, `main` (content plus a
+`::: main-box` callout), `summary` (two grouped blocks) and `closing`; `section` exists on the Azure
+templates. Check `--list-layouts <TEMPLATE>` for the blocks each accepts.
 
 ### Executive/research compositions
 
@@ -82,14 +120,14 @@ Do not write authoring trace or unresolved placeholders. Treat overclaim, jargon
 
 ## 4. Compile
 ```bash
-node "$SKILL_ROOT/scripts/compile-deck.js" deck.md --template <TEMPLATE> --html out.html      # preview
-node "$SKILL_ROOT/scripts/compile-deck.js" deck.md --template <TEMPLATE> --pptx out.pptx --embed-fonts
+node "$SKILL_ROOT/scripts/compile-deck.js" deck.md --pptx out.pptx --embed-fonts                    # tonality: from the frontmatter
+node "$SKILL_ROOT/scripts/compile-deck.js" deck.md --template <TEMPLATE> --pptx out.pptx --embed-fonts  # a named legacy template
 ```
 `--embed-fonts` makes the deck self-contained (renders on machines without the font). `--ast out.json` dumps the intermediate AST.
 
 ## 5. Verify (always)
 ```bash
-python3 "$SKILL_ROOT/scripts/qa_deck.py" out.pptx        # overflow/overlap + WCAG contrast + anti-slop; non-zero = FAIL
+python3 "$SKILL_ROOT/scripts/qa_deck.py" out.pptx        # overflow, contrast, anti-slop, craft floor and the deck output checks; non-zero = FAIL
 python3 "$LITCLAUDE_LIB/render_pages.py" out.pptx --out-dir renders --pages 5   # then open renders/page-*.png
 ```
 A clean gate is defect-absence, not quality — read the rendered pages. See `references/anti-slop-checklist.md`.
@@ -97,8 +135,11 @@ A clean gate is defect-absence, not quality — read the rendered pages. See `re
 ## 6. Anti-patterns (fix before shipping)
 - Generic titles ("개요"/"Overview") → make them specific.
 - Padding bullets that restate the heading → cut or add real information.
-- Manually adding logos/lines/colors/fonts → the template applies decorations; don't.
+- Manually adding logos/lines/colors/fonts → the pack or template applies decoration; don't.
+- Positioning a title with a free box → every treatment has one frame; pin a different treatment with `title:` instead.
+- A table, a big number or an ask with nothing under it → add the takeaway, the evidence or the next step (`density-and-fill.md`).
 - Overloaded slides (> ~8 bullets, > ~8 table rows, > 4 items per summary group) → split.
+- A data slide without its basis, comparison, period or source → add them; end with `출처:` (`Source:`).
 - Placeholder/AI-slop wording → gated by `scripts/forbidden-terms.json`.
 - Evidence image with only a filename-like alt → write a numbered caption plus `Source:`/`출처:` so the visible caption stays bound to the figure.
 - Appendix DOI/canonical/raw URL field without a hyperlink → add an actual PowerPoint hyperlink. QA detects the field directly and verifies its external OOXML relationship; no special “link available” phrase is required.
@@ -110,6 +151,15 @@ node "$SKILL_ROOT/scripts/compile-deck.js" deck.md --template MY-BRAND --pptx ou
 ```
 The learned template only references fonts/colors/assets present in your source (off-brand-by-construction).
 
+## Run-in labels
+
+A point may open with a bold label: `- **요약:** 앱에서 맡기면 …`, `- **Basis:** 1.0 L/min feed`. Write
+the colon; the engine adds one when the label ends without a separator (`**요약** 앱에서 …` is set as
+"**요약:** 앱에서 …"), because a bold word running into its sentence reads as part of it. A bold line
+with nothing after it is a group heading and takes no colon. The gate fails a run-in label without a
+separator (OF-118). An agenda numbers its own rows, so its title stands without a numeral beside it
+(OF-119).
+
 ## Placement (spec v2)
 
 Reach for the least freedom that says the thing. Each tier gives up a guardrail, and
@@ -153,21 +203,48 @@ pie and doughnut use the first series. The chart takes the table's place on any
 layout that accepts a table and fills the slide down to its caption, which the
 engine numbers "도 N.".
 
-Headline numbers become KPI cards on the Azure templates when the table is small:
-one data row with two to four short values, or two columns of value/label with up to
-four rows.
+One series carries the accent, and it is the same kind of series on every chart of the deck: the
+latest period when every series names one ("2026" over "2025", "Q3" over "Q2"), else the measured
+series beside a plan, target, budget or prior period ("실적" over "계획"), else the last column. Put
+the proposed or current series last when the names say neither. Data labels keep the decimals the
+table writes, so a chart beside a table that says 18.0 says 18.0 too.
+
+A figure exported as a picture (a plot or a diagram drawn on white) stands as a white card on a dark
+tonality. Give it a dark variant beside it, named like the file with `.dark` before the extension
+(`assets/flow.png` and `assets/flow.dark.png`): a dark tonality draws the variant, a light one the
+original. Better still, give a plot its numbers as a `::: chart` block, which every tonality draws in
+its own colours. The gate fails a mostly-white picture on a dark ground (OF-117).
+
+Headline numbers become KPI cards on the Azure templates (two to four short values), and the
+`kpi-row` family under a tonality: one data row of up to six short values, a second row with each
+figure's basis or comparison, a caption with period and source, the takeaways, and the source line.
+Under a side title, or when the cards would stop high on the page, the values run down the body as
+rows (value, label, basis) with the takeaways beside them.
 
 ```markdown
-| 매출 | 영업이익 | 영업이익률 |
-|---|---|---|
-| 1,184억 원 | 110억 원 | 9.3% |
+| 매출 | 영업이익 | 영업이익률 | 영업현금흐름 | 수주 잔고 |
+|---|---|---|---|---|
+| 1,184억 원 | 110억 원 | 9.3% | 96억 원 | 2,310억 원 |
+| 계획 대비 +3.9% | 계획 대비 +10.0% | 계획 대비 +0.5%p | 전년 동기 81억 원 | 전분기 대비 +4% |
+
+> 2026년 3분기(7-9월), 내부 결산 자료 (예시)
+
+- 매출과 영업이익이 모두 계획을 넘었다
+- 영업현금흐름은 영업이익의 87% 수준이다
+- 수주 잔고는 매출 약 2분기분이다
+- 출처: 예시 기업 내부 결산 자료(2026년 3분기), 2026년 연간 사업 계획
 ```
 
-`notice:` in the frontmatter prints one line at the bottom right of every slide —
+A slide is dense when every block on it says something the reader needs: the figure, what it is
+compared with, the period, where it comes from, and what follows. Write that, and the compact step
+(density 10, every pack's default) sets it at 13 pt in 24 pt margins with the source strip at the
+foot. Never repeat a line to fill a slide; merge thin slides instead.
+
+`notice:` in the frontmatter prints one tag at the bottom left of every slide —
 use it whenever values are examples: `notice: 예시 데이터 — 실제 수치로 바꿔 주세요`.
 
 Measured scientific data (instrument output, fitted curves, uncertainty) is still
 drawn by `/litclaude:lit-scientific-visualization`: hand it the deck's visual system
-with `compile-deck.js --template <T> --export-viz-context ctx.json` and place the
+with `compile-deck.js deck.md --export-viz-context ctx.json` (the tonality comes from the frontmatter) and place the
 result as a captioned figure. Register the font *file* from `ctx.json` rather than the
 family name — a Korean family resolved by name alone renders as boxes.

package/plugins/litclaude/skills/lit-pptx/references/consensus-protocol.md

@@ -119,7 +119,7 @@ Write to `.pptx-pipeline/plan-{slug}.md`:
 - Render path: compile-deck.js
 
 ## QA Plan
-- Compile: `node "$SKILL_ROOT/scripts/compile-deck.js" deck.md --template <TEMPLATE> --pptx output.pptx --embed-fonts` (default `<TEMPLATE>` = AZURE-PRO)
+- Compile: `node "$SKILL_ROOT/scripts/compile-deck.js" deck.md --template <TEMPLATE> --pptx output.pptx --embed-fonts` (or without `--template` when the frontmatter names the tonality; there is no default look)
 - Verify: `python3 "$SKILL_ROOT/scripts/layout_inventory.py" output.pptx --issues-only`
 - No scripts/forbidden-terms.json check: `python validate_pptx.py output.pptx`
 ```

package/plugins/litclaude/skills/lit-pptx/references/data-display-cookbook.md

@@ -1,6 +1,6 @@
 # Data Display Cookbook
 
-Standardizes numbers, tables, and KPI tiles. Colors below refer to the chosen template's palette roles, not fixed brand hex.
+Standardizes numbers, tables, and KPI tiles. Colors below refer to the palette roles of the chosen tonality (or the named legacy template), not fixed brand hex. The pack also fixes the table style (booktabs, ledger, light grid, header fill or open), its rules and banding, and the chart style (gridlines, direct labels or legend, how the highlight is drawn); write the data and let the pack draw it. Each tonality sheet in `tonalities/` names its table and chart style.
 
 ## Number display
 | Data type | Preferred | Avoid |
@@ -14,13 +14,13 @@ Standardizes numbers, tables, and KPI tiles. Colors below refer to the chosen te
 ## Table patterns
 
 ### 1. Compact operational table (4–6 columns of operational data)
-- Body and bold header in the template's table sizes; tight row padding; light bottom rules only. Use right-aligned numbers in quantitative columns.
+- Units in the header, numbers right-aligned, a total row last when the data has one (the engine sets it apart by the pack's rules). Follow it with two or three takeaway lines (`table-insight` beside, `ledger-table` under).
 
 ### 2. Comparison matrix (alternatives / vendors / scenarios)
-- Alternating row bands; strong header row; one emphasis column only; right-align all quantitative columns.
+- One row per option, one emphasis only: the pack tints the row whose first cell the slide title names. Right-align all quantitative columns. Two options with three to four points each read better as a `comparison`; two axes with four options read better as a `matrix-2x2`.
 
-### 3. KPI strip (3–4 headline numbers before a narrative/chart)
-- Value on top, label below; primary value in the template's metric color; positive/negative only for deltas (with ▲/▼ glyph); center within each tile.
+### 3. KPI strip (2–4 headline numbers before a narrative/chart)
+- A one-row table of short values with the labels in the header; the first value takes the accent. Positive/negative colours only for deltas, always with a ▲/▼ glyph and a sign. Add one to three evidence bullets; under a side title the values become rows down the body.
 
 ## Source-note pattern
 Place source text under the table/chart, smaller than body text:
@@ -31,7 +31,7 @@ Place source text under the table/chart, smaller than body text:
 ## Rules of thumb
 - Units in headers, never per cell. Numeric columns right-aligned (the real fix on export).
 - ≤ 6 columns; split a wide table rather than shrinking text below the template's minimum body size.
-- One emphasis per table; no styled spans inside cells; no rainbow semantics.
+- One emphasis per table; no styled spans inside cells; no rainbow semantics. One series is one hue; several series take the pack's series colours in order.
 - Keep one primary visual emphasis. Do not highlight a row, a column, and several cells at the same time.
 - Avoid chart-type mixing unless a clear analytical reason requires it; state that reason in the interpretation.
 - Keep labels readable at presentation scale and move or abbreviate collision-prone labels. Axis labels, data labels, annotations, and legends must not overlap.
@@ -43,3 +43,10 @@ Place source text under the table/chart, smaller than body text:
 - **table plus decision takeaway:** one bounded table, caption/source, and one decision sentence. Do not duplicate the table in prose.
 - **source capture:** crop to the relevant region while retaining enough interface/document context to verify the locator.
 - **two-record appendix evidence:** at most two records per slide. Each record includes summary, source/locator, and DOI/canonical link when available.
+
+## Filling the slide with the data, not around it
+
+- A table of three rows or fewer at the top of a slide leaves the page empty; make it a `kpi-row`, a `comparison`, or give it its takeaway.
+- A chart takes the body to the floor (`anchor-visual`), with its caption bound under it; two or three takeaways sit beside it (`chart-insight`) or the title explains it from below (`bottom-anchor`).
+- One real figure that carries the slide is a `big-number` with two or three lines of evidence; a decorative number is a defect.
+- See `density-and-fill.md` for the fill policies and the gate checks that measure the empty band.

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

@@ -0,0 +1,164 @@
+# Density and fill
+
+Two dials set how a deck uses its pages. Density decides how much each page holds and how tightly;
+variance decides how many title treatments and layout families one deck mixes. Each tonality has
+defaults, and the direction card records the values used. The skill may move a dial by up to 2 on
+its own and says so on the card; a larger move waits for the user.
+
+Fill is what density is for. The old engine left the lower half of most slides empty: a short table
+at the top, cards as tall as their two lines, a closing that said only "thank you". The engine now
+measures how much of each slide's body stays empty under its last block and tries to close the gap,
+and the gate fails a deck whose typical slide still leaves more than a fifth of its body unused. The
+engine can only grow what the source gives it, though, so most of the work is in how the source is
+written.
+
+## Density
+
+| Density | Grid (16:9 side margin) | Ramp | Body size | Item / group / block gap | Padding | Table row (min) | Empty band a slide may leave |
+|---|---|---|---|---|---|---|---|
+| 1-2 | airy (60 pt) | presented | 24 for four items or fewer, else 18 | 18 / 36 / 48 | 24 | 36 | 28 % |
+| 3-4 | standard (48 pt) | presented | 18, may step to 24 | 12 / 24 / 36 | 24 | 32 | 24 % |
+| 5-6 | standard (48 pt) | reading | 14, may step to 18 | 6 / 18 / 24 | 18 | 24 | 18 % |
+| 7-8 | dense (36 pt) | reading | 14, may step to 18 | 6 / 12 / 24 | 12 | 22 | 14 % |
+| 9 | dense (36 pt) | reading | 14 | 6 / 12 / 24 | 12 | 20 | 12 % |
+| 10 | compact (24 pt) | compact: body 13, label 11, source 9 | 13 | 6 / 12 / 18 | 12 | 18 | 12 % |
+
+The grid's side margins, the gaps, the padding and the body size move with density. From density 5
+a deck reads on the reading ramp (body 14 pt, title 26 pt); density 10 is the compact step, and every
+pack now starts there. On it a top title sits close over its rule (the body starts about 30 pt
+higher), nothing is stepped up to fill, and the readable floor holds: body text 12 pt or more, table
+cells and captions 11 pt, sources 9 pt. Lower the density (by at most 2 without asking, to 8: body
+14 pt, 36 pt margins) only for a deck presented to a large room.
+
+## Variance
+
+| Variance | Title treatments per deck | Same family in a row |
+|---|---|---|
+| 1-3 (only when the user asks for a uniform deck) | 1-2; the gate records "variety lowered by the user" | — |
+| 4 | 3 | at most 3 |
+| 5-6 | 3-4 | at most 3 |
+| 7-8 | 4-5 | at most 2 |
+| 9-10 | 5 | at most 2, and at most 2 of one family in the deck |
+
+The upper end is also capped by how many treatments the pack has.
+
+## What the engine does to fill a slide
+
+When a content slide's empty band exceeds the cap for its density, the engine tries the pack's
+`fill-order`, one policy at a time, and keeps a step only when it does not overflow:
+
+- **step-up** sets the body one ramp step larger (presented 18 → 24, reading 14 → 18), table data
+  from label to body size, and KPI values a step up. One step only; titles never shrink to make room.
+- **distribute** opens the item, group and block gaps one step each, keeping the body's top edge
+  fixed. Rows of peers keep equal heights; a body is never centred vertically.
+- **anchor-visual** lets a chart, figure or image take the rest of the body, and grows table rows up
+  to a quarter above the density minimum.
+- **change-family** is the author's step: the engine cannot invent a better shape, so the compile
+  log says "choose a fuller family" and the source changes.
+
+Every filled slide gets a line in the compile output, which goes into the build log:
+
+```text
+fill: slide 5 band 0.41 -> 0.12 (step-up, distribute)
+fill: slide 9 band 0.39 -> 0.39 (none: nothing on the slide can grow; choose a fuller family)
+```
+
+A column can stand empty beside a full one even when the body's last block reaches the floor: two
+short takeaways beside a chart, a source line at the column's foot and nothing between. The engine
+reads each text or picture column against the column beside it (its largest empty band, from the
+top of the pair down to where the longer column ends) and fills a column that leaves more than 40 %
+of the body empty, in this order, by layout only:
+
+- the visual takes columns: a narrower takeaway column wraps onto more lines and a wider chart or
+  picture grows (down to three columns of takeaways; a picture keeps taking columns while either
+  side leaves a fifth of the body empty);
+- the takeaways step up to lead size when they fit and keep twelve glyphs a line;
+- the room left is shared between the points, at most a sixth of the body a gap;
+- two short points beside a chart that still leave the column empty run under the chart, side by
+  side, and the chart with its values takes the body's width;
+- a short sidebar note beside a long main column stands across the top at lead size and the main
+  points run in two columns under it;
+- a title under which a column still stays empty is unfit for the slide when another title fits.
+
+The source strip closing a column counts as a block but never hides the band above it, and the
+chart's values table under the takeaways is part of their column. The gate measures the same way
+(OF-115).
+
+The engine chooses the title treatment for a slide by fill as well: among the treatments the role
+and the family allow, a slide whose body stays short under the role default may move to a side rail
+or a bottom title, where a chart or table takes the full height. It never adds decoration to cover
+space and never pads cards.
+
+## Writing source that fills
+
+These are the rules the examples follow. Each one gives the engine something real to place in the
+lower part of the body.
+
+- **Every content slide carries its supporting facts.** Beside the main point, give what a careful
+  reader asks for: the basis (where the figure comes from), a comparison (previous period, plan,
+  peer), the period, the source, and the implication or next step. Tables run five to eight rows and
+  four to six columns where the source has them, charts five to eight categories, comparisons three
+  or four labelled criteria a side. Example values are labelled as examples.
+- **Close every data slide with its source.** A last line `출처: …` (`Source: …`) names where the
+  figures come from and when; a `주: …` (`Note: …`) line may follow with a definition or a caveat.
+  The engine sets them as a strip at the foot of the body, at source size, so they cost the takeaways
+  no room.
+- **Figures come in rows of four to six.** A `kpi-row` table holds up to six figures, its second row
+  each figure's basis or comparison ("계획 대비 +3.9%", "전년 동기 81억 원"). On the compact step a short
+  card row runs as figure rows with the takeaways beside them.
+- **Label comparison points by criterion.** Start each point with the same label on both sides
+  ("비용: …", "일정: …"); the engine draws the labels as a criteria column and the two sides as rows.
+- **Pair a chart with its numbers.** On the compact step the values of a chart (up to eight rows and
+  four columns) stand as a small table under its takeaways when they fit; write the chart's table
+  with the exact figures, units in the headers.
+- **The title names the topic; the claim opens the body.** "분기별 매출 추이", not "매출은 다섯 분기 연속
+  늘었다"; the sentence becomes the first takeaway. A claim with its reasons is a `summary-box-list`
+  (the claim boxed over the reasons), a `kpi-row`, or a table with the claim as its first takeaway;
+  a stand-alone `statement` slide is for a pull quote or a deck the user asks to be display-led.
+- **Numbers are never the whole slide.** A `big-number` is a data panel of two to four related
+  figures: a KPI table with labels, values and a second row giving each figure's basis or comparison
+  ("전년 대비 +12%", "목표 50%"), a caption with period and source, then two or three lines of
+  evidence. Figures are set at title size at most.
+- **Every table gets a takeaway.** Two or three bullets after the table: the row that matters, the
+  comparison, the decision it supports. `table-insight` sets them beside the table, `ledger-table`
+  under it. A short table (three rows or fewer) is usually a `kpi-row` or a `comparison` instead.
+- **Every chart gets a caption and two or three takeaways.** The caption says what is plotted and
+  marks example data; the bullets say what to notice.
+- **A closing carries the ask and the next step.** The title names the request ("운영 자금 30억 원 요청
+  내역"); the body
+  lists what is to be approved (a small table of item, amount, date, owner works well) and the next
+  step with its owner and date. "감사합니다" or "Questions?" alone is never a closing.
+- **A comparison has the same number of points on both sides,** each a full clause, so the rows
+  read across and reach the floor together.
+- **A process or timeline names what happens at each step,** not only the step's name; a timeline
+  fed by a table takes its takeaway bullets under the axis. Give a timeline two or three takeaways:
+  one alone can leave the band under the axis empty, which OF-109 fails.
+- **References and appendices list every source with its date,** one per row; when there are only
+  two or three, add the definitions the deck relies on.
+- **Merge before you pad.** When a slide still has little to say, merge it with its neighbour or
+  give it a family that suits short content. Never add filler bullets that restate the title.
+
+## How the gate measures it
+
+`qa_deck.py` measures the empty band from the compiled file: the share of the body (from the title's
+bottom, or the top margin when the title sits low, down to 486 pt) below the lowest content block.
+Decoration, the footer and the example notice are not content. Cover, section, statement, quote
+and statement-closing slides are exempt.
+
+- **OF-112** reports each slide over its density cap as an advisory with a fix hint, and fails the
+  deck when the median band over all measured slides is above 0.20. On a legacy template the median
+  is an advisory too, because the legacy renderer has no fill policies.
+- **OF-109** (older and stricter per slide) still fails any single slide or card that leaves more
+  than 35 % of its area as one empty band.
+- **OF-115** fails a slide with an empty region: among them a text or picture column whose largest
+  empty band beside a longer column passes 40 % of the body (a source strip at its foot and the
+  chart's values table under the takeaways included). Beside the figure rows of a kpi-row or
+  big-number slide the takeaway column is measured to the body floor, since the rows stop where
+  their spacing ends; the engine sets the takeaways across under the rows, or lets them share the
+  room beside the rows when the across form would leave a band between the two.
+- **OF-111** fails a deck whose content slides share one composition (title zone × body partition ×
+  dominant content) on more than 40 % of them, or show too few distinct compositions.
+
+A slide that cannot be filled honestly (a one-line agenda, a short appendix) may stay over its cap;
+the deck median still has to hold. Shrinking text, inflating cards or adding decorative shapes to
+pass the gate is a defect, and the critique counts it as one.

package/plugins/litclaude/skills/lit-pptx/references/design-system-azure.md

@@ -1,7 +1,10 @@
-# Azure Professional — SOTA Blue & White Design System (2026)
+# Azure Professional — the legacy blue and white template
 
-A pro-designer blue-and-white system for `BOILERPLATE-AZURE` (flagship). 16:9 widescreen.
-Goal aesthetic: modern, geometric, confident — like a paid premium template, not a stock deck.
+The design system behind the legacy `AZURE-PRO` and `AZURE-A2Z` templates, 16:9 widescreen. It is
+one fixed look: geometric covers, tinted numbered cards, KPI badges, navy dividers. It is used only
+when the user names one of these templates or an existing deck source already does; a new deck takes
+a tonality from the direction step (`direction-step.md`). Under a legacy template the gate reports
+the variety checks and the median empty band as advisories, because the user asked for this look.
 
 ## Color tokens (locked)
 
@@ -55,4 +58,4 @@ Contrast (verified intent): ink/white very high; ink-muted/white ≈5.6:1; prima
 - 4pt spacing scale. Generous margins (16:9): outer ≈0.6in.
 
 ## Canvas
-- 16:9 widescreen: **13.333 × 7.5 in** (1280×720px @96). (Modern default; upgrade from 4:3.)
+- 16:9 widescreen: **13.333 × 7.5 in** (1280×720px @96).