name: kami-deck
en_name: "Turn a Study into a Lab Meeting Deck like a Senior Postdoc"
zh_name: "像资深博士后一样做组会研究汇报"
description: |
A lab-meeting deck on gut-microbiome links to sleep quality — the design, the results, the caveats, and the next experiment. Built as a decision-grade academic research deck for lab group, PI.
en_description: |
A lab-meeting deck on gut-microbiome links to sleep quality — the design, the results, the caveats, and the next experiment. Built as a decision-grade academic research deck for lab group, PI.
zh_description: |
像资深博士后一样做组会研究汇报——一份可商业交付的学术研究 Deck,围绕真实主题、证据链与决策目标组织。
tags:
- "academic-research"
- "academic-review-deck"
- "research"
- "grant"
- "review"
- "decision-deck"
- "commercial-slide-agent"
- "kami-deck"
triggers:
- "academic-review-deck"
- "academic-research"
- "Turn a Study into a Lab Meeting Deck like a Senior Postdoc"
- "像资深博士后一样做组会研究汇报"
- "research"
- "grant"
- "review"
- "html deck"
- "html slides"
od:
surface: web
mode: deck
featured: 4
audience: founders, researchers, design studios, conference talks
tone: editorial, restrained, print-first
scale: 6-15 viewport-locked slides
preview:
type: html
entry: index.html
design_system:
requires: false
craft:
requires:
- typographic-rhythm
- pixel-discipline
category: "academic-research"
scenario: "research"
example_prompt: "Create "Turn a Study into a Lab Meeting Deck like a Senior Postdoc" as a decision-grade Academic research deck in this template's own visual system. Subject: A lab-meeting deck on gut-microbiome links to sleep quality — the design, the results, the caveats, and the next experiment. Audience: lab group, PI. First ask only for missing essentials: audience, decision target, source-of-truth materials, deadline, and must-keep numbers. Then produce the slide plan, written slides, visual direction, speaker-ready structure, and a critic pass against this rubric: does the deck prove novelty without overclaiming."
inputs:
- id: brand
label: Brand identity (shared across slides)
- id: deck_title
label: Deck title shown in the per-slide chrome
- id: slides
label: Ordered list of typed slides (cover · chapter · content · stats · quote · cta · end)
- id: language
label: Primary language stack
parameters:
language:
type: enum
values: [en, zh-CN, ja]
default: en
description: Sets
--serif to Charter / TsangerJinKai02 / YuMincho respectively.
outputs:
- path: /index.html
description: Self-contained kami deck with horizontal swipe pagination.
capabilities_required:
- file-write
example_prompt: |
Build me a 9-slide kami-style internal deck for "Hokuto Research" —
a Q1 portfolio review. Cover slide on ink-blue with the firm name.
Chapter dividers between Macro, Equities, and Outlook. Three content
slides with ink-blue numbered headings. One stats slide showing
AUM / IRR / fund count. One closing CTA. End card with the firm
signature. Japanese language stack.
kami-deck
Sister skill to kami-landing. Produces a single
self-contained HTML file: a horizontal magazine-style swipe deck in
the kami (紙 / 纸) design system — print rhythm, ink-blue accent,
serif at one weight, no italic, no cool grays.
The navigation model is intentionally borrowed from the
guizang-ppt skill — ←/→ arrow keys, wheel /
swipe, ESC for the overview grid. The aesthetic stays kami: parchment
content slides, ink-blue cover and chapter slides, serif everywhere.
Design system source of truth:
design-systems/kami/DESIGN.md.
Read it before shipping. Tokens, type rules, and forbidden colors
all live there. Slide-specific scale ratios (macro × 1.6,
letter-spacing × 0.6 vs. print) are documented in §3 "Hierarchy"
and §5 "Layout Principles · Slides".
What you get
- N viewport-sized slides (6-15 is the sweet spot) laid out
horizontally on one transformed flex track.
- Cover and chapter slides flip background to ink-blue
(
#1B365D) with ivory text — the only place dark theme is used.
- Content / stats / quote / CTA slides stay on parchment
(
#f5f4ed) with serif at weight 500.
- Per-slide chrome strip: brand mark · deck title · live slide
counter (
01 / 09).
- Tabular-nums on every counter, metric, page number.
- Coral-free — kami's accent is ink-blue. Progress bar and dot
nav are ink-blue too.
- Keyboard / wheel / touch nav, ESC overview grid, dot indicator.
- Multilingual stack — EN / zh-CN / ja, set on
:root via
the language parameter.
Slide types
| Kind | Background | Use it for |
|---|
cover | ink-blue | Title plate at the start. Centered serif title + tagline. |
chapter | ink-blue | Roman/Arabic numeral chapter divider. |
content | parchment | Section number + title + body + optional bullets. |
stats | parchment | 3-4 metric cells (value · label · sub). |
quote | parchment | Pull quote with ink-blue left rule + author signature. |
cta | parchment | Closing pitch + 1-2 buttons. |
end | ink-blue | Mega serif kicker word + colophon footer. |
A typical 11-slide deck:
1. cover — ink-blue title plate
2. chapter — "01 / Why now"
3. content — manifesto
4. content — capabilities + bullets
5. stats — 4 numbers
6. chapter — "02 / How it feels"
7. content — method
8. content — selected work
9. quote — testimonial
10. cta — primary action
11. end — ink-blue kicker
Workflow
1. Gather the brief
Ask in two rounds (don't dump the whole list at once):
- Identity round — name, mark, tagline, location, edition, language.
- Content round — for each slide, kind + the typed fields.
2. Pick the language stack
Same as kami-landing:
EN → Charter, zh-CN → TsangerJinKai02 / Source Han Serif, ja →
YuMincho. JA also overrides --olive to #4d4c48 because YuMincho
strokes are thinner.
3. Write index.html
Output a single file with all CSS inline. Mirror the structure of
example.html. Use only the tokens from
design-systems/kami/DESIGN.md.
The runtime script (keyboard / wheel / touch nav, dot indicator,
progress bar, ESC overview) should match the model documented in
open-design-landing-deck/scripts/compose.ts.
Do not reuse the open-design-landing-deck CSS; the visual
language is different.
4. Self-check
Boundaries
- Do not introduce a second accent color. Pick ink-blue or
pick nothing.
- Do not use italic anywhere — emphasis swaps to ink-blue.
- Do not use
rgba() for tag fills; pre-blend over parchment
and use solid hex from the table in
design-systems/kami/DESIGN.md §2.
- Do not add a router. This is a single-file artifact.
- Do not reuse Atelier Zero collage imagery (the open-design-landing
visual system). Kami is gradient-free, image-light, and hierarchy
is carried by type.
See also