Pragmatic Programmer
Apply the broad heuristics from Andy Hunt & Dave Thomas's "The Pragmatic Programmer" (1999, 20th-anniversary ed. 2019) — DRY, orthogonality, tracer bullets, reversibility, programming by coincidence, design by contract, broken windows, knowledge portfolio, good-enough software, and the dozens of tips that shape a craftsperson's everyday judgment. Use when stuck on a non-pattern-specific problem, when reasoning about engineering trade-offs, when picking up a new technology, when growing as a developer, or when articulating habits and stances that don't fit neatly into any single methodology.
Install
/plugin marketplace add vnovakovits/claude-skillsThe repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.
npx skills add vnovakovits/claude-skills --skill pragmatic-programmergit clone --depth 1 https://github.com/vnovakovits/claude-skills.git /tmp/claude-skills
mkdir -p ~/.claude/skills
cp -r /tmp/claude-skills/plugins/engineering-practices/skills/pragmatic-programmer ~/.claude/skills/pragmatic-programmerPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# The Pragmatic Programmer (Hunt & Thomas) Apply this skill when reasoning about software at the level of *general engineering judgment* rather than specific patterns, methodologies, or technologies. The book is a collection of stances — DRY, orthogonality, reversibility, tracer bullets, broken windows — that apply across languages, stacks, and decades. ## Core Philosophy **Software engineering is craft, not assembly.** Pragmatic programmers care about the work, take ownership of outcomes, and refuse to treat code as someone else's problem. **Think about your work.** The single trait that distinguishes good engineers from average ones: deliberate reflection on what they're doing and why. **Care about your craft.** Aesthetics, ergonomics, longevity — these matter. The team that doesn't care about quality ships worse software. **Take responsibility.** Don't blame the language, the framework, the previous developer, the deadline. Own your decisions; own your communications about them. **Provide options, not excuses.** When something is going wrong, the pragmatic response is "here are three things we could do, with these trade-offs" — not "this is broken because…". --- ## The Big Heuristics ### DRY — Don't Repeat Yourself > *Every piece of knowledge must have a single, unambiguous, authoritative representation within a system.*
Details
- Skill name
pragmatic-programmer- Repository
- vnovakovits/claude-skills
- Path
plugins/engineering-practices/skills/pragmatic-programmer/SKILL.md- License
- MIT
- Repo updated
- 16 November 2026
FAQ
What does the Pragmatic Programmer skill do?
Apply the broad heuristics from Andy Hunt & Dave Thomas's "The Pragmatic Programmer" (1999, 20th-anniversary ed. 2019) — DRY, orthogonality, tracer bullets, reversibility, programming by coincidence, design by contract, broken windows, knowledge portfolio, good-enough software, and the dozens of tips that shape a craftsperson's everyday judgment. Use when stuck on a non-pattern-specific problem, when reasoning about engineering trade-offs, when picking up a new technology, when growing as a developer, or when articulating habits and stances that don't fit neatly into any single methodology.
How do I install the Pragmatic Programmer skill?
Claude Code plugin: /plugin marketplace add vnovakovits/claude-skills. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Pragmatic Programmer popular?
It lives in vnovakovits/claude-skills, which has 5 GitHub stars and 2 forks.
Related skills
Accidental Cio
5vnovakovits/claude-skills
Apply Scott Millett's "The Accidental CIO — A Lean and Agile Playbook for IT Leaders" (Wiley, 2024) when designing or reviewing how a technology organisation decides, funds, governs and delivers work. Covers the five components of an adaptive IT operating model (organised, work, govern, talent, lead) and its four themes (outcomes over output, intrinsic motivation, being not doing agile, manage flow not people); matching method and governance to context via Cynefin and Wardley evolution; governance as demand management + funding + measurement + decision rights, shifting from project funding to
Agent Retro
5vnovakovits/claude-skills
Run a retrospective on a coding-agent session and improve the agent's environment, not the code. Combines Derby & Larsen's five-stage retrospective, Shigeo Shingo's poka-yoke (turn a mechanical mistake into a check that makes it impossible), and Matt Pocock's retro categories — navigation, automated checks, coding standards, steering files, tool economy, information access. Covers mining the session transcript for corrections, wrong turns and slow searches; deciding where each fix belongs (analyzer, hook, CI, reviewer standards, CLAUDE.md pointer, skill, doc or memory); the no-op test for stee
API Design
5vnovakovits/claude-skills
Design APIs that are clear, evolvable, and idiomatic to their protocol — covering REST (Fielding, Richardson Maturity Model, Massé), GraphQL, gRPC/protobuf, versioning strategies, pagination, error responses (RFC 7807 Problem Details), idempotency, authentication, documentation (OpenAPI), and the pragmatic trade-offs between RESTful purity and developer ergonomics. Use when designing a new endpoint, choosing between REST/GraphQL/gRPC, defining versioning, structuring error responses, deciding pagination strategy, or evaluating an existing API's evolvability.
Pre Commit Hooks
8Freddy-CHEN-ux/00_claude_skills
MANDATORY setup for all projects. Automated code quality enforcement before commits. Prevents bad code from entering repository.
Plugin Developer
8Freddy-CHEN-ux/00_claude_skills
Create and maintain Claude Code plugins following established patterns
Product Development Flow
5vnovakovits/claude-skills
Apply Don Reinertsen's "The Principles of Product Development Flow" (Celeritas, 2009), the quantitative case for flow in product work. Covers its 175 principles across eight areas (economics, queues, variability, batch size, WIP constraints, flow control under uncertainty, fast feedback, decentralised control) with verified codes; cost of delay and the SJF, HDCF and WSJF (CD3) sequencing rules; utilisation, Little's formula and why you control queue size rather than cycle time; the batch-size U-curve; congestion collapse; cadence; pooled versus dedicated capacity; and how to handle interrupt,
Browse the most popular Claude skills, all software development skills, or write your own with the skills generator.