CLAUDE.md Example

dot-skills — Validator-First Definition of Done

Frames a markdown-authoring repo as red-green-refactor with the validator as the test gate, and gives an explicit 'Definition of Done —…

Type: CLAUDE.md Example
Repository: pproenca/dot-skills
GitHub stars: 211
License: MIT
Repo last updated: Aug 15, 2026
Source file: AGENTS.md

What dot-skills — Validator-First Definition of Done is

dot-skills — Validator-First Definition of Done is a claude.md example published in the pproenca/dot-skills repository on GitHub, which has about 211 stars. The repository describes itself as: “A collection of AI agent skills following the Agent Skills open format”

A CLAUDE.md file holds standing instructions that Claude Code reads at the start of every session in a project, such as conventions, commands, and rules. Examples like dot-skills — Validator-First Definition of Done show how other teams structure theirs.

In Claude Cowork, the equivalent places for this kind of guidance are your global instructions, project instructions, and folder instructions.

How to install dot-skills — Validator-First Definition of Done

Claude Code

Copy the parts that fit your project into CLAUDE.md at the project root, or into ~/.claude/CLAUDE.md for rules that apply everywhere.
Keep it short and specific; remove anything that doesn't match how your team works.

Claude Cowork

Put personal rules in Settings → Instructions for Claude (global instructions).
Put project or folder rules in the project's instructions or the folder instructions for that directory.

New to extending Cowork? Our plugins guide and Customize guide explain how skills, plugins, and connectors fit together.

Inside the source file

An excerpt from AGENTS.md, shared under the repository's MIT license. Read the full file on GitHub.

What This Repo Is

dot-skills is a curated collection of Agent Skills (markdown rule packs + scripts).

skills/.curated/ — stable, published skills
skills/.experimental/ — new / in-progress skills. New skills start here.
Skills are authored and evolved with the dev-skill plugin: /dev-skill:new, :ingest, :evolve, :validate.
dev-skill disciplines: distillation / composition / investigation / extraction. Don't mix disciplines in one skill dir — adding a scripts/ dir to a distillation skill flips its detected discipline and breaks validation. Build a sibling skill instead.

Definition of Done — run before every commit

When asked to "run all the skill validation and audit scripts" (or before committing skill changes):

npm run validate                          # skills-ref: structural validation of every skill
node scripts/check-versions.mjs           # flag STALE/DIRTY skill versions
scripts/generate-readme-tables --update   # regenerate README skill tables
npm test                                   # skills-ref validator test suite

Fix every reported issue, then commit & push. A goal is not complete until verified.

Task Management

Always use TaskCreate for any task with 2+ steps
Break tasks into small, atomic units (carpaccio slicing)
Each task should be completable in a single focused action
Include acceptance criteria in task descriptions
Set up task dependencies with addBlockedBy/addBlocks

Development Workflow — Validator-First

Most work here is authoring markdown rule files, so the validators are the test gate (the equivalent of red-green-refactor):

Red — run the validator and read the failures:

whole repo: npm run validate
single skill while authoring: dev-skill's discipline-aware validate-skill.js (/dev-skill:validate )

Green — fix rule files until the validator reports 0 errors.
Refactor — tighten wording / dedupe rules, then re-validate to stay green.

Never consider a skill done while the validator reports errors.
When changing the tooling itself (scripts/, tests/), keep classic TDD: add/extend a fixture in tests/, watch it fail, then make npm test pass.

Plan Mode

At the end of each plan, give me a list of unresolved questions to answer, if any. Use the AskUserQuestions to clarify.
Make sure that the plan leads to comprensive list of tasks, dependencies defined where possible, it's better to slice tasks like carpaccio than overly broad tasks

Gotchas

Skill description ≤ 1024 chars (enforced by skills-ref). This is the most common validation failure — check length before committing a new or edited SKILL.md.
README tables are generated — always run scripts/generate-readme-tables --update; never hand-edit the skill tables in README.md (they get clobbered).
Per-skill validation during authoring uses dev-skill's validate-skill.js, which is separate from skills-ref and discipline-aware; aim for 0 errors.

Before you install

Read the whole file first. Skills, commands, and subagents are instructions Claude will follow, so make sure they match what you want.
Check which tools, scripts, or MCP servers it uses. Local servers and scripts run with your permissions.
Try it in a test project or a copy of your files before pointing it at real work.
Pin the version you tested, and review changes before updating.
Watch for instructions that fetch web content or run shell commands; those are where prompt injection risks start. See our prompt injection guide.

FAQ

What is dot-skills — Validator-First Definition of Done?

dot-skills — Validator-First Definition of Done is a claude.md example for Claude Code and Claude Cowork from the pproenca/dot-skills repository on GitHub. Frames a markdown-authoring repo as red-green-refactor with the validator as the test gate, and gives an explicit 'Definition of Done —…

How do I install dot-skills — Validator-First Definition of Done in Claude Code?

Copy the parts that fit your project into CLAUDE.md at the project root, or into ~/.claude/CLAUDE.md for rules that apply everywhere. Keep it short and specific; remove anything that doesn't match how your team works.

Can I use dot-skills — Validator-First Definition of Done in Claude Cowork?

Put personal rules in Settings → Instructions for Claude (global instructions). Put project or folder rules in the project's instructions or the folder instructions for that directory.

Is dot-skills — Validator-First Definition of Done safe to install?

It is a third-party community resource, not reviewed by Anthropic or this site. Read the source file first, check which tools and connectors it uses, and install only from sources you trust.

Similar resources

Browse all skills, subagents, and plugins →

Listing data comes from the public GitHub repository and was last checked in September 2026. Excerpts are © their authors and shared under MIT. This directory is independent and not affiliated with Anthropic or the resource's authors.