@litfamily/litgrok 1.0.13 → 1.0.15

package/.grok/skills/lit-docx/references/tonalities/memo.md

@@ -0,0 +1,95 @@
+# Memo
+
+A notice, internal memo, short decision request or letter of one or two pages. It has no cover and no components: a small label, the subject set as the title, To / From / Date / Subject rows between two hairlines, then a few unnumbered sections of plain prose. Its quietness is the point; a memo that looks designed reads like marketing.
+
+Worked examples: `examples/05-memo-en.md` and `examples/09-memo-ko.md`, one page each.
+
+## When it fits
+
+- Something has changed or will happen, and a defined group needs to know what to do: a move, a drill, a new rule, a deadline.
+- A short request to one person or team that needs a written record.
+- The whole message fits on one page, two at most.
+
+## When it is wrong
+
+- The reader must choose between options: use Brief, which puts the decision and the comparison up front.
+- It needs tables of evidence or more than one table: use Report or Brief.
+- It is over two pages. Shorten it, or move the detail into an attached manual or report and keep the memo as the cover note.
+
+## Structure that sets it apart
+
+1. A label in muted bold at table size: the kicker of the `::: cover` directive (공지, 안내, Notice, Memo), or 메모 / Memo by default.
+2. The subject as the title, at 1.8 times the body (19 pt Korean, 20 pt English), not the 26 pt of the other tonalities. Frontmatter `subtitle:` is not printed in a memo (it still has to be a noun phrase, because the gate reads it), so put anything the reader needs into the Subject row.
+3. The memo block: rows of label and value between two ink hairlines, built from the cover line `To: … · From: … · Subject: …` (Korean `받는 사람:`, `보내는 사람:`, `제목:`, `참조:`; English also `Cc:`). The date row is added after From from frontmatter `date:` and printed as `2026. 10. 5.` or `5 October 2026`.
+4. The notice line under the block.
+5. Unnumbered sections in prose: what is happening, what each group must do, by when, whom to ask. The first section gives the whole message; later sections give detail.
+6. The folio at the foot from page 2, right-aligned; nothing in the header.
+
+## Tokens from the pack
+
+| Token | Value |
+|---|---|
+| Dials | density 9, variance 2 |
+| Margins | 25 / 27 / 25 / 25 mm |
+| Body | Pretendard 10.5 pt Korean (justified), 11 pt English (ragged) |
+| Ramp | h1 1.2 (12.5 / 13 pt), h2 1.1 (11.5 / 12 pt), title 1.8 (19 / 20 pt) |
+| Numbering | none |
+| Title block | memo block |
+| Summary | prose |
+| Running head | footer: folio right |
+| Palette | ink #1A1A1A, muted #555555, line #8C8C8C, no accent |
+| Accent on | nothing |
+| Components | none |
+| Figures | at most 0.40 of the frame high |
+| Spacing | `spacing: tight`: line pitch at the low end (Hangul 165 %, Latin 120 %), heading space reduced; a run-in title line keeps a heading's 12 pt above it, and the paragraph after a list stands 6 pt clear of the last item |
+| Fit | a memo never runs onto a second page that it fills under a quarter of the frame (`memo.fit`) |
+
+## Components
+
+None. Every directive except `::: cover` turns into plain text: a callout becomes a bold title line and its paragraph, key figures become a list. That is deliberate; if something must stand out, put it in the first sentence of the first section. The memo block itself counts as the one component kind the gate sees, which is why a memo must stay under four pages.
+
+## Writing the source
+
+- The subject line in the memo block and the title can differ: the title names the matter ("Finance team move to the sixth floor"), the Subject row says what the memo does ("Moving the finance team from floor 3 to floor 6 on 14–15 November").
+- Write the To / From / Subject values on one line, separated by ` · ` (space, middle dot, space). English values are capitalised automatically.
+- Korean memos to staff use 합니다체 consistently; a notice from an office may use 해요체 if the organisation does. Do not mix.
+- One small table is acceptable (a schedule, a floor-by-floor list); give it no caption if it is the only one.
+- End with the contact section: names, extensions, the date of any follow-up.
+- Dates in Korean text as `10월 22일(목)` or `2026. 10. 22.`; a line must not begin with a date.
+
+## Do and avoid
+
+| Do | Avoid |
+|---|---|
+| Say what changes for whom in the first paragraph | A background section before the reader learns what to do |
+| Name a person and an extension for questions | "문의 사항은 담당 부서로" with no name |
+| Keep it to one page when you can | Callouts, key figures or columns; they will print as text |
+| Trim sentences when a few lines spill onto page 2 | Leaving a second page that holds two lines (`memo.fit` fails it) |
+
+## Worked snippet
+
+```markdown
+---
+title: 2026년 하반기 본사 소방 대피 훈련 안내
+subtitle: 훈련 일시, 층별 대피 경로와 부서별 협조 사항
+author: 안전관리실
+organization: 예시 주식회사
+date: 2026-10-05
+notice: "예시 데이터: 실제 내용으로 바꿔 주세요"
+tonality: Memo
+---
+
+::: cover kicker="안내"
+받는 사람: 본사 전 직원 · 보내는 사람: 안전관리실 · 제목: 10월 22일 오후 소방 대피 훈련 실시
+:::
+
+# 훈련 개요
+
+본사 건물 전체를 대상으로 하는 하반기 소방 대피 훈련을 10월 22일(목) 오후 2시부터 2시 40분까지 실시합니다.
+
+# 문의
+
+훈련 일정은 안전관리실 김도윤 책임(내선 4410)에게 연락해 주십시오.
+```
+
+Page 1 shows "안내", the title, then four rows (받는 사람, 보내는 사람, 날짜 2026. 10. 5., 제목) between hairlines, the notice, and the two sections.

