Vincent Driessen
Community@nvie · The Netherlands
Simplifying things for fun and profit.
Agent Skills by Vincent Driessen
Showing 10 vetted skills indexed across 1 GitHub repositories.
proper
Diagnose design friction and propose strategic refactorings before implementing features.
self-review
Analyze Claude Code session history to surface repeated user corrections and preferences for CLAUDE.md.
liveblocks-new-npm-package
Creates a minimal placeholder package and publishes it to NPM under the @liveblocks org.
tech-design
Draft, review, and refine technical design documents as Notion-compatible markdown files.
quick-explainer
Generates a single concrete worked example explaining what a PR, design doc, or plan changes.
pr
Opens a pre-populated GitHub PR creation page with a drafted title and body.
slack
Convert input text into a ready-to-paste Slack message using Slack-flavored markdown.
mikado
Breaks large refactorings into incremental steps using the Mikado method with revert-on-failure.
visually-explain
Generate a self-contained interactive HTML document that visually explains a specific codebase mechanism.
pr-review
Reviews GitHub pull requests through progressive, layered code analysis.
Frequently Asked Questions About Vincent Driessen
FAQPage SchemaWhat tasks can I accomplish with nvie's skills?▼
You can run Mikado-method incremental refactorings, draft and pressure-test technical design documents, review GitHub PRs layer by layer, open pre-drafted PR creation pages, write Slack-formatted messages, generate interactive HTML code explainers, publish placeholder @liveblocks NPM packages, and mine session history for reusable preferences.
Who are nvie's skills designed for?▼
They target senior software engineers and technical leads who make and defend architecture decisions, review pull requests before spending time on details, plan migrations and rollbacks, and communicate changes through PRs, Slack, and design documents.
How do I invoke these skills in practice?▼
Each skill runs as a slash command inside Claude Code: /proper for strategic redesign, /mikado for incremental refactoring, /pr and /pr-review for pull request work, /slack for message drafting, /tech-design for design docs, /quick-explainer and /visually-explain for comprehension, and /self-review for session analysis.
Does the PR skill create pull requests automatically?▼
No. The /pr skill only opens a pre-populated GitHub PR creation page in your browser with a drafted title and body in nvie's writing style. You review the draft and submit the pull request manually, keeping human approval in the loop.
What prerequisites do these skills require?▼
They require a Claude Code environment where slash-command skills are installed, plus access to the relevant context: a GitHub repository and branch for PR skills, a codebase or spec for explainers and refactoring, and NPM account access for publishing @liveblocks/* placeholder packages.