Mmcp.market

kami-deck skill

by nexu-io·nexu-io/open-design·98k stars·Apache-2.0

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.

A100/100content scan

Is the kami-deck skill safe?

Clean: nothing in its files matched our rules. We read 3 files in the folder on 2026-09-28.

No findings.

Install the kami-deck skill

A skill is a folder. Copy it into your agent's skills folder and the agent loads it when the task matches its description.

git clone --depth 1 https://github.com/nexu-io/open-design.git /tmp/open-design
mkdir -p ~/.claude/skills
cp -r /tmp/open-design/design-templates/kami-deck ~/.claude/skills/kami-deck
available in every project

In the Claude apps, zip the folder and upload it from the Skills settings. The folder on GitHub

The instructions your agent would load

SKILL.md as published, without the frontmatter. Read it on GitHub

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

horizontally on one transformed flex track.

  • N viewport-sized slides (6-15 is the sweet spot) laid out

(#1B365D) with ivory text — the only place dark theme is used.

  • Cover and chapter slides flip background to ink-blue

(#f5f4ed) with serif at weight 500.

  • Content / stats / quote / CTA slides stay on parchment

counter (01 / 09).

  • Per-slide chrome strip: brand mark · deck title · live slide

nav are ink-blue too.

  • Tabular-nums on every counter, metric, page number.
  • Coral-free — kami's accent is ink-blue. Progress bar and dot

the language parameter.

  • Keyboard / wheel / touch nav, ESC overview grid, dot indicator.
  • Multilingual stack — EN / zh-CN / ja, set on :root via

Slide types

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):

  1. Identity round — name, mark, tagline, location, edition, language.
  2. 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

(#1B365D) with ivory text. All other slides are on parchment.

  • [ ] All cover / chapter / end slides use ink-blue background

font-variant-numeric: tabular-nums.

  • [ ] Ink-blue covers ≤ 5% of any parchment slide's surface.
  • [ ] Slide titles use serif weight 500 only. No italic.
  • [ ] All numeric stacks (counter, metrics, page numbers) carry

to the right; dot nav advances; the ink-blue progress bar ticks forward.

  • [ ] Press → / Space / scroll. Smoothly slides one viewport

single column; dot nav still works.

  • [ ] Press Esc. Overview grid appears with scaled thumbnails.
  • [ ] Resize to 1080px and 640px. Cover / content collapse to a
  • [ ] Lighthouse: contrast AA, font-display swap, no layout shift.

Boundaries

pick nothing.

  • Do not introduce a second accent color. Pick ink-blue or

and use solid hex from the table in design-systems/kami/DESIGN.md §2.

  • Do not use italic anywhere — emphasis swaps to ink-blue.
  • Do not use rgba() for tag fills; pre-blend over parchment

visual system). Kami is gradient-free, image-light, and hierarchy is carried by type.

  • Do not add a router. This is a single-file artifact.
  • Do not reuse Atelier Zero collage imagery (the open-design-landing

See also

horizontal swipe nav model, different visual language (Atelier Zero).

  • kami-landing — long-form one-pager sister skill.
  • design-systems/kami/DESIGN.md — token spec.
  • open-design-landing-deck — same

Claude skill (MIT). Kami's slides.py template documents the macro × 1.6 / micro × 0.6 ratios this skill applies.

  • Upstream: tw93/kami — original

More skills from nexu-io/open-design

  • Aarticle-magazineHuashu / huashu-md-html-inspired magazine article layout for turning Markdown or notes into a polished long-form HTML essay.
  • Aaudio-jingleAudio generation skill — jingles, beds, voiceover, and sound effects. Routes music requests to Suno V5 / Udio / Lyria, speech to MiniMax TTS / FishAudio / ElevenLabs V3, and SFX to ElevenLabs SFX or AudioCraft. Output is one MP3/WAV file saved to the project folder.
  • Aaudio-jingleAudio generation skill — jingles, beds, voiceover, and sound effects. Routes music requests to Suno V5 / Udio / Lyria, speech to MiniMax TTS / FishAudio / ElevenLabs V3, and SFX to ElevenLabs SFX or AudioCraft. Output is one MP3/WAV file saved to the project folder.
  • Ablog-postA long-form article / blog post — masthead, hero image placeholder, article body with figures and pull quotes, author byline, related posts. Use when the brief asks for "blog", "article", "post", "essay", or "case study".
  • Ablog-postA long-form article / blog post — masthead, hero image placeholder, article body with figures and pull quotes, author byline, related posts. Use when the brief asks for "blog", "article", "post", "essay", or "case study".
  • Abuild-testRun the project's build / typecheck / lint / test commands and emit the build.passing + tests.passing signals devloop convergence reads.
  • Acard-twitterTwitter quote or data card designed to pair with a post.
  • Acard-xiaohongshuXiaohongshu-style knowledge cards, arranged as a swipeable multi-card carousel.
  • Aclinical-case-reportStructured medical case presentation for clinical rounds, conferences, and documentation. Generates SOAP-format or narrative case reports with physiologically accurate vitals, labs, and evidence-based plans. Use when the brief mentions "case report", "case presentation", "SOAP note", "clinical case", "ward rounds", "case summary", or "patient presentation".
  • Aclinical-case-reportStructured medical case presentation for clinical rounds, conferences, and documentation. Generates SOAP-format or narrative case reports with physiologically accurate vitals, labs, and evidence-based plans. Use when the brief mentions "case report", "case presentation", "SOAP note", "clinical case", "ward rounds", "case summary", or "patient presentation".
  • Acode-importRead an existing repository's structure into the project cwd as a normalised snapshot the agent can analyse without re-walking the tree on every turn.
  • Acodex-interactive-capability-mapTurn a long-form article, thread, memo, or product narrative into a compact clickable capability map with a workflow loop, use-case matrix, and responsive detail panel.

All agent skills → · MCP servers