package/.grok/skills/lit-docx/references/tonalities/proposal.md

@@ -0,0 +1,105 @@
+# Proposal
+
+A proposal, plan or funding request as a document. It is the only tonality with a separate cover page, and the cover is typographic: the kind of document, the title set left in the upper third, one short rule, the subtitle and a two-line lead, with the organisation and date at the foot. The body that follows is unnumbered, states the case once with a key-figure strip, puts one decision box where the reader meets the request, and carries a budget table and a schedule.
+
+Worked examples: `examples/04-proposal-ko.md` (cover and 3 body pages) and `examples/08-proposal-en.md` (cover and 3 body pages).
+
+## When it fits
+
+- The document exists to get something approved: money, a pilot, a change of practice.
+- The reader needs the problem, the plan, the cost, the timetable and how success will be judged, in that order.
+- It may be read by people who were not in the room, so it must stand alone.
+
+## When it is wrong
+
+- The decision is small and the reader wants one page: use Brief.
+- It reports results of work already done, with a request at the end: use Report.
+- It is a plan only for the team that will carry it out, with steps: use Manual.
+- A cover page on a two-page document looks inflated; under about three body pages choose Brief.
+
+## Structure that sets it apart
+
+1. Cover page (its own section, no folio): kicker such as 사업 제안서 or Proposal, the title in the upper third at 2.7 times the body, a 36 mm rule in the accent, subtitle, the cover directive's lead paragraph, and at the foot the byline, date and sample-data notice.
+2. The body starts on page 2, numbered from 1, folio centred at the foot.
+3. 제안 요약 / Proposal in brief: the problem in numbers, the key-figure strip after the first paragraph, what is proposed, and the decision box.
+4. Unnumbered sections: current situation, what will be done, timetable, budget, benefits and how they will be measured.
+5. One budget table with a basis column and a bold total row; one schedule table.
+6. The last section names the measures and thresholds by which the pilot or plan will be judged.
+
+## Tokens from the pack
+
+| Token | Value |
+|---|---|
+| Dials | density 8, variance 6 |
+| Margins | 26 / 28 / 26 / 26 mm |
+| Body | Pretendard 10.5 pt Korean (justified), 11 pt English (ragged) |
+| Ramp | h1 1.4, h2 1.2, title 2.7 (Korean 14.5 / 12.5 / 28.5 pt; English 15.5 / 13 / 29.5 pt) |
+| Numbering | none |
+| Title block | cover page |
+| Summary | prose with one key-figure strip |
+| Running head | footer: folio centred |
+| Palette | ink #1A1A1A, muted #555555, line #8C8C8C, accent #6E2639 |
+| Accent on | title rule, callout rules |
+| Components | keyfigures (3 per row), callout (at most one), columns |
+| Figures | at most 0.60 of the frame high |
+| Fill target | median 0.75 |
+
+## Components
+
+- Key figures: three measured quantities that frame the case (the size of the problem, the target, the cost or payback), each with a basis line. Written inside `::: cover`, they are moved to the summary; they never stand on the cover.
+- One decision box, `::: callout kind=key title="결정 요청"` / `title="Decision requested"`: what, how much, from which budget, by when. A second callout becomes plain text.
+- Columns: for a short before / after or two-option comparison of similar length.
+
+The cover counts as one component kind, so the strip or the box alone already meets the two-kind floor; use both.
+
+## Writing the source
+
+- Put the cover's lead in `::: cover` as one or two sentences stating what is proposed. The title stays a noun phrase ("자전거 출퇴근 지원 시범 사업 제안서", "Booking system for shared laboratory instruments").
+- Give each budget line a basis in its own column (`80명 × 주 2.4회 × 26주 × 3,000원`), so the reader can check the arithmetic. Make sure the rows add up to the total.
+- State savings and benefits at their estimated size with the assumption that produces them. If a figure is a ceiling, say so.
+- The timetable is a table of phases with months, not a paragraph.
+- End with the measures and thresholds, not a restatement of the benefits.
+
+## Do and avoid
+
+| Do | Avoid |
+|---|---|
+| One decision box with amount and source of funds | Boxes for each benefit |
+| A budget table whose rows sum to the total | Rounded "약" figures that do not reconcile |
+| Key figures with a basis, in the summary | Figures on the cover, or a "number of sites" posing as a metric |
+| A cover lead that states the proposal in one or two sentences | A cover lead that repeats the title in other words |
+
+## Worked snippet
+
+```markdown
+---
+title: Booking system for shared laboratory instruments
+subtitle: A twelve-month plan for the Chemistry Building core facility
+author: Core Facility Committee
+organization: Example University, Department of Chemistry
+date: 2026-10-05
+notice: "Sample data: replace with real figures"
+tonality: Proposal
+---
+
+::: cover variant=typographic kicker="Proposal"
+This proposal replaces paper booking sheets with one booking system tied to training records and charges.
+:::
+
+# Proposal in brief
+
+Last year the paper sheets produced 46 recorded double bookings.
+
+::: keyfigures
+- **46** double bookings recorded (sample)
+  * Facility incident log, 2025–26 academic year
+- **610 h** booked but unused instrument time (sample)
+  * Spreadsheet bookings against instrument logs
+:::
+
+::: callout kind=key title="Decision requested"
+Approve the plan and a first-year budget of £38,500 (sample) from the equipment reserve.
+:::
+```
+
+The cover holds the kicker, title, rule and lead with the byline and date at its foot; "Proposal in brief" opens page 1 of the body.

