[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7ASPS6Y9ZGK9KCDHNPDR75A":3,"skill-same:01M7ASPS6Y9ZGK9KCDHNPDR75A":76},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":24,"commitSha":25,"skillDirectory":26,"forksCount":27,"repositoryHtmlUrl":28,"repositoryHomepageUrl":6,"ownerHtmlUrl":29,"ownerBlogUrl":6,"ownerDescription":30,"updatedAt":31,"install":32,"resources":45},"01M7ASPS6Y9ZGK9KCDHNPDR75A","create-slides",null,"Use when the user asks for a slide deck, presentation, talk, or slides from a document, report, PR, notes, or topic. Builds one self-contained Machinify-branded HTML deck in a minimalist style, with headline-plus-visual slides, speaker notes, and every diagram drawn by architecture-design:create-diagram.","ozzycodes2\u002Fclaudellum","ozzycodes2","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F21285094?v=4","01M7ASJ57KTP519F96S4QGM7C5","Osniel Quintana","01M7ASJ589JS8S075AA92Y08S4",1,"MIT","https:\u002F\u002Fgithub.com\u002Fozzycodes2\u002Fclaudellum\u002Fblob\u002Fmain\u002Ftechnical-writing\u002Fskills\u002Fcreate-slides\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: create-slides\ndescription: Use when the user asks for a slide deck, presentation, talk, or slides from a document, report, PR, notes, or topic. Builds one self-contained Machinify-branded HTML deck in a minimalist style, with headline-plus-visual slides, speaker notes, and every diagram drawn by architecture-design:create-diagram.\n---\n\n# Create Slides\n\nTurn content into a minimalist Machinify HTML deck: one claim and one visual\nper slide, prose in the speaker notes. The output is a single `index.html`\nthat opens from disk, navigates with the keyboard, and prints one slide per\npage.\n\nReferences, relative to this skill:\n\n- `references\u002Fminimalism.md`: the slide rules. Read it before drafting.\n- `references\u002Fbrand.md`: colors, type, fixed elements, icons.\n- `assets\u002Fdeck-template.html`: the slide catalogue to build from.\n- `assets\u002Fmachinify.diagram-profile.md`: the create-diagram skin for slides.\n- `scripts\u002Fcheck_deck.py`: the rule checker.\n\n## Requirement\n\nDiagrams come only from the `architecture-design:create-diagram` skill. If\nit is not installed, stop and tell the user to install the\n`architecture-design` plugin. Do not hand-draw SVG, build diagrams from HTML\nboxes, or fall back to Mermaid.\n\n## Workflow\n\n### 1. Intake\n\nRead the source first: a file, a PR, a report, notes, or a topic. Then ask\nonly for what the source does not answer:\n\n- **Audience** and what they should do or believe afterwards.\n- **Duration.** Plan about one slide per two minutes, plus title and closing.\n- **Ground.** Light (default) or dark content slides.\n- **Output directory.** Default: a new directory named after the deck, next\n  to the source.\n\n### 2. Storyline and outline approval\n\nWrite one claim per slide, in the order the argument needs. A claim is a\nsentence the audience could disagree with: \"Tests own 70% of build time\", not\n\"Build time\". Then pick the visual that shows the claim:\n\n| The claim is about | Visual |\n|---|---|\n| Relationship, flow, structure, sequence, state, time, comparison, distribution, ranking, hierarchy | Diagram via create-diagram, which picks the type |\n| One number | `big-number` |\n| Three or four numbers | `stat-strip`, one marked `focus` |\n| Three parallel concepts | `icon-trio` |\n| One idea that needs no picture | `statement` slide |\n\nThere is no bullet-list slide. If a claim seems to need bullets, it is a\ndiagram, several slides, or speaker notes.\n\nPresent the outline as a table and wait for approval before building:\n\n| # | Layout | Eyebrow | Headline | Visual |\n|---|---|---|---|---|\n| 1 | title | CI review | Faster builds by **Q3** | — |\n| 2 | content | CI | Tests own 70% of build time | bar chart: stage durations |\n\nIterate on the table, not on built slides.\n\n### 3. Diagrams\n\nPrepare the profile once per deck:\n\n1. If `~\u002F.diagram-design\u002Fprofiles\u002Fmachinify.md` is missing, copy\n   `assets\u002Fmachinify.diagram-profile.md` there. If it exists and differs from\n   the bundled copy, show the difference and ask before replacing it.\n2. Write `\u003Cdeck-dir>\u002F.diagram-design` containing exactly `profile: machinify`.\n   If the deck directory sits inside a git repository whose root has no\n   marker, ask before writing one at the repository root, since it would\n   reskin every diagram in that repository. If an existing marker names\n   another profile, ask before changing it.\n\nFor each diagram slide, invoke the `architecture-design:create-diagram` skill\nfrom the deck directory, one diagram per call, with:\n\n- **The claim** the diagram must show, and the source facts behind it.\n- **Size preset `slide-body`**: the viewBox is `0 0 1104 520`, there is no\n  title or eyebrow inside the SVG, and there is no footer reserve.\n- **Profile `machinify`**, light or dark to match the slide.\n- **Detail `simplified`** and **audience `executive`** unless the audience is\n  engineers, then `balanced` and `mixed`.\n- **Output** `\u003Cdeck-dir>\u002Fdiagrams\u002F\u003Cslug>.html`, with a slug that describes\n  the diagram.\n\nLet create-diagram choose the diagram type and run its own checks. Then\nexport and inline:\n\n```bash\npython3 \u003Ccreate-diagram-dir>\u002Fscripts\u002Fexport_svg.py \u003Cdeck-dir>\u002Fdiagrams\u002F\u003Cslug>.html --system-fonts\n```\n\nPaste the resulting `\u003Csvg>` element into the slide's `.visual.dgm` div. Drop\nthe `\u003C?xml ...?>` line. Keep the diagram HTML next to the deck; it is the\nsource to edit later.\n\n### 4. Assemble\n\nCopy `assets\u002Fdeck-template.html` to `\u003Cdeck-dir>\u002Findex.html`. Keep the slide\nblocks the outline needs, in outline order, and delete the rest. For each\nslide:\n\n- Set the eyebrow (1–3 words) and the headline (7 words or fewer, one\n  `\u003Cstrong>` phrase at most).\n- Fill the one visual.\n- Put everything else in `\u003Caside class=\"notes\">`: explanation, sources,\n  caveats, numbers behind the numbers.\n- Add class `dark` to a content slide to put it on teal.\n\nDo not add footers, page numbers, or nav dots; the template's script\ngenerates them. Do not add CSS colors; use the template's variables.\n\n### 5. Check\n\n```bash\npython3 \u003Cthis-skill-dir>\u002Fscripts\u002Fcheck_deck.py \u003Cdeck-dir>\u002Findex.html\n```\n\nIt prints JSON and exits 1 on findings. Fix every finding by cutting, moving\ntext to notes, or re-requesting the diagram, never by loosening a rule. Then\nreview what the checker cannot see, from `references\u002Fminimalism.md`: one\naccent per slide, whitespace left empty, labels that are two to four words.\n\nReport the deck path, the slide count, and the diagram files. Mention that\n`N` toggles speaker notes and `F` toggles full screen.\n\n## Revising a deck\n\nEdit the outline first when the change moves the argument. Re-run the\ndiagram step only for diagrams whose claim changed, then re-export, re-inline,\nand re-run the checker.\n","# Create Slides\n\nTurn content into a minimalist Machinify HTML deck: one claim and one visual\nper slide, prose in the speaker notes. The output is a single `index.html`\nthat opens from disk, navigates with the keyboard, and prints one slide per\npage.\n\nReferences, relative to this skill:\n\n- `references\u002Fminimalism.md`: the slide rules. Read it before drafting.\n- `references\u002Fbrand.md`: colors, type, fixed elements, icons.\n- `assets\u002Fdeck-template.html`: the slide catalogue to build from.\n- `assets\u002Fmachinify.diagram-profile.md`: the create-diagram skin for slides.\n- `scripts\u002Fcheck_deck.py`: the rule checker.\n\n## Requirement\n\nDiagrams come only from the `architecture-design:create-diagram` skill. If\nit is not installed, stop and tell the user to install the\n`architecture-design` plugin. Do not hand-draw SVG, build diagrams from HTML\nboxes, or fall back to Mermaid.\n\n## Workflow\n\n### 1. Intake\n\nRead the source first: a file, a PR, a report, notes, or a topic. Then ask\nonly for what the source does not answer:\n\n- **Audience** and what they should do or believe afterwards.\n- **Duration.** Plan about one slide per two minutes, plus title and closing.\n- **Ground.** Light (default) or dark content slides.\n- **Output directory.** Default: a new directory named after the deck, next\n  to the source.\n\n### 2. Storyline and outline approval\n\nWrite one claim per slide, in the order the argument needs. A claim is a\nsentence the audience could disagree with: \"Tests own 70% of build time\", not\n\"Build time\". Then pick the visual that shows the claim:\n\n| The claim is about | Visual |\n|---|---|\n| Relationship, flow, structure, sequence, state, time, comparison, distribution, ranking, hierarchy | Diagram via create-diagram, which picks the type |\n| One number | `big-number` |\n| Three or four numbers | `stat-strip`, one marked `focus` |\n| Three parallel concepts | `icon-trio` |\n| One idea that needs no picture | `statement` slide |\n\nThere is no bullet-list slide. If a claim seems to need bullets, it is a\ndiagram, several slides, or speaker notes.\n\nPresent the outline as a table and wait for approval before building:\n\n| # | Layout | Eyebrow | Headline | Visual |\n|---|---|---|---|---|\n| 1 | title | CI review | Faster builds by **Q3** | — |\n| 2 | content | CI | Tests own 70% of build time | bar chart: stage durations |\n\nIterate on the table, not on built slides.\n\n### 3. Diagrams\n\nPrepare the profile once per deck:\n\n1. If `~\u002F.diagram-design\u002Fprofiles\u002Fmachinify.md` is missing, copy\n   `assets\u002Fmachinify.diagram-profile.md` there. If it exists and differs from\n   the bundled copy, show the difference and ask before replacing it.\n2. Write `\u003Cdeck-dir>\u002F.diagram-design` containing exactly `profile: machinify`.\n   If the deck directory sits inside a git repository whose root has no\n   marker, ask before writing one at the repository root, since it would\n   reskin every diagram in that repository. If an existing marker names\n   another profile, ask before changing it.\n\nFor each diagram slide, invoke the `architecture-design:create-diagram` skill\nfrom the deck directory, one diagram per call, with:\n\n- **The claim** the diagram must show, and the source facts behind it.\n- **Size preset `slide-body`**: the viewBox is `0 0 1104 520`, there is no\n  title or eyebrow inside the SVG, and there is no footer reserve.\n- **Profile `machinify`**, light or dark to match the slide.\n- **Detail `simplified`** and **audience `executive`** unless the audience is\n  engineers, then `balanced` and `mixed`.\n- **Output** `\u003Cdeck-dir>\u002Fdiagrams\u002F\u003Cslug>.html`, with a slug that describes\n  the diagram.\n\nLet create-diagram choose the diagram type and run its own checks. Then\nexport and inline:\n\n```bash\npython3 \u003Ccreate-diagram-dir>\u002Fscripts\u002Fexport_svg.py \u003Cdeck-dir>\u002Fdiagrams\u002F\u003Cslug>.html --system-fonts\n```\n\nPaste the resulting `\u003Csvg>` element into the slide's `.visual.dgm` div. Drop\nthe `\u003C?xml ...?>` line. Keep the diagram HTML next to the deck; it is the\nsource to edit later.\n\n### 4. Assemble\n\nCopy `assets\u002Fdeck-template.html` to `\u003Cdeck-dir>\u002Findex.html`. Keep the slide\nblocks the outline needs, in outline order, and delete the rest. For each\nslide:\n\n- Set the eyebrow (1–3 words) and the headline (7 words or fewer, one\n  `\u003Cstrong>` phrase at most).\n- Fill the one visual.\n- Put everything else in `\u003Caside class=\"notes\">`: explanation, sources,\n  caveats, numbers behind the numbers.\n- Add class `dark` to a content slide to put it on teal.\n\nDo not add footers, page numbers, or nav dots; the template's script\ngenerates them. Do not add CSS colors; use the template's variables.\n\n### 5. Check\n\n```bash\npython3 \u003Cthis-skill-dir>\u002Fscripts\u002Fcheck_deck.py \u003Cdeck-dir>\u002Findex.html\n```\n\nIt prints JSON and exits 1 on findings. Fix every finding by cutting, moving\ntext to notes, or re-requesting the diagram, never by loosening a rule. Then\nreview what the checker cannot see, from `references\u002Fminimalism.md`: one\naccent per slide, whitespace left empty, labels that are two to four words.\n\nReport the deck path, the slide count, and the diagram files. Mention that\n`N` toggles speaker notes and `F` toggles full screen.\n\n## Revising a deck\n\nEdit the outline first when the change moves the argument. Re-run the\ndiagram step only for diagrams whose claim changed, then re-export, re-inline,\nand re-run the checker.\n",{"name":5,"description":7},"main","a3f19bcc313571bff79dca391a83f9c4d38bb335","technical-writing\u002Fskills\u002Fcreate-slides",0,"https:\u002F\u002Fgithub.com\u002Fozzycodes2\u002Fclaudellum","https:\u002F\u002Fgithub.com\u002Fozzycodes2","Software Engineer | Engineering Manager | AI whisperer | ☕Enjoyer","2026-11-14 04:50:11",{"source":8,"skillName":5,"commands":33,"prompt":43,"zipAvailable":44},[34,37,40],{"tool":35,"command":36},"npx","npx skills add ozzycodes2\u002Fclaudellum --skill create-slides",{"tool":38,"command":39},"bunx","bunx skills add ozzycodes2\u002Fclaudellum --skill create-slides",{"tool":41,"command":42},"pnpm","pnpm dlx skills add ozzycodes2\u002Fclaudellum --skill create-slides","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fozzycodes2\u002Fclaudellum\u002Fblob\u002Fmain\u002Ftechnical-writing\u002Fskills\u002Fcreate-slides\u002FSKILL.md",true,[46,52,56,62,66,70],{"path":47,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":50,"sourceHtmlUrl":51},"assets\u002Fdeck-template.html","ASSET","资产文件",13644,"https:\u002F\u002Fgithub.com\u002Fozzycodes2\u002Fclaudellum\u002Fblob\u002Fmain\u002Ftechnical-writing\u002Fskills\u002Fcreate-slides\u002Fassets\u002Fdeck-template.html",{"path":53,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":54,"sourceHtmlUrl":55},"assets\u002Fmachinify.diagram-profile.md",33708,"https:\u002F\u002Fgithub.com\u002Fozzycodes2\u002Fclaudellum\u002Fblob\u002Fmain\u002Ftechnical-writing\u002Fskills\u002Fcreate-slides\u002Fassets\u002Fmachinify.diagram-profile.md",{"path":57,"resourceType":58,"resourceTypeDesc":59,"sizeBytes":60,"sourceHtmlUrl":61},"evals\u002Fevals.json","REFERENCE","参考文档",3405,"https:\u002F\u002Fgithub.com\u002Fozzycodes2\u002Fclaudellum\u002Fblob\u002Fmain\u002Ftechnical-writing\u002Fskills\u002Fcreate-slides\u002Fevals\u002Fevals.json",{"path":63,"resourceType":58,"resourceTypeDesc":59,"sizeBytes":64,"sourceHtmlUrl":65},"references\u002Fbrand.md",3499,"https:\u002F\u002Fgithub.com\u002Fozzycodes2\u002Fclaudellum\u002Fblob\u002Fmain\u002Ftechnical-writing\u002Fskills\u002Fcreate-slides\u002Freferences\u002Fbrand.md",{"path":67,"resourceType":58,"resourceTypeDesc":59,"sizeBytes":68,"sourceHtmlUrl":69},"references\u002Fminimalism.md",2935,"https:\u002F\u002Fgithub.com\u002Fozzycodes2\u002Fclaudellum\u002Fblob\u002Fmain\u002Ftechnical-writing\u002Fskills\u002Fcreate-slides\u002Freferences\u002Fminimalism.md",{"path":71,"resourceType":72,"resourceTypeDesc":73,"sizeBytes":74,"sourceHtmlUrl":75},"scripts\u002Fcheck_deck.py","SCRIPT","脚本",11035,"https:\u002F\u002Fgithub.com\u002Fozzycodes2\u002Fclaudellum\u002Fblob\u002Fmain\u002Ftechnical-writing\u002Fskills\u002Fcreate-slides\u002Fscripts\u002Fcheck_deck.py",[77,84,91,98,105,112],{"skillNo":78,"name":79,"nameZh":6,"description":80,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":81,"categories":82,"keywords":83,"publishedAt":19},"01M7ASQB3CTKMKDNAXD9DCF1YC","writing-design-docs","Use when the user wants to write a problem-statement design doc, says \"let's plan a feature properly\" \u002F \"write a design doc\" \u002F \"I'm thinking about how to do X\" for a non-trivial X, or before committing to a non-obvious technical direction","https:\u002F\u002Fgithub.com\u002Fozzycodes2\u002Fclaudellum\u002Fblob\u002Fmain\u002Ftechnical-writing\u002Fskills\u002Fwriting-design-docs\u002FSKILL.md",[],[],{"skillNo":85,"name":86,"nameZh":6,"description":87,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":88,"categories":89,"keywords":90,"publishedAt":19},"01M7ASQ6JD4QRV5ZKK2QME401Y","write-doc","Use when the user asks to write or draft a README, ADR, runbook, tutorial, how-to, explanation, or reference doc, or a caller passes \"type ADR\" or \"type README\". Picks the type, fills a template, adds diagrams. RFCs and design docs belong to writing-design-docs.","https:\u002F\u002Fgithub.com\u002Fozzycodes2\u002Fclaudellum\u002Fblob\u002Fmain\u002Ftechnical-writing\u002Fskills\u002Fwrite-doc\u002FSKILL.md",[],[],{"skillNo":92,"name":93,"nameZh":6,"description":94,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":95,"categories":96,"keywords":97,"publishedAt":19},"01M7ASQ1VWNVP1RE7M5D4G2QMG","review-doc","Use when the user asks to review, critique, score, grade, or \"how good is this doc\" for a Markdown doc or pasted text. Read-only. Scores it on the 20 Practical Prose dimensions and emits a findings table. Does not edit; fix-doc applies the findings next.","https:\u002F\u002Fgithub.com\u002Fozzycodes2\u002Fclaudellum\u002Fblob\u002Fmain\u002Ftechnical-writing\u002Fskills\u002Freview-doc\u002FSKILL.md",[],[],{"skillNo":99,"name":100,"nameZh":6,"description":101,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":102,"categories":103,"keywords":104,"publishedAt":19},"01M7ASPWST208JZNR7HF7J6KMV","fix-doc","Use when the user asks to fix, edit for prose quality, polish, tighten, humanize, or de-slop a Markdown doc or pasted text, or says \"make this read less AI\". Applies review-doc findings, generates flagged diagrams, lists substantive issues for the author, then runs the AI-tell pass last. Modifies the target.","https:\u002F\u002Fgithub.com\u002Fozzycodes2\u002Fclaudellum\u002Fblob\u002Fmain\u002Ftechnical-writing\u002Fskills\u002Ffix-doc\u002FSKILL.md",[],[],{"skillNo":106,"name":107,"nameZh":6,"description":108,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":109,"categories":110,"keywords":111,"publishedAt":19},"01M7ASPAKFY045KHR92Y4QFTWV","start-session","Open a Claude Code working session in a fresh, isolated git worktree, so the user can start a task with a single \u002Fstart-session \u003Cname>. Use at the START of a session when the user says \"start session\", \"start a worktree\", \"spin up a worktree for ABC-123\", \"begin work on \u003Cticket>\", or passes a name\u002Fticket to work under. Creates and ENTERS a worktree via the EnterWorktree tool (never `git worktree add`) under .claude\u002Fworktrees\u002F, named exactly after the argument, on a local branch `worktree-\u003Cargument>`. Reports what the worktree inherited (`.worktreeinclude` copies, symlinked node_modules) and whether its `.env` still points at the main checkout's stack. If the argument is a JIRA key (e.g. ABC-123, PROJ-1505), also loads that story with the Atlassian CLI (`acli`) when available and summarizes the implementation ask. Also renames the session to the argument (the same effect as `\u002Frename \u003CNAME>`) so it's easy to find in `\u002Fresume`. Then stops and waits — it sets up the workspace and context, it does not implement.","https:\u002F\u002Fgithub.com\u002Fozzycodes2\u002Fclaudellum\u002Fblob\u002Fmain\u002Fsession-mgmt\u002Fskills\u002Fstart-session\u002FSKILL.md",[],[],{"skillNo":113,"name":114,"nameZh":6,"description":115,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":116,"categories":117,"keywords":118,"publishedAt":19},"01M7ASNSKFMMXSG954AEMW8HAZ","exit-session","Tear down the ephemeral resources a Claude Code working session created, then quit the CLI — so the user can wrap up with a single \u002Fexit-session. Use when the user says \"exit session\", \"clean up this session\", \"tear down everything\", \"wrap up and clean up resources\", \"remove the worktree and scratch\", \"stop the background processes\", \"shut down the stack\", \"clean up the agent worktrees\", or asks to clean up after finishing a task — even if they only name one resource (assume they want the full sweep unless they scope it). Runs teardown permission-free: stops background processes and dev servers, Docker\u002Fcompose stacks plus their volumes, networks and images, local Tilt\u002FKubernetes, git worktrees, merged local branches, and temp\u002Fscratch files without prompting, then exits the CLI. Covers the worktrees and Docker resources left behind by subagents spawned during the session, not just the primary agent's own worktree — both determined from git locks and Docker labels rather than from recall. Never touches resources a still-live session holds.","https:\u002F\u002Fgithub.com\u002Fozzycodes2\u002Fclaudellum\u002Fblob\u002Fmain\u002Fsession-mgmt\u002Fskills\u002Fexit-session\u002FSKILL.md",[],[]]