원클릭으로 Manus에서 모든 스킬 실행

iii-slides

스타1

포크0

업데이트2026년 5월 11일 20:33

Generate a single-file scroll-snap slide deck for an iii talk, demo, or design review. Same iii editorial register as the architecture and infographic skills — cream paper or warm dark, Inter Tight + JetBrains Mono, ember accent reserved for the binary axis. Each slide is exactly one viewport tall (100dvh). No auto-advance, no transitions on more than two elements, no marketing copy. Use when the user asks for a deck, a slide-deck, or a presentation about an iii project.

설치

Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.

Manus에서 실행

출처

iii-experimental

iii-experimental/diagram-skills

GitHub 저장소 열기 Creator 저장소 보기

다운로드

Manus에서 실행

iii Slides Skill

Generates a single-file HTML scroll-snap slide deck. The output is one self-contained deck.html with inline CSS and JS. The same iii editorial register as iii-architecture-diagram and iii-infographic — cream + dark themes, Inter Tight + JetBrains Mono, ember accent anchored to a binary axis.

When to use

The user explicitly asks for a deck, slides, or a presentation.
The audience will scroll or click through one viewport at a time.
The content fits the iii voice: numbers carry the prose, no marketing words.

When NOT to use

The deliverable is a single diagram. Use iii-architecture-diagram.
The deliverable is a dense multi-section reference. Use iii-infographic.
The user wants animated transitions or a presentation with auto-advance. The iii deck has neither.
The content has no real numbers and would be a marketing page. Refuse.

Workflow

Inventory the source — references/inventory.md. Count every section, decision, table row, footnote in the source document. Map each to ≥1 slide. A 7-section plan with 6 decisions is ~25 items, so the deck is 18–25 slides — not 10–13.
Pick the binary axis — the same --accent (paid / opt-in / composable) vs --signal (free / built-in / always-on) binding from iii-infographic. State it on the title slide's legend.
Plan layouts — for each slide, pick a slide type from references/slide-grammar.md: title, content, diagram, quote, two-column, data. Vary across the sequence.
Open the scaffold — templates/deck.html ships scroll-snap container + topnav theme cycle + 3 sample slides wired up.
Pull snippets — templates/slide-snippets/{title,content,diagram,quote,two-column,data}.html for additional slides.
Walk the checklist — references/checklist.md. Refuse anything in references/anti-patterns.md.

References

File	Covers
`references/tokens.md`	Color, typography, density (shared with `iii-infographic`)
`references/slide-grammar.md`	Scroll-snap container, 100dvh slides, slide types, type scale, navigation chrome
`references/inventory.md`	Source-document → slide mapping; the test for completeness
`references/checklist.md`	Pre-output gate
`references/anti-patterns.md`	Refuse-to-ship list

Templates in templates/deck.html + templates/slide-snippets/*.html.

Commands

commands/iii-slides.md is the entrypoint. Surfaces as /iii-slides <topic-or-source-file> in Claude Code.

iii context

For canonical iii primitive semantics (iii.registerFunction, iii.registerTrigger, worker registration, trigger types), see iii.dev/docs.

이 저장소의 다른 Skills

같은 저장소

iii-infographic

iii-experimental/diagram-skills

Generate a single-page, dense, engineering-poster site for an iii-based project. Reads like a printed system reference, not a marketing page. Six to eight numbered sections, real numbers from the code, cream-paper canvas (or warm dark) with ember-orange + signal-green carrying a binary semantic. Use when the user wants a reference asset (printable, citable) for an iii deployment, a worker, or any technical project sitting on the iii substrate (iii.dev). Also handles diff reviews, plan reviews, and project recaps in the same visual register.

2026-05-111

iii-architecture-diagram

iii-experimental/diagram-skills

Standalone architecture diagrams for iii projects. Output is `.svg` (+ optional `.png` via rsvg-convert). One focal element per diagram, max 9 nodes, ember accent reserved for the iii primary path. Cream paper canvas, Inter Tight + JetBrains Mono, type tags above every node, arrow labels masked. Use when the user asks for a diagram (SVG or PNG) of an iii deployment, a worker, or any inter-worker dataflow on iii (iii.dev).

2026-05-111

iii-playground

iii-experimental/diagram-skills

Generate a single-file, throwaway HTML editor for a specific task — drag-and-drop kanban, slider tuner, form editor, split-preview, or annotation canvas. Always ends in a "copy as prompt" or "copy as JSON" button so the user can paste the result back into the agent. Same iii editorial register as the architecture, infographic, and slides skills — cream paper or warm dark, Inter Tight + JetBrains Mono, ember accent on the export action. Use when the user asks for a tuner, a sliders panel, a draggable interface, a custom editor, a triage UI, or any one-off interactive HTML to manipulate values they'll feed back into the agent.

2026-05-111

name	iii-slides
description	Generate a single-file scroll-snap slide deck for an iii talk, demo, or design review. Same iii editorial register as the architecture and infographic skills — cream paper or warm dark, Inter Tight + JetBrains Mono, ember accent reserved for the binary axis. Each slide is exactly one viewport tall (100dvh). No auto-advance, no transitions on more than two elements, no marketing copy. Use when the user asks for a deck, a slide-deck, or a presentation about an iii project.
license	Apache-2.0
metadata	{"version":"1.0","author":"iii (https://iii.dev)","brand":"iii"}

iii Slides Skill

When to use

The user explicitly asks for a deck, slides, or a presentation.
The audience will scroll or click through one viewport at a time.
The content fits the iii voice: numbers carry the prose, no marketing words.

When NOT to use

The deliverable is a single diagram. Use iii-architecture-diagram.
The deliverable is a dense multi-section reference. Use iii-infographic.
The user wants animated transitions or a presentation with auto-advance. The iii deck has neither.
The content has no real numbers and would be a marketing page. Refuse.

Workflow

Inventory the source — references/inventory.md. Count every section, decision, table row, footnote in the source document. Map each to ≥1 slide. A 7-section plan with 6 decisions is ~25 items, so the deck is 18–25 slides — not 10–13.
Pick the binary axis — the same --accent (paid / opt-in / composable) vs --signal (free / built-in / always-on) binding from iii-infographic. State it on the title slide's legend.
Plan layouts — for each slide, pick a slide type from references/slide-grammar.md: title, content, diagram, quote, two-column, data. Vary across the sequence.
Open the scaffold — templates/deck.html ships scroll-snap container + topnav theme cycle + 3 sample slides wired up.
Pull snippets — templates/slide-snippets/{title,content,diagram,quote,two-column,data}.html for additional slides.
Walk the checklist — references/checklist.md. Refuse anything in references/anti-patterns.md.

References

File	Covers
`references/tokens.md`	Color, typography, density (shared with `iii-infographic`)
`references/slide-grammar.md`	Scroll-snap container, 100dvh slides, slide types, type scale, navigation chrome
`references/inventory.md`	Source-document → slide mapping; the test for completeness
`references/checklist.md`	Pre-output gate
`references/anti-patterns.md`	Refuse-to-ship list

Templates in templates/deck.html + templates/slide-snippets/*.html.

Commands

commands/iii-slides.md is the entrypoint. Surfaces as /iii-slides <topic-or-source-file> in Claude Code.

iii context

For canonical iii primitive semantics (iii.registerFunction, iii.registerTrigger, worker registration, trigger types), see iii.dev/docs.