Skip to content

Destynova2/cli-code-skills / cli-forge-demo

cli-forge-demo

Unverified

Generate a reproducible live-demo kit for any project: a staged demo script (DEMO.md), deterministic seed and idempotent reset wired into the project's own task runner (make / just / task / npm / ansible / flux / chainsaw — never an imposed .sh), a pre-flight checklist, and a backup recording. Picks the best delivery support for the project (live, terminal GIF via VHS, asciinema cast/SVG, subtitled video, or a self-guided 'next-next' interactive walkthrough) and lets you force one. Tunes dramaturgy to the audience: technique, fonctionnel, commercial, or pédagogique. Use when the user says 'demo', 'démo', 'live demo', 'demo script', 'demo gif', 'record a demo', 'show this off', 'walkthrough', 'interactive tutorial', 'present OpenBao', 'sprint review demo', 'sales demo', 'pitch demo', 'reproducible demo', 'reset demo data', 'seed demo', 'demo magic', 'asciinema', 'vhs tape', 'demo that does not break'. Do NOT use for slide decks (use cli-forge-prez) or for a README (use cli-forge-readme).

FileKindSize
README.mdmarkdown983 B
SKILL.mdskill md15.0 KB
references/anti-patterns.mdmarkdown3.4 KB
references/demo-md-template.mdmarkdown2.3 KB
references/dramaturgy.mdmarkdown3.7 KB
references/gif-video.mdmarkdown3.4 KB
references/interactive.mdmarkdown2.7 KB
references/staging.mdmarkdown4.4 KB
references/tiers.mdmarkdown3.7 KB
references/tooling.mdmarkdown4.1 KB

references/interactive.md

View on GitHub
# Interactive Walkthrough — Self-Guided "Next-Next"

> **When to read:** Step 4 when support = interactive. The audience downloads the project and steps through it alone, with a verification at each step.

## What it is

A **matinée**: the demo replayed by the audience themselves. It is stepped markdown with copyable commands and a check after each step, in the lineage of Google Cloud Shell **teachme** tutorials, **Killercoda** scenarios, and VS Code **CodeTour**. The defining trait: the learner moves Next / Previous and **cannot get silently stuck** — every step tells them what success looks like.

## Format choice

| Target environment | Emit |
|---|---|
| Repo + local shell (most cases) | `walkthrough.md` — stepped markdown (portable, renders on GitHub) |
| Google Cloud Shell | `tutorial.md` with teachme step markers + `cloudshell_tutorial` link |
| Browser lab | Killercoda `index.json` + `step1.md…` + `background.sh` |
| In-editor code tour | `.tours/demo.tour` (CodeTour JSON) |

Default to portable `walkthrough.md` unless the project clearly targets one of the others.

## walkthrough.md skeleton

```markdown
# <feature> — hands-on walkthrough

> You'll end with: <the showstopper>. ~<n> min. Prereqs: <tools>.

## Setup (once)
\`\`\`
git clone <repo> && cd <repo> && make demo-seed
\`\`\`
✅ **Check:** `make demo-status` prints `ready`.
❌ If you see `<common error>` → `<fix>`.

## Step 1 — <action>
\`\`\`
<one copyable command>
\`\`\`
✅ **Check:** you should see `<expected>`.
❌ If instead `<symptom>` → `<recovery>`.
➡️ **Next:** Step 2.

## Step 2 — <action>
<same shape>

## You did it
You built <result>. Reset anytime with `make demo-reset`. Next: <link>.
```

## Rules

- **One action per step.** Two commands in a step is two steps.
- **Every step has a ✅ check.** A copyable verification command beats prose ("run `curl …`, expect `200`").
- **Every step has a ❌ recovery.** Anticipate the common failure; this is what prevents silent stuck.
- **Commands are copy-paste exact.** No `<placeholders>` inside fenced commands unless the step explains how to fill them.
- **Reuse the DEMO.md beats** as the spine so live and interactive never drift.
- **End with reset + next.** The learner must be able to return to `s0` and know where to go.

## Innovation hooks (optional, if the project supports it)

- **`demo next` stepper** — a tiny runner target that prints the current step, waits, then advances (state in a dotfile). Wire into the detected runner, not a stray script.
- **Self-check target** — `make demo-verify STEP=2` runs the step's ✅ check programmatically.
- **Branch-per-step** — `git checkout step-2` jumps to a known-good state, so a stuck learner skips ahead without falling off the golden path.
canvas-designanthropics/skillsCreate beautiful visual art in .png and .pdf documents using design philosophy. You should use this skill when the user asks to create a poster, piece of art, design, or other static piece. Create original visual designs, never copying existing artists' work to avoid copyright violations.Stars: 196kUpdated Claude CodeCodexVerifiedInstall
docxanthropics/skillsUse this skill whenever the user wants to create, read, edit, or manipulate Word documents (.docx files) or Word templates (.dotx files). Triggers include: any mention of 'Word doc', 'word document', '.docx', '.dotx', or requests to produce professional documents with formatting like tables of contents, headings, page numbers, or letterheads. Also use when extracting or reorganizing content from .docx or .dotx files, inserting or replacing images in documents, performing find-and-replace in Word files, working with tracked changes or comments, or converting content into a polished Word document. If the user asks for a 'report', 'memo', 'letter', 'template', or similar deliverable as a Word or .docx file, use this skill. Do NOT use for PDFs, spreadsheets, Google Docs, or general coding tasks unrelated to document generation.Stars: 196kUpdated Claude CodeCodexVerifiedInstall
pdfanthropics/skillsUse this skill whenever the user wants to do anything with PDF files. This includes reading or extracting text/tables from PDFs, combining or merging multiple PDFs into one, splitting PDFs apart, rotating pages, adding watermarks, creating new PDFs, filling PDF forms, encrypting/decrypting PDFs, extracting images, and OCR on scanned PDFs to make them searchable. If the user mentions a .pdf file or asks to produce one, use this skill.Stars: 196kUpdated Claude CodeCodexVerifiedInstall
pptxanthropics/skillsUse this skill any time a .pptx or .potx file is involved in any way — as input, output, or both. This includes: creating slide decks, pitch decks, or presentations; reading, parsing, or extracting text from any .pptx or .potx file (even if the extracted content will be used elsewhere, like in an email or summary); editing, modifying, or updating existing presentations; combining or splitting slide files; working with templates (.potx), layouts, speaker notes, or comments. Trigger whenever the user mentions "deck," "slides," "presentation," or references a .pptx or .potx filename, regardless of what they plan to do with the content afterward. If a .pptx or .potx file needs to be opened, created, or touched, use this skill.Stars: 196kUpdated Claude CodeCodexVerifiedInstall