Claude Skills

claude-skills

What this is

A set of guardrails for Claude Code, the AI coding tool. Each
one is a short rule that Claude loads by itself, at the moment it is about to do the thing that
rule covers. Almost every one exists because that mistake already shipped on a real project.

They are not prompts or personas. They came out of the lessons-learned records of four production
codebases, one of them a regulated UK property-management platform, so the examples are concrete
and a few are specific to that domain. Install the lot, fork it, or read two and steal the ideas.
The two that change the most behaviour for the least reading are
verify-the-effect, which says never call something done because a
command exited without error, and prove-it-can-fail, which says a
test that cannot go red is not a test.

Four kinds of thing live here.

- Skills: short playbooks Claude reads at the right moment. The table below lists all 56.
- Hooks: small scripts that run automatically around what Claude does. One stops and asks you
  before Claude uploads any code to GitHub. One checks a file Claude has just edited for mistakes,
  using whatever checker that project already uses. One looks up what has changed in your project
  since you last worked on it, so Claude is not working from an out-of-date picture.
- Norms: six one-line rules that apply in every session, listed in NORMS.md.
- Agents: reviewers Claude can hand a change to for a second opinion, listed under
  Agents.

It installs once per machine and applies to every project on it. You never run any of it by hand.

This repository is licensed under Apache-2.0 (see the LICENSE file). The three unslop-*
skills and the four legal skills (contract-review, legal-citation-integrity,
statute-to-obligations-register, legal-notice-handling)…