Source profileQuality 82/100

nexu-io/open-design/design-templates/kami-deck/SKILL.md

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.

Source repository stars
91,167
Declared platforms
0
Static risk flags
0
Last source update
2026-08-25
Source checked
2026-08-25
DecisionCompatibilityInstallWorkflowPermissionsEvidenceSourceFAQ

Decision brief

What it does: where it fits

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.

Best for

    Not for

    • Tasks that require unconfirmed production actions or broad system permissions.
    • Environments where the pinned source and install steps cannot be inspected.

    Compatibility matrix

    Platform support, with evidence labels

    PlatformStatusEvidenceWhat to check
    CodexNot declaredNo explicit evidencePortability before use
    Claude CodeNot declaredNo explicit evidencePortability before use
    CursorNot declaredNo explicit evidencePortability before use
    Gemini CLINot declaredNo explicit evidencePortability before use
    Open the compatibility checker

    Installation

    Inspect first. Install second.

    The source command is displayed only when detected. A safe inspection prompt is always available so your agent can explain every action before execution.

    Source-detected install commandSource
    npx skills add https://github.com/nexu-io/open-design --skill "design-templates/kami-deck"
    Safe inspection promptEditorial

    Inspect the Agent Skill "kami-deck" from https://github.com/nexu-io/open-design/blob/edfa6b5f447e95cb120eae030f03baba00dc34de/design-templates/kami-deck/SKILL.md at commit edfa6b5f447e95cb120eae030f03baba00dc34de. List every install step, command, network request, credential, file read/write, external action, and rollback step. Explain whether it fits my task. Do not install or execute anything until I approve.

    Workflow

    What the source asks the agent to do

    1. 01

      Workflow

      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.[ ] All cover / chapter / end slides use ink-blue background
    2. 02

      What you get

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

      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
    3. 03

      Slide types

      A typical 11-slide deck:

      A typical 11-slide deck:
    4. 04

      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.Ask in two rounds (don't dump the whole list at once):
    5. 05

      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.

      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.

    Permission review

    Static risk signals and limitations

    No configured static risk pattern was detected

    This is not proof of safety. Runtime behavior, indirect dependencies, and hidden external systems are outside the static scan.

    Evidence record

    Why each signal appears

    EvidenceSourceComputedTestedEditorial
    SignalValueEvidence typeMeaning
    Quality score82/100ComputedDocumentation, specificity, maintenance, and trust rules
    Repository stars91,167SourceRepository attention, not individual Skill quality
    Compatibility0 platformsSourceDeclared in the catalog source record
    Usage guideautomated source guideEditorialGenerated or reviewed according to the visible evidence level

    Pinned source

    Provenance and original SKILL.md

    Repository
    nexu-io/open-design
    Skill path
    design-templates/kami-deck/SKILL.md
    Commit
    edfa6b5f447e95cb120eae030f03baba00dc34de
    License
    Apache-2.0
    Collected
    2026-08-25
    Default branch
    main
    View the original SKILL.md

    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

    KindBackgroundUse it for
    coverink-blueTitle plate at the start. Centered serif title + tagline.
    chapterink-blueRoman/Arabic numeral chapter divider.
    contentparchmentSection number + title + body + optional bullets.
    statsparchment3-4 metric cells (value · label · sub).
    quoteparchmentPull quote with ink-blue left rule + author signature.
    ctaparchmentClosing pitch + 1-2 buttons.
    endink-blueMega 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):

    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

    • 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.

    See also

    Frequently asked questions

    What to verify before installation and use

    What does the kami-deck source document cover?

    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.

    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.

    Alternatives

    Compare before choosing

    Computed 10014,671

    prowler-cloud/prowler

    postgresql-indexing

    PostgreSQL indexing best practices for Prowler: index design, partial indexes, partitioned table indexing, EXPLAIN ANALYZE validation, concurrent operations, monitoring, and maintenance. Trigger: When creating or modifying PostgreSQL indexes, analyzing query performance with EXPLAIN, debugging slow queries, reviewing index usage statistics, reindexing, dropping indexes, or working with partitioned table indexes. Also trigger when discussing index strategies, partial indexes, or index maintenance

    2026-08-240 platforms
    Computed 9965

    brucesongs/kali-claw

    insecure-design

    Insecure Design (OWASP A06:2025) focuses on security flaws in system architecture and design phases, rather than code implementation-level bugs.

    2026-08-192 platforms
    Computed 9916

    NintendaDev/unikit-ai

    unikit-docs

    Generate and maintain the project's TECHNICAL documentation from its codebase — scans the project structure, tech stack, and module boundaries, then writes a lean README landing page plus detailed topic pages (architecture, modules, setup, build, APIs), only the docs that are relevant. Use whenever the user wants to create, update, or validate documentation of the CODE or the project itself, e.g. "generate documentation", "create docs", "write the README", "update the project docs", "document th

    2026-08-190 platforms
    Computed 98269

    Aperivue/medsci-skills

    make-figures

    Generate publication-ready figures and visual abstracts for medical research papers. Supports ROC curves, forest plots, CONSORT/STARD/PRISMA flow diagrams, calibration plots, Kaplan-Meier curves, Bland-Altman plots, confusion matrices, pipeline diagrams, and journal-specific visual/graphical abstracts (python-pptx template-based).

    2026-08-240 platforms