Let the audience find the protagonist of this page at a glance, and give the speaker enough cues to keep expanding. The Unix flavor comes from precise relationships, natural text, clear hierarchy, and intentionally preserved whitespace.
Workflow Routing
| Work | Entry |
|---|---|
| Generate, rearrange, or improve a presentation | Workflows/Generate.md |
Gotchas
- Purpose tags such as share and talk do not determine color. When no visual theme is specified, use hacker-dark.
- Two lines can be one judgment. Role is determined by the narrative function; line count only affects font size and pagination.
- Title, body, and cue sentence are not a mandatory trio. When the main sentence already completes the expression, let it stand on its own.
- Unicode connector lines use a monospaced grid, and Chinese nodes are typeset independently. Do not stuff Chinese character by character into fixed character cells.
- Passing static checks does not mean the visual holds up. The build tool fixes the template; the browser probe verifies the actually rendered page, and screenshots separately check visual hierarchy.
Two content contracts
| Mode | When to use | Fidelity target |
|---|---|---|
| faithful typography | An existing projection outline; rewriting not authorized | Original wording, order, tables, code, and source images |
| editorial talk arrangement | The user has asked to distill the script, reorganize the presentation, or redraw diagrams | Claims, evidence, qualifications, values, and relationships; on-screen text may be rewritten within the authorized scope |
Distillation or redrawing already authorized by the current request is executed directly, without asking again. Talk arrangement records editingBasis, and on-screen content returns to the full source via sourceIds; the full narration goes into notes, viewed with N. "Make it into a presentation" alone does not automatically authorize deleting or changing the author's content.
Design and implementation
- First read DesignSystem.md, and view the actual samples of CompositionReference.md by relevant layout.
- For the data contract see RenderingSpec.md; for the boundaries of relationship diagrams, native diagrams, and source code see ChartSpec.md。
- Use Tools/BuildDeck.ts to load the data into SloganTemplate.html; do not append CSS at the end of the artifact, and do not write a separate rendering branch.
- Preserve the section turns and pauses in the source. The number of content nodes, pages, and diagrams are not quality goals.
- Core claims, important limitations, and data remain readable at projection distance; auxiliary information recedes or goes into the script, and core information must not be shrunk to create whitespace.
Theme
Explicit choice > clear theme_* visual tag > hacker-dark. Ordinary topics and purpose tags do not participate in theme selection.
| Intent or parameter | theme |
|---|---|
| Default, Unix, terminal, dark | hacker-dark |
| Light Hacker, --hacker, compatible --cyber | hacker |
| -b / --theme=black | black |
| -r / --theme=red | red |
| -y / --theme=yellow | yellow |
Delivery
One ~/Downloads/{title}.html, fonts embedded, diagrams inline, offline, zero animation. → ↓ Space Enter j PageDown forward; ← ↑ k PageUp back; Home/End first/last page; F fullscreen; N script. Scrolling graphics and the script do not trigger page turns.
Static validation checks the current template and source data; use Interceptor to isolate the browser loading Tools/ProbeDeck.js, then review the full set of thumbnails and representative pages. When an isolated browser is unavailable, retain the artifacts and truthfully report that the visual re-verification was not completed; do not switch to the main browser to pass it off as acceptance.
Examples
- "Make the presentation according to the original outline, do not change the wording" → faithful, choose the layout based on semantics, and continue pages along source boundaries when necessary.
- "Put the essence of the narration into the display for me to expand on live" → editorial, distill the claims, contrasts, or relationships, and put the full script into notes.
- "Change the old ASCII diagrams to Unicode" → record the redrawing authorization, and verify the new diagrams by nodes, connections, and direction; real code is still preserved character by character.