From emacs-skills
Creates diagrams from the current context using D2, outputting PNG images. Invoked via /d2. Integrates with Emacs for theme-aware styling.
How this skill is triggered — by the user, by Claude, or both
Slash command
/emacs-skills:d2The summary Claude sees in its skill listing — used to decide when to auto-load this skill
Create a diagram from the most recent interaction context using D2. Generate a PNG image and output it as a markdown image so it renders inline.
Create a diagram from the most recent interaction context using D2. Generate a PNG image and output it as a markdown image so it renders inline.
emacsclient --eval '(face-foreground (quote default))'
emacsclient --eval '(frame-parameter nil (quote background-mode))'
The first returns a hex color like "#eeffff". The second returns dark or light. Reuse both for all subsequent diagrams.--theme 200 if background mode is dark, or --theme 0 if light.
# Use --theme 200 for dark, --theme 0 for light
d2 --theme 200 --pad 40 /tmp/agent-diagram-XXXX.d2 /tmp/agent-diagram-XXXX.png
Use --theme 200 for dark or --theme 0 for light, based on the Emacs background mode. Apply the queried foreground color to style.font-color and style.stroke on nodes and edges.
direction: right
node1: Label {
style.font-color: "#eeffff"
style.fill: "#2d3748"
style.stroke: "#eeffff"
}
node2: Label {
style.font-color: "#eeffff"
style.fill: "#2d3748"
style.stroke: "#eeffff"
}
node1 -> node2: label {style.stroke: "#eeffff"; style.font-color: "#eeffff"}
(frame-parameter nil 'background-mode). Use --theme 200 for dark or --theme 0 for light. Always use --pad 40./tmp/agent-diagram-$(date +%s).png). Never use descriptive names.style.font-color and style.stroke for all nodes and edges so the diagram is readable on the user's Emacs background.) on its own line.npx claudepluginhub xenodium/emacs-skills --plugin emacs-skillsGuides collaborative design exploration before implementation: explores context, asks clarifying questions, proposes approaches, and writes a design doc for user approval.
Creates structured, bite-sized implementation plans from specs or requirements before writing code. Useful for breaking down multi-step tasks into testable steps with file structure and task boundaries.
Resolves in-progress git merge or rebase conflicts by analyzing history, understanding intent, and preserving both changes where possible. Runs automated checks after resolution.