package/.grok/skills/lit-docx/references/tonalities/report.md

@@ -0,0 +1,114 @@
+# Report
+
+The default for results, project reports, periodic reviews and analyses read by managers, from about three to thirty pages. In Korean it follows the manner of a central-bank or research-institute issue note: an unadorned title block, numbered sections in the institute order Ⅰ. / 1. / 가., prose paragraphs that state a finding and then its evidence, and tables that carry the numbers. In English it is the same page with decimal numbering.
+
+Worked examples: `examples/01-report-ko.md` (4 pages) and `examples/07-report-en.md` (3 pages).
+
+## When it fits
+
+- The reader needs the evidence, not only the conclusion: tables, comparisons, causes.
+- The document will be filed and read again, so section numbers help people point at things ("Ⅲ장 2절").
+- There are several findings of similar weight and one or more requests at the end.
+
+## When it is wrong
+
+- One decision for one busy reader: use Brief.
+- The document exists to win approval for new spending: use Proposal, which gives the budget and the decision box their proper place.
+- Readers will follow it step by step at a machine or a desk: use Manual.
+- It fits on one page: use Memo.
+
+## Structure that sets it apart
+
+1. Page 1 masthead: the kicker (the kind of report, e.g. "운영 결과 보고" or "Quarterly review") at the left of a series line with the date at the right, then the title, subtitle, byline, one rule in the accent, the sample-data notice, and the cover directive's lead paragraph.
+2. A short contents list after the title block when the source is long enough for about five pages.
+3. A first section named 요약 / Summary in prose: the main result in the first sentence, the key-figure strip after the first paragraph, then what the reader is asked to do.
+4. Numbered sections, each opening with a paragraph before its first subsection.
+5. Tables with numbered captions, units and source lines.
+6. The last section ends on the request, the next step or the open question, never on a generic wrap-up.
+
+## Tokens from the pack
+
+| Token | Value |
+|---|---|
+| Dials | density 9, variance 5 |
+| Margins | 25 / 27 / 25 / 25 mm (top, bottom, left, right) |
+| Body | Pretendard 10.5 pt, Korean justified, English ragged |
+| Ramp | h1 1.4 (14.5 pt), h2 1.2 (12.5 pt), title 2.5 (26.5 pt) |
+| Numbering | Korean `roman-ko` (Ⅰ. / 1. / 가.), English `decimal` |
+| Title block | masthead, contents on |
+| Summary | prose |
+| Running head | footer: short title left, folio right |
+| Palette | ink #1A1A1A, muted #555555, line #8C8C8C, accent #1F3A5F |
+| Accent on | title rule, callout rules |
+| Components | keyfigures (3 per row), callout, columns |
+| Figures | at most 0.45 of the frame high |
+
+## Components
+
+Use at most two of the three in most reports:
+
+- One key-figure strip in the summary, three real metrics each with a basis.
+- A callout for a stated assumption, a definition, or a warning about how to read a number; about one per four pages.
+- Columns for a genuine pair (before / after, two sites), rarely.
+
+A report of four pages or more must show two component kinds, and the masthead does not count as one in this tonality; the strip plus one callout is the usual pair.
+
+## Writing the source
+
+- Headings are topics: "발전 실적", "효율 저하 요인", "Speed of response". Never "발전량이 예측을 넘었다".
+- The first sentence under each heading carries the finding; the rest gives the evidence.
+- Each table is introduced by the paragraph above it and followed by a sentence that says what to notice.
+- Captions: `표 2. 분기별 발전량과 예측 대비 실적 (예시)`. Put units in the header cells; when all value columns share one unit, the converter lifts it into a `(단위: …)` line.
+- Close a table with `자료:` (and `주:` before it when needed) or `Source:`.
+- Avoid the generic institute headings that say nothing (개요, 주요 내용, 시사점, 결론) when a specific label is available.
+
+## Do and avoid
+
+| Do | Avoid |
+|---|---|
+| Give every number its period and source | Rounding a 4.7 % gain to "약 5%" in one place and "4.7%" in another |
+| Keep sections uneven when the material is uneven | Padding a short section to match its neighbours |
+| Write `short_title:` so the footer reads cleanly | Typing section numbers into headings |
+| End on the request or next step | Ending each section with a one-line restatement |
+
+## Worked snippet
+
+```markdown
+---
+title: 본사 옥상 태양광 설비 1년 운영 결과
+subtitle: 2025년 10월~2026년 9월 발전 실적과 2027년 보완 계획
+author: 시설관리팀 에너지파트
+organization: 예시 주식회사
+date: 2026-10-05
+short_title: 옥상 태양광 1년 운영 결과
+notice: "예시 데이터: 실제 수치로 바꿔 주세요"
+tonality: Report
+---
+
+::: cover variant=masthead kicker="운영 결과 보고"
+첫 1년의 발전량, 절감액, 고장 이력과 2027년 보완 예산 요청을 담았다.
+:::
+
+# 요약
+
+옥상 태양광 설비는 1년 동안 312MWh를 생산해 본사 전력 사용량의 8.4%를 대체했다.
+
+::: keyfigures
+- **312MWh** 연간 발전량 (예시)
+  * 2025. 10.~2026. 9. 인버터 누적 기록
+:::
+
+# 발전 실적
+
+## 월별 발전량
+
+표 1. 분기별 발전량 (예시)
+
+| 분기 | 예측 (MWh) | 실적 (MWh) |
+| --- | ---: | ---: |
+| 2026년 2분기 | 94 | 101 |
+
+자료: 인버터 원격 감시 기록
+```
+
+The headings print as "Ⅰ. 요약", "Ⅱ. 발전 실적" and "1. 월별 발전량"; the caption prints as "<표 1> 분기별 발전량 (예시)". The basis line may open with `*` or `-`; either reads as a list marker, not a dash.