Skip to content
SkillModel-led114 tokens in use

The Pragmatic Programmer

Engineering rules inspired by The Pragmatic Programmer: one owner per fact, independent modules, tracer bullets, automation and fast feedback.

3,324 stars on the repository MIT Licenseciembor/agent-rules-books · the-pragmatic-programmer
npx skills add ciembor/agent-rules-books --skill the-pragmatic-programmer
View source

Install command as written in the repository's README

Skill label

measured from its files

What installing The Pragmatic Programmer costs

38tokens idle
114tokens in use
4,113tokens, up to

Idle is what sits in context while the skill is installed. In use is its instructions, loaded when it runs. Up to adds the files its instructions link. Counts are approximate, made offline with cl100k_base.

Model dependence Model-led

Script-ledMixedModel-led

Mostly instructions, so how well it works depends on the model that follows them.

This describes the skill's structure, how much of it is scripts. It does not say how well it works.

Touches

Nothing detected: no shell, network, file writes, git or credentials in its files.

Declared tags come from the skill's frontmatter; detected ones from its scripts, its code blocks and the commands it names in inline code. This is detected, not audited.

How it scores

Quality

How well the skill is written, counted from its own files: its frontmatter, its steps, examples, stated output and constraints, its size and whether every file it ships is one it names.How we score it →
Needs attention
  • Frontmatter11/15
  • Structure0/25
  • Examples0/15
  • Output2/15
  • Size15/15
  • Resources10/15

Security

Starts at 100 and loses points for each thing in the skill's files that a reader should look at first.How we score it →
Excellent

No findings.

Repository health

Pre-computed score based on development activity, maintenance, community, maturity, and trend momentum.How we score it →
Fair
  • Development activity44
  • Maintenance72
  • Community52
  • Maturity28
  • Momentum40

This skill gives a coding agent a set of working rules inspired by Andrew Hunt and David Thomas’s The Pragmatic Programmer. When a task touches engineering judgment, the agent reads a compact rule set and applies it to design and code decisions.

The rules cover knowledge-level DRY, orthogonality, tracer bullets, prototypes, automation, explicit contracts, error and resource handling, debugging from reproduced facts and the broken windows rule. A longer version of the same rules sits beside it for harder tradeoffs.

What You Get

  • A compact rule set of decision rules, trigger rules and a final checklist that the agent loads when the skill applies
  • A longer reference version of the same rules for tradeoffs the compact version does not settle
  • A short nano version for very tight context budgets
  • Review prompts that look for duplicated knowledge, hidden coupling, manual steps and slow feedback

Common Use Cases

  • Reviewing a change that copies the same rule into the UI, API and database layers
  • Starting a feature with a thin end-to-end slice before building every layer
  • Turning a repeated manual release or setup routine into a versioned script
  • Deciding whether a prototype can be hardened or must be thrown away

What Makes It Unique

Most book-based skills cover one narrow practice such as refactoring or architecture. This one is a general engineering layer: it spans DRY, orthogonality, feedback loops, contracts, resources, concurrency visibility and team habits in one rule set. Each trigger rule says what to do when a specific situation shows up, such as the same fact in several files or a prototype turning into production code.

Under The Hood

The skill is a short SKILL.md that tells the agent to read the compact rules file before making design or code decisions, and to open the full file only when the compact one does not settle a tradeoff. There are no scripts. It does not fetch web pages, call APIs, run commands or write files. The rules shape how the agent reasons and what it proposes.

Join founders building with open source

Opinionated takes, migration guides, cost-saving tips, and insights from the open source ecosystem.

Subscribe on SubstackJoin 750+ subscribers