
dwmkerr
Personal Claude Code plugin for dwmkerr with repo management and custom workflows
- version
- 0.1.6-rc5
- GitHub stars
- 24
Install
/plugin install dwmkerr@claude-toolkitRun it inside Claude Code after adding the marketplace with /plugin marketplace add dwmkerr/claude-toolkit.
Contents
Discovered from sourceSkills 5
drawio-diagram
Generate .drawio architecture diagrams with a consistent visual style. Always include a legend. Supports export to PNG, SVG, PDF, and self-contained HTML.
Workflow
- Understand the subject — read source material (repos, docs, README, user description)
- Plan the diagram — identify containers, capabilities, external services, and connections
- Generate the
.drawiofile — use the XML structure and style conventions below - Add a legend — always include a legend row at the top of the diagram
- Export — offer to export to PNG/SVG/PDF via draw.io CLI, or to self-contained HTML
XML Structure
Every .drawio file must follow this structure:
<mxfile host="Electron" version="28.0.6">
<diagram name="Page-1" id="unique-id">
<mxGraphModel dx="1100" dy="760" grid="1" gridSize="10" guides="1" tooltips="1" connect="1" arrows="1" fold="1" page="1" pageScale="1" pageWidth="1169" pageHeight="827" math="0" shadow="0">
<root>
<mxCell id="0" />
<mxCell id="1" parent="0" />
<!-- All diagram cells use parent="1" -->
</root>
</mxGraphModel>
</diagram>
</mxfile>
For larger diagrams, increase pageWidth and pageHeight as needed (e.g., 1400x900 or 1600x1000).
Element Types and Styles
Container (systems, layers, groupings)
Blue, rounded, bold title top-aligned.
rounded=1;whiteSpace=wrap;html=1;fillColor=#dae8fc;strokeColor=#6c8ebf;verticalAlign=top;fontSize=10;
Capability (features, components, public)
Green, rounded, bold title with description.
rounded=1;whiteSpace=wrap;html=1;fillColor=#d5e8d4;strokeColor=#82b366;fontSize=10;verticalAlign=top;
Existing / External (infrastructure, third-party)
Grey, rounded.
rounded=1;whiteSpace=wrap;html=1;fillColor=#f5f5f5;fontColor=#333333;strokeColor=#666666;verticalAlign=top;fontSize=10;
Tech Preview (experimental, private, future)
Purple, rounded.
rounded=1;whiteSpace=wrap;html=1;fillColor=#e1d5e7;strokeColor=#9673a6;fontSize=10;verticalAlign=top;
Process Step (automated actions, gates)
Orange, sharp corners.
rounded=0;whiteSpace=wrap;html=1;fillColor=#ffe6cc;strokeColor=#d79b00;fontSize=10;
Use Case (domain applications, verticals)
Yellow, italic, pill-shaped.
rounded=1;whiteSpace=wrap;html=1;fillColor=#fff2cc;strokeColor=#d6b656;fontSize=10;verticalAlign=middle;fontStyle=2
Outcome (key deliverable, result)
Dark green, white text. Use sparingly.
rounded=0;whiteSpace=wrap;html=1;fillColor=#008a00;strokeColor=#005700;fontColor=#ffffff;fontSize=10;
Protocol Indicator (interface type)
Small circle, 8pt font.
ellipse;whiteSpace=wrap;html=1;aspect=fixed;fontSize=8;fontStyle=0
Size: 25x25.
Annotation (ideas, notes, questions)
Sticky note shape, yellow.
shape=note;whiteSpace=wrap;html=1;backgroundOutline=1;fontColor=#000000;darkOpacity=0.05;fillColor=#FFF9B2;strokeColor=none;fillStyle=solid;direction=west;gradientDirection=north;gradientColor=#FFF2A1;shadow=1;size=20;pointerEvents=1;
Region (soft grouping)
No fill, dashed border.
rounded=0;whiteSpace=wrap;html=1;dashed=1;fillColor=none;strokeColor=#999999;
Infrastructure Bar
Full-width grey bar, typically at bottom.
rounded=1;whiteSpace=wrap;html=1;fillColor=#f5f5f5;strokeColor=#666666;fontColor=#333333;fontSize=10;
HTML Labels
Use HTML in value attributes for rich text:
- Bold title:
<b>Title</b> - Line break:
<br> - Small text:
<font style="font-size: 9px;">text</font> - Combined:
<font><b>Title</b><br>Description</font>
Standard element label pattern:
<font><b>Component Name</b><br>Brief description</font>
Connections
Always use orthogonal edges:
edgeStyle=orthogonalEdgeStyle;rounded=0;orthogonalLoop=1;jettySize=auto;html=1;
Add labels on edges where the relationship needs clarification.
Legend
Every diagram must include a legend row near the top. Use small pill-shaped elements (80x20) showing each element type used in the diagram:
<mxCell id="key-1" value="<span>Capability</span>" style="rounded=1;whiteSpace=wrap;html=1;fillColor=#d5e8d4;strokeColor=#82b366;fontSize=10;verticalAlign=middle;fontStyle=2" vertex="1" parent="1">
<mxGeometry x="20" y="40" width="80" height="20" as="geometry" />
</mxCell>
Space legend items 90px apart horizontally. Only include element types actually used in the diagram.
Export
draw.io CLI Export
# macOS
/Applications/draw.io.app/Contents/MacOS/draw.io -x -f png -e -b 10 -o output.drawio.png input.drawio
# Linux
drawio -x -f png -e -b 10 -o output.drawio.png input.drawio
Formats: png, svg, pdf, jpg
Key flags:
-x: export mode-f: format-e: embed diagram XML in output-b 10: border width-t: transparent background (PNG only)
After export, the .drawio source can be deleted since the export embeds the XML.
Self-Contained HTML Export
Generate a standalone HTML file that renders the diagram in a browser without draw.io installed:
<!DOCTYPE html>
<html>
<head>
<meta charset="utf-8">
<title>DIAGRAM_TITLE</title>
<style>
body { margin: 0; background: #f5f5f5; display: flex; justify-content: center; align-items: center; min-height: 100vh; }
.container { background: white; border-radius: 8px; box-shadow: 0 2px 10px rgba(0,0,0,0.1); overflow: hidden; }
</style>
</head>
<body>
<div class="container">
<div class="mxgraph" style="max-width:100%;border:1px solid transparent;" data-mxgraph='{"highlight":"#0000ff","nav":true,"resize":true,"toolbar":"zoom layers lightbox","edit":"_blank","xml":"ESCAPED_XML_HERE"}'></div>
</div>
<script src="https://viewer.diagrams.net/js/viewer-static.min.js"></script>
</body>
</html>
To create the HTML:
- Take the complete
<mxGraphModel>...</mxGraphModel>XML from the.drawiofile - XML-escape it for embedding in the
data-mxgraphJSON attribute (escape",<,>,&) - Replace
ESCAPED_XML_HEREwith the escaped XML - Replace
DIAGRAM_TITLEwith the diagram title
Open with open output.html (macOS) or xdg-open output.html (Linux).
File Naming
- Source:
name.drawio - Exports:
name.drawio.png,name.drawio.svg,name.drawio.pdf - HTML:
name.drawio.html
Layout Guidelines
- Place legend at top
- Use containers to group related components
- Infrastructure bar at bottom
- External services on the right side
- Process flows left-to-right
- Annotations (sticky notes) in margins
- Leave adequate spacing between elements (20-30px minimum)
Reference
See references/ in this skill directory for:
demo.drawio— example output with all element typesxml-and-export.md— detailed XML structure and CLI reference
My Repos
Guide for locating and working with dwmkerr's repositories.
Repository Structure
~/repos/
├── github/
│ ├── dwmkerr/ # Personal repos (github.com/dwmkerr)
│ │ ├── effective-shell/
│ │ ├── hacker-laws/
│ │ ├── claude-toolkit/
│ │ └── ...
│ └── mckinsey/ # McKinsey open source repos (github.com/mckinsey)
│ └── ...
Finding a Repository
1. Check Local First
Always check if the repo exists locally:
ls ~/repos/github/dwmkerr/<repo-name>
ls ~/repos/github/mckinsey/<repo-name>
2. If Local Repo Exists
When working with an existing local repo:
-
Record the current state before making changes:
cd ~/repos/github/dwmkerr/<repo> ORIGINAL_BRANCH=$(git branch --show-current) git stash --include-untracked -
Fetch for reference if you need other branches:
git fetch origin git checkout origin/main # or any branch for reference -
Always return to original state when done:
git checkout "$ORIGINAL_BRANCH" git stash pop
3. If Repo Not Found Locally
Check if it exists on GitHub:
gh repo view dwmkerr/<repo-name> --json name,url
If it exists remotely, clone it:
git clone https://github.com/dwmkerr/<repo-name> ~/repos/github/dwmkerr/<repo-name>
For McKinsey repos:
gh repo view mckinsey/<repo-name> --json name,url
git clone https://github.com/mckinsey/<repo-name> ~/repos/github/mckinsey/<repo-name>
GitHub Details
- Personal GitHub username:
dwmkerr - Personal repos path:
~/repos/github/dwmkerr/ - McKinsey repos path:
~/repos/github/mckinsey/
Common Repos
Some frequently accessed repositories:
effective-shell- Book and website for shell/terminal skillshacker-laws- Laws, theories, and patterns for developersclaude-toolkit- Claude Code plugins and skillsdotfiles- Personal configuration files
Example Usage
User: "Check my repo effective-shell for the chapter on pipes"
- Check local:
ls ~/repos/github/dwmkerr/effective-shell - If exists, work directly in the repo
- Search for content:
grep -r "pipes" ~/repos/github/dwmkerr/effective-shell/
User: "What branches are in my repo X?"
- Locate repo locally or clone
cd ~/repos/github/dwmkerr/X && git branch -a
PDF Sign
Sign and fill PDF forms programmatically. Works on both digital PDFs (with a text layer) and scanned PDFs (via OCR).
Signature image
Always ask the user where their signature image is — never assume a location, and never commit a signature image to a repository. A scanned signature (dark ink on white) works best.
If the image has a white background (typical JPG scan), convert it to a transparent PNG first — otherwise the overlay blanks out any text or lines beneath it:
from PIL import Image
img = Image.open(SRC_JPG).convert("RGBA")
img.putdata([(0, 0, 0, 0 if (r+g+b)//3 > 200 else 255-(r+g+b)//3)
for r, g, b, a in img.getdata()])
img.save(OUT_PNG)
Save the transparent version next to the original so it can be reused.
Setup
pymupdf in a venv (system Python is often externally managed):
python3 -m venv ./scratch/venv # or /tmp outside a repo
./scratch/venv/bin/pip install -q pymupdf pillow
OCR (scanned PDFs) needs tesseract: brew install tesseract, and set TESSDATA_PREFIX (Homebrew: /opt/homebrew/share/tessdata).
Approach
- Try text search first.
page.search_for("SIGNATURE:")— a digital PDF locates fields directly. - Scanned PDF →
page.get_text()returns empty. Fall back to an OCR textpage:tp = page.get_textpage_ocr(full=True, dpi=200) hits = page.search_for("SIGNATURE:", textpage=tp) - Place content relative to the found label rects (see recipe).
- Always render and visually verify each modified page before declaring done:
Read the PNG — misplaced marks are common on the first pass.page.get_pixmap(dpi=100).save("check.png")
Recipe
import os
os.environ.setdefault("TESSDATA_PREFIX", "/opt/homebrew/share/tessdata")
import pymupdf
doc = pymupdf.open(SRC)
page = doc[0]
tp = page.get_textpage_ocr(full=True, dpi=200) # omit for digital PDFs
def find(needle):
hits = page.search_for(needle, textpage=tp)
return hits[0] if hits else None
# Signature: transparent PNG spanning the line, right of the label
r = find("SIGNATURE:")
page.insert_image(pymupdf.Rect(r.x1 + 40, r.y0 - 32, r.x1 + 180, r.y1 + 4),
filename=SIGNATURE_PNG, keep_proportion=True)
# Text field: right of label, baseline-aligned
r = find("DATE:")
page.insert_text((r.x1 + 15, r.y1 - 2), "01/31/2026", fontsize=11, color=(0, 0, 0.55))
# Checkbox: box sits ~22pt left of its label text
r = find("Check here if your name")
page.insert_text((r.x0 - 22, r.y1 - 2), "X", fontsize=12, color=(0, 0, 0.55))
doc.save(OUT) # never overwrite the source
Blue-ish ink (color=(0, 0, 0.55)) reads as pen on printed forms. Match the form's date format (US forms: MM/DD/YYYY).
Gotchas
| Problem | Fix |
|---|---|
search_for finds nothing, no error | Scanned page with no text layer — check len(page.get_text()) == 0, use OCR textpage |
Label matches twice (e.g. DATE: also hits Check Date: header) | Filter hits by y-position, e.g. same line as the SIGNATURE match: abs(h.y1 - rsig.y1) < 8 |
| Partial-phrase match places mark mid-sentence | Anchor x on a reliably-found label (e.g. checkbox column from the first checkbox label), use the phrase match only for y |
| Checkbox X lands on text | Checkbox is left of label: x0 - 22 works for typical forms; verify visually |
| Signature overlay blanks out text/lines beneath it | White image background — convert to transparent PNG (see above) |
| Multi-copy documents (same letter × N pages) | Loop the letter pages, skip FAQ/back pages |
| Draft email already carries the old attachment after re-signing | Mail clients attach a snapshot; discard the draft and recreate it with the new file |
import fitz deprecation warning | Use import pymupdf |
Workflow
- Ask the user for the signature image location (and any fill values: date, printed name, phone)
- Save/locate the source PDF
- Sign to a new file
<name> - Signed.pdf— never overwrite the source - Render pages → view the PNGs → verify placement
- Iterate until correct, then hand back or attach to a draft email
Project Setup
Create a new GitHub repository with standard dwmkerr project configuration.
What Gets Created
- Private GitHub repo with description
- Branch protection - prevent direct push to main
- Squash merges only for pull requests
- Actions can create PRs enabled
- GitHub Pages enabled (Actions-based deployment)
- MIT License
- Basic README with intro and quickstart
- Sponsor badge and funding metadata -
.github/FUNDING.yml, a "thanks | donate" badge in the README, and afundingfield inpackage.jsonwhen present
Setup Process
1. Create the Repository
gh repo create <repo-name> \
--private \
--description "<short description>" \
--clone
2. Configure Repository Settings
# Require squash merges only, disable merge commits and rebase
gh api repos/dwmkerr/<repo-name> \
--method PATCH \
--field allow_squash_merge=true \
--field allow_merge_commit=false \
--field allow_rebase_merge=false \
--field delete_branch_on_merge=true
# Allow GitHub Actions to create PRs
gh api repos/dwmkerr/<repo-name> \
--method PATCH \
--field allow_auto_merge=true
# For org repos, workflow write permissions must be enabled at the org level
# first, otherwise the repo-level call below will fail with a 409 Conflict.
# For personal repos this call will 404 harmlessly.
gh api orgs/dwmkerr/actions/permissions/workflow \
--method PUT \
--field can_approve_pull_request_reviews=true \
--field default_workflow_permissions=write 2>/dev/null || true
gh api repos/dwmkerr/<repo-name>/actions/permissions/workflow \
--method PUT \
--field can_approve_pull_request_reviews=true \
--field default_workflow_permissions=write
# Enable GitHub Pages with Actions-based deployment
gh api repos/dwmkerr/<repo-name>/pages \
--method POST \
--field "build_type=workflow"
3. Set Up Branch Protection Ruleset
gh api repos/dwmkerr/<repo-name>/rulesets \
--method POST \
--field name=main \
--field target=branch \
--field enforcement=active \
--field 'conditions[ref_name][include][]=~DEFAULT_BRANCH' \
--field 'rules[][type]=pull_request' \
--field 'rules[][type]=deletion'
4. Create MIT License
Create LICENSE file:
MIT License
Copyright (c) 2025 Dave Kerr
Permission is hereby granted, free of charge, to any person obtaining a copy
of this software and associated documentation files (the "Software"), to deal
in the Software without restriction, including without limitation the rights
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
copies of the Software, and to permit persons to whom the Software is
furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in all
copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
SOFTWARE.
5. Create README
Follow this pattern. The badge row sits directly under the title, and the sponsor badge is always the last badge in that row:
# <repo-name>
[](https://github.com/sponsors/dwmkerr/sponsorships?frequency=one-time&amount=5)
<One-line description of what this project does.>
## Quickstart
<Minimal steps to get started - install and run.>
Example:
# my-awesome-tool
[](https://github.com/sponsors/dwmkerr/sponsorships?frequency=one-time&amount=5)
CLI tool for automating deployment workflows.
## Quickstart
Install and run:
\`\`\`bash
npm install -g my-awesome-tool
my-awesome-tool init
\`\`\`
6. Add Funding Metadata
Every public repo carries the same three pieces of funding metadata. The badge is the only ask in the README; do not add a "please sponsor" sentence.
Create .github/FUNDING.yml:
# Support 'GitHub Sponsors' funding.
github: dwmkerr
The README badge from step 5 links to the one-time tab of the sponsors page.
If the project has a package.json, add the funding field:
jq '.funding = {"type": "github", "url": "https://github.com/sponsors/dwmkerr"}' package.json > package.json.tmp && mv package.json.tmp package.json
If the README uses a <p align="center"> header block instead of a plain badge row, use the HTML anchor form as the last <a> in the badge paragraph:
<a href="https://github.com/sponsors/dwmkerr/sponsorships?frequency=one-time&amount=5"><img src="https://img.shields.io/badge/thanks-donate-ea4aaa?logo=githubsponsors&logoColor=white" alt="Donate"></a>
7. Set Up Release Please (Optional)
Release Please automates version bumps and changelogs from conventional commits. Skip this step if the project doesn't need automated releases.
Create release-please-config.json. Adjust release-type to match the project (common values: node, python, go, simple):
{
"$schema": "https://raw.githubusercontent.com/googleapis/release-please/main/schemas/config.json",
"include-component-in-tag": false,
"packages": {
".": {
"release-type": "node",
"bump-minor-pre-major": true,
"bump-patch-for-minor-pre-major": true
}
}
}
Create .release-please-manifest.json:
{
".": "0.1.0"
}
Version strategy for pre-1.0 projects:
bump-minor-pre-major: true— breaking changes bump minor (0.1.x → 0.2.0), not majorbump-patch-for-minor-pre-major: true—feat:commits bump patch (0.1.0 → 0.1.1), not minor
Both flags are required to stay in the 0.1.x line. Without bump-patch-for-minor-pre-major, every feat: commit bumps the minor version (0.1 → 0.2 → 0.3), which burns through version numbers before the project is stable.
If the project has a version file (e.g. package.json), set its version to 0.1.0 to match the manifest.
8. Initial Commit
git add LICENSE README.md .github/FUNDING.yml
# Include release-please files only if step 7 was done
git add release-please-config.json .release-please-manifest.json 2>/dev/null || true
git commit -m "chore: initial project setup"
git push -u origin main
Example Usage
User: "Create a new project called 'config-validator' for validating YAML configs"
gh repo create config-validator --private --description "CLI tool for validating YAML configuration files" --clone- Configure squash merges and branch protection
- Create LICENSE and README
- Push initial commit
Slides
Scaffold and manage presentation decks in any project. Two modes:
- Slidev mode (default) - Markdown-driven decks using
@slidev/cli. Best for project pitches, internal decks, README-driven content, and anything where the author edits markdown and lets Slidev render. Covered in the "Slidev Mode" section below. - Conference mode - Hand-built HTML deck modelled on the AI Native DevCon London 2026 talk. Dark theme, Inter + JetBrains Mono, right-arrow progressive reveal, fullscreen, page number, in-deck notes overlay, separate teleprompter sheet for a phone, deployable to GitHub Pages via a
gh-pagesworktree. No framework, no build step - the author edits HTML directly. Covered in the "Conference Mode" section further below.
0. Ask which mode
When the user invokes the skill, ASK upfront:
"Slidev (default) or conference (hand-built HTML)?"
Pick by signal too. Default to Slidev unless the user says any of: "conference", "conference talk", "conference deck", "hand-built", "no framework", "html deck", or references the AI Native DevCon style. If they pick conference, skip the Slidev sections and follow "Conference Mode" below.
Slidev Mode
1. Ask where to keep slides
Ask the user where to create the slides folder. Suggest ./slides as default.
2. Scaffold the folder
Create the following structure:
<slides-dir>/
├── slides.md # Slide content (Slidev markdown)
├── package.json # Slidev dependencies
├── Makefile # Convenience targets
└── public/ # Static assets (images, diagrams)
package.json
{
"name": "slides",
"private": true,
"scripts": {
"dev": "slidev slides.md --open",
"build": "slidev build slides.md",
"export": "slidev export slides.md"
},
"dependencies": {
"@slidev/cli": "^52.11.5",
"@slidev/theme-default": "^0.25.0"
}
}
Makefile
.PHONY: slides slides-build slides-export slides-setup
slides: node_modules ## Open slides in browser with hot-reload
npx slidev slides.md --open
slides-build: node_modules ## Build static SPA to ./dist
npx slidev build slides.md
slides-export: node_modules ## Export slides to PDF
npx slidev export slides.md
slides-setup: ## Install dependencies
npm install
node_modules: package.json
npm install
@touch node_modules
slides.md (starter)
Generate a title slide using the project name. Use this template:
---
theme: default
title: "<Project Name>"
---
# <Project Name>
<One-line project description from README or user prompt.>
---
# Overview
- Point one
- Point two
- Point three
3. Install dependencies
Run npm install inside the slides folder.
4. Add to .gitignore
If a .gitignore exists in the slides folder or project root, ensure node_modules/ and dist/ are ignored. Check before adding to avoid duplicates.
Content Generation
When asked to generate or write slide content:
- Read the source material (README, docs, solution.md, or user prompt)
- Write slides in Slidev markdown format:
---separates slides- YAML frontmatter on first slide sets theme and title
- Standard markdown for content (headers, lists, code blocks, images)
- Images go in
public/and are referenced as/image.png
- Keep slides concise — one idea per slide, max 5-6 bullet points
- Write directly to
slides.md
Slidev Markdown Quick Reference
---
theme: default
title: "Deck Title"
---
# Slide Title
Regular markdown content.
---
# Code Slide
\`\`\`python
def hello():
print("hello")
\`\`\`
---
# Image Slide
<img src="/diagram.png" class="h-80" />
---
layout: two-cols
---
# Left Column
Content here.
::right::
# Right Column
Content here.
---
layout: center
---
# Centered Content
Big statement.
Available Layouts
default— standard contentcenter— centered on pagetwo-cols— split with::right::separatorimage-right/image-left— content + image side by sidecover— title/cover slidesection— section divider
Styling
Keep slides.md readable. Prefer built-in layouts and theme classes before writing custom CSS. Add styles selectively — not preemptively.
Content first, styling after. When a slide does need a <style> or <style scoped> block, put it at the bottom of the slide, just above the closing ---. Slidev parses the whole slide regardless of position, so pushing CSS below the content means a reader opening slides.md sees the actual content first — if they then scroll past some styling, so be it.
If a pattern is reused across many slides (typography, card layouts, shared tables), promote it to the theme under themes/<name>/styles/ instead of repeating it inline.
Revision
When asked to edit slides:
- Read
slides.md - Make targeted edits — don't regenerate the whole deck
- Suggest
make slidesto preview changes
Themes
By default, use theme: default in frontmatter. Do NOT suggest or apply custom themes unless the user specifically asks about available themes.
Custom themes are local Slidev theme folders stored in this skill at themes/<name>/. To apply one, copy the theme folder into the slides directory and set theme: ./<name> in frontmatter.
Available Themes
qblabs
Style inspired by QuantumBlack's publicly available visual identity. All colors, fonts, and design patterns sourced exclusively from public materials:
- quantumblack.com — public website (redirects to mckinsey.com/capabilities/quantumblack)
- github.com/mckinsey/qbstyles — matplotlib theme, dark bg
#0C1C23 - brandfetch.com/mckinsey.com — public brand colors
For an example slide in this style, see references/qblabs-example-slide.html.
Setup: Copy themes/qblabs/ into the slides directory, then:
---
theme: ./qblabs
title: "Deck Title"
---
Layouts:
cover— dark navy background, blue accent bar, centered titledefault— clean white background, blue underline on h1section— dark navy section divider with blue accent
Key colors (from public QB website/branding):
#051C2C— Dark navy (hero/section backgrounds)#2251FF— Electric blue (accent, links, CTAs)#222222— Body text (on light backgrounds)#A2AAAD— Secondary text (medium grey)
Fonts: Georgia (serif, headings) and Arial (sans, body) — standard PowerPoint substitutes for Bower and McKinsey Sans which are not publicly licensed.
Utility classes: .qb-blue, .qb-navy, .qb-bg-dark, .qb-bg-light, .qb-accent-bar
Standalone HTML Slide Templates
Two hand-built, single-file HTML slides live in references/. Each is a self-contained 1920x1080 slide with no dependencies - open in a browser, edit, save.
- QuantumBlack dark exemplar (
references/qblabs-example-slide.html) - dark, corporate, agentic-engineering style. Use for QB-branded or dark technical decks. - dwmkerr.com timeline template (
references/dwmkerr-com-timeline-slide.html) - light off-white, shell-header,# timelineheading over four phase columns. Use for personal-site, terminal/shell-focused slides.
dwmkerr.com timeline slide in edit mode
Keyboard edit / save mode
Both slides support in-browser editing. Open the file, then:
| Key | Action |
|---|---|
E | Enter edit mode (click any text and type) |
Cmd/Ctrl+S | Save - downloads the edited slide as an HTML file |
Esc | Exit edit mode |
Press E, edit text inline, Cmd+S to download the updated HTML, Esc to finish. Edits are made live in the browser; save writes a new HTML file you keep. The E shortcut is ignored while a field is focused, so it never inserts a stray character.
Using the timeline template
Copy references/dwmkerr-com-timeline-slide.html, open it in a browser, press E and edit the text, then Cmd+S to save. To add columns, duplicate a .phase block and bump the count in the .phases grid; relabel the timeline ticks by editing the t0...t4 labels.
Conference Mode
A hand-built HTML conference deck. No framework, no Vue, no Slidev, no build step. The author edits presentation.html directly. Speaker notes live in presentation.md and are baked into a standalone notes.html teleprompter sheet for a phone or second screen.
When to use it
- A conference talk (20-45 minutes) where presence and feel matter as much as content.
- Dark theme, typographic, whitespace-led, minimal chrome.
- Custom interactions (right-arrow progressive reveal, hidden in-deck notes overlay, fullscreen toggle).
- Deploys to GitHub Pages via a
gh-pagesworktree, with separate public URLs for the deck and for the phone-readable notes sheet.
If the user wants a quick scaffold from a README, or wants Markdown-driven content with Slidev's built-in layouts, use Slidev mode instead.
For a complete real-world example of a finished conference deck (structure, slide markup), see references/conference-example.html — the final deck from a real AI Native DevCon talk.
Setup flow
- Ask where to keep the deck. Suggest
./presentationor a conference-specific folder name (for example./conferences/<year>-<event>/). - Copy everything under
themes/conference/template/into the target folder verbatim. Nonpm install, no dependencies. - Tell the user:
make devservespresentation.htmlonhttp://localhost:2663.make notesservesnotes.html(open on a phone for a teleprompter).- Edit
presentation.htmlto change slide content. - Edit
presentation.mdto change speaker notes, then regeneratenotes.htmlfrom it.
- If the user wants
make deployto work, ask for their site repo path and the public URL pattern, then updateSITE_REPO,PUBLIC_NOTES_URL, andPUBLIC_PRESENTATION_URLat the top of theMakefile.
File layout
<deck-dir>/
├── presentation.html # The deck (single hand-edited HTML file)
├── presentation.md # Single source of truth for speaker notes
├── notes.html # Baked teleprompter sheet (regenerated from md)
├── Makefile # dev / notes / deploy / deploy-presentation / deploy-notes / lab / help
├── images/ # QR codes, photos, diagrams
└── README.md # Quick start, conventions
Slide markup conventions
- Each slide is a
<section class="slide <type>" data-name="<unique-id>">block. - Each slide uses an eyebrow + heading pattern:
<div class="label-in">Section name</div>then<h3>One central idea</h3>(or<h1>for title slides,<h2>for disclaimer / punch). - Slides that should reveal items one-at-a-time on Right have
data-reveal="true"and mark each fragment withclass="revealable". - The provided slide types:
title,disclaimer,content,chartslide,punch(section divider),regtable(two-column bad-vs-good table, optionallyrecap-hero),jokes(progressive reveal list with punchline),title split(title + image / QR on the right).
Copy conventions
- No em-dashes. Use a regular hyphen. Do not "tidy up" hyphens into em-dashes anywhere.
- No full stops at the end of slide leads or headings. Body text and notes are normal prose.
- One central idea per slide. Whitespace-led. The slide is not the script.
Colour convention
Apply consistently when colouring words, lines, table rows, and markers.
| Token | Hex | Meaning |
|---|---|---|
| Red | #e8503a | Bad / dysregulating / warning |
| Green | #6bbf73 | Good / regulating / managing |
| Blue | #4c8dd6 | Accent / anchored to baseline |
| Yellow | #f2c94c | Support / highlight |
The slate accent (#5e8a9c) and warm rust (#d99161) are the deck's neutral accents - eyebrows, section punches, decorative rules.
Speaker notes flow
presentation.mdis the single source of truth for speaker notes. The deck (presentation.html) is the public artefact and should not carry full notes inline.- Each slide in
presentation.mdis a##or###heading. On-slide content sits above---; speaker notes sit below---. End each notes block with*Clock: X:XX*for pacing. - Top-level
#headings in the md are the author's organising structure (parts / acts) - they are scaffolding, not slides. Skip them when regenerating. - When notes change, regenerate
notes.htmlby rewriting the entries inside its<div id="list">block from the parsed md, pairing each md slide by index with the deck'sdata-nameorder. Keep thenotes.htmlshell (CSS, controls bar, fonts / theme JS) untouched.
Deploy pattern
make deploy-presentation and make deploy-notes publish straight to the gh-pages branch of SITE_REPO via a throwaway git worktree. Each pushes a single commit. The deck lives at <site>/presentation/presentation.html; the notes sheet lives at <site>/presentation/notes.html. The phone-readable notes URL is meant to be opened on a second screen during the talk.
Example Interactions
User: "Add slides to this project"
- Ask: "Slidev (default) or conference (hand-built HTML)?"
- If Slidev: ask where to keep them (suggest
./slides), scaffold folder withtheme: default, runnpm install, tell usercd slides && make slidesto open. - If conference: ask where to keep the deck (suggest
./presentationor./conferences/<year>-<event>/), copythemes/conference/template/*into it, tell usermake devto open.
User: "Create a conference talk deck" or "Set up a hand-built HTML deck"
- Skip the Slidev question - go straight to conference mode.
- Ask where to keep the deck.
- Copy
themes/conference/template/*into the target folder. - Tell user:
make devto preview, editpresentation.htmlfor content andpresentation.mdfor notes, regeneratenotes.htmlfrom md when notes change.
User: "Create slides from the README"
- If slides folder exists, read
slides.mdto understand current state - If no slides folder, scaffold first
- Read README.md
- Generate slide content and write to
slides.md - Suggest
make slidesto preview
User: "Add a slide about the architecture"
- Read
slides.md - Add new slide section with
---delimiter - Suggest
make slidesto preview
User: "What themes are available?" or "Use the qblabs theme"
- List available themes from the Themes section above
- If user picks one, copy the theme folder into the slides directory
- Update frontmatter to
theme: ./<name>
Commands 1
/next
Arguments
$ARGUMENTS
Context
- Branch: !
git branch --show-current - Recent commits: !
git log --oneline -10 - Working tree: !
git status --short - tasks.md: !
cat tasks.md 2>/dev/null || echo "No tasks.md found" - ideas.md: !
cat ideas.md 2>/dev/null || echo "No ideas.md found" - Framework detection: !
ls -d .obra/ .openspec/ docs/plans/ 2>/dev/null || echo "No framework directories found" - Open GitHub issues: !
gh issue list --limit 5 --state open 2>/dev/null || echo "No GitHub issues or gh not configured"
Instructions
Determine the mode from the arguments above:
Suggest Mode (default — no arguments, or arguments that aren't about wrapping up)
Analyze all the context above and produce:
- Current State — 1-2 sentences: what branch we're on, what the recent work looks like, whether the working tree is clean
- Suggested Next Actions — up to 5 bullet points, prioritized. Each bullet should:
- Start with a source tag like
[tasks.md],[GitHub #N],[ideas.md],[branch], or[plan] - Be a concrete, actionable next step
- Be brief (one line)
- Start with a source tag like
If a development framework is detected (Obra Superpowers plans in docs/plans/, OpenSpec, etc.), check for active plans and include their next steps in the suggestions.
Present the bullets and stop. Do not start working on anything.
Wrap-up Mode (arguments contain "done", "finished", "complete", "wrap up", or similar)
The user is finished with current work. Do:
- Summary — briefly describe what was accomplished this session based on conversation history and recent commits
- Ask what to do next using
AskUserQuestionwith these options:- Create/update PR — if on a feature branch with commits ahead of main
- Update tasks.md — mark current task done, add any new tasks discovered
- Update ideas.md — capture any ideas that came up during work
- Nothing, just summarize — only show the summary
- Execute whichever actions the user selects
Sponsors
Details
- Marketplace
- dwmkerr/claude-toolkit
- Source
- plugins/dwmkerr
- Category
- Community