nexu-io/open-design

kami-deck

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.

82Collecting

See how to use it View GitHub source

npx skills add https://github.com/nexu-io/open-design --skill "design-templates/kami-deck"

Automated source guideDesignDeep source

Source checked Jul 28, 2026·Refresh due Oct 26, 2026

Reorganized from the pinned upstream SKILL.md

Source-grounded design guide: 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.

npx skills add https://github.com/nexu-io/open-design --skill "design-templates/kami-deck"

Check the pinned source

The pinned source contains enough sections and task detail for a source-grounded deep guide; automated content is still not an independent test.

701 source words · 8 usable sections

Design process

Read kami-deck through these 5 source sections

Sections are extracted automatically from the pinned SKILL.md and link back to the source.

Workflow

Ask in two rounds (don't dump the whole list at once):

SKILL.md · Workflow

Identity round — name, mark, tagline, location, edition, language.Content round — for each slide, kind + the typed fields.[ ] All cover / chapter / end slides use ink-blue background

What you get

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

SKILL.md · What you get

N viewport-sized slides (6-15 is the sweet spot) laid outCover and chapter slides flip background to ink-blueContent / stats / quote / CTA slides stay on parchment

Slide types

A typical 11-slide deck:

SKILL.md · Slide types

A typical 11-slide deck:

1. Gather the brief

Ask in two rounds (don't dump the whole list at once):

SKILL.md · 1. Gather the brief

Identity round — name, mark, tagline, location, edition, language.Content round — for each slide, kind + the typed fields.Ask in two rounds (don't dump the whole list at once):

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.

SKILL.md · 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.

SkillSignal prompt templates

Provide the task, context, and acceptance criteria

These prompts were written by SkillSignal from the source structure; they are not upstream text.

Source-grounded prompt

Use for a design task while explicitly checking the source sections.

Use kami-deck for this design task: [task]. Inputs and constraints: [details]. Work through these pinned SKILL.md sections: “Workflow”, “What you get”, “Slide types”, “1. Gather the brief”, “2. Pick the language stack”. Cite the concrete requirements that shape each step, do not invent capabilities absent from the source, and verify the result against: [acceptance criteria].

Design checklist

Verify each item before delivery

The source section “Workflow” has been checked.

The source section “What you get” has been checked.

The source section “Slide types” has been checked.

The source section “1. Gather the brief” has been checked.

Choose a different workflow

When another Skill is the better fit

design-review

Use when the user says "review the design", "check the UI", or wants a comprehensive UI/UX review. Uses a 7-phase methodology covering interaction, responsiveness, accessibility, and more.

A separate implementation from event4u-app/agent-config; compare its source, maintenance signals, and permission requirements.

Open source detail

neuropixels-analysis

Analyze Neuropixels extracellular recordings end-to-end with SpikeInterface. Covers loading SpikeGLX/Open Ephys/NWB data, preprocessing, drift/motion correction, Kilosort4 (and CPU) spike sorting, quality metrics, and unit curation (threshold-based, model-based UnitRefine, and AI-assisted visual review). Use when working with Neuropixels 1.0/2.0 recordings, spike sorting, or extracellular electrophysiology analysis.

A separate implementation from K-Dense-AI/scientific-agent-skills; compare its source, maintenance signals, and permission requirements.

Open source detail

scientific-brainstorming

Facilitates evidence-aware scientific ideation with independent generation, structured discussion, explicit assumptions, transparent evaluation, adversarial review, and decision logs. Use for early-stage research brainstorming or prioritizing candidate directions; hand off empirical validation, study design, ethics or regulatory review, and clinical questions to appropriate experts or skills.

A separate implementation from K-Dense-AI/scientific-agent-skills; compare its source, maintenance signals, and permission requirements.

Open source detail

FAQ

What does the kami-deck source document cover?

How do I install kami-deck?

The source record exposes this install command: npx skills add https://github.com/nexu-io/open-design --skill "design-templates/kami-deck". Inspect the command and pinned source before running it.

Repository stars

82,073

Repository forks

9,485

Quality

82/100

Source repository last pushed

2026-07-28

Quality breakdown

Based on traceable docs and repository signals; stars are not treated as quality.

82/100

Documentation26/30

Specificity16/25

Maintenance20/20

Trust signals20/25

Compare before choosing

Related Agent Skills and source variants

These links are selected from shared tasks, functions, stacks, platforms, and same-name variants. Compare the source owner, documentation, permissions, and maintenance signals.

design-review by event4u-app

Use when the user says "review the design", "check the UI", or wants a comprehensive UI/UX review. Uses a 7-phase methodology covering interaction, responsiveness, accessibility, and more.

neuropixels-analysis by k-dense-ai

scientific-brainstorming by k-dense-ai

citation-management by k-dense-ai

Comprehensive citation management for academic research. Search Google Scholar and PubMed for papers, extract accurate metadata, validate citations, and generate properly formatted BibTeX entries. This skill should be used when you need to find papers, verify citation information, convert DOIs to BibTeX, or ensure reference accuracy in scientific writing.

doc-and-modernize by github

Two related workflows for a locally-cloned codebase, in one skill. Documentation mode produces a single, comprehensive, verifiable architecture document primarily by reading files on disk (local-first) — use it whenever the user wants to understand, map, document, research, or onboard onto a codebase ("research this repo", "write up the architecture", "do an architecture deep dive", "document how this codebase works", "map the system design", "create an onboarding doc"). Modernization mode gener

View original Skill.mdThis page is parsed directly from the repository SKILL.md without editorial rewriting. Collected: Jul 28, 2026 · about 4 min

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

All cover / chapter / end slides use ink-blue background (#1B365D) with ivory text. All other slides are on parchment.
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 font-variant-numeric: tabular-nums.
Press → / Space / scroll. Smoothly slides one viewport to the right; dot nav advances; the ink-blue progress bar ticks forward.
Press Esc. Overview grid appears with scaled thumbnails.
Resize to 1080px and 640px. Cover / content collapse to a single column; dot nav still works.
Lighthouse: contrast AA, font-display swap, no layout shift.

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.

kami-deck

Source-grounded design guide: kami-deck

Read kami-deck through these 5 source sections

Workflow

What you get

Slide types

1. Gather the brief

2. Pick the language stack

Provide the task, context, and acceptance criteria

Verify each item before delivery

When another Skill is the better fit

design-review

neuropixels-analysis

scientific-brainstorming

What does the kami-deck source document cover?

How do I install kami-deck?

Related Agent Skills and source variants

design-review by event4u-app

neuropixels-analysis by k-dense-ai

scientific-brainstorming by k-dense-ai

citation-management by k-dense-ai

doc-and-modernize by github

kami-deck

What you get

Slide types

Workflow

1. Gather the brief

2. Pick the language stack

3. Write index.html

4. Self-check

Boundaries

See also

3. Write `index.html`