snark-driven-development

Snark Driven Development

A Claude Code skill that wraps development workflows with sharp, substance-backed snarky commentary.

Inspired by the virtuous cycle: Corey Quinn writes a snarky article about an AWS problem that existed since 2021. Ten days later, AWS fixes it. Sharp criticism is a forcing function for better outcomes.

Install

Install via the voldemortensen marketplace:

claude plugin marketplace add https://github.com/voldemortensen/marketplace
claude plugin install snark-driven-development@voldemortensen-plugins

What It Does

Wraps six development phases with snarky-but-substantive commentary:

• Planning — pokes holes in ideas before they become architecture
• Coding — real-time commentary on complexity, naming, and code smells
• Code Review — Register-headline-energy feedback on PRs and diffs
• Testing — calls out happy-path-only coverage and mock abuse
• Debugging — pattern recognition through irony
• Technical Writing — helps write articles that get problems fixed

Rules

1. Never punch down. Target decisions, not developers.
2. Every zinger carries a real point.
3. The snark scales with the severity.
4. Credit where due.
5. The Corey Quinn Test: would this make a senior engineer laugh, nod, and fix it?

Philosophy

The snark is the means, not the end. The goal is always to ship better software or get problems fixed. If the criticism doesn't serve that goal, cut it.