Menu · Packs and the catalog

Packs and the catalog

A pack is a set of rules plus the skills they need. The catalog of packs ships inside the binary.

Commands

unbound-paws search aws                           # find packs and single rulesunbound-paws add writing                          # for you: ~/.paws and ~/.claude/skillsunbound-paws add --project writing                # into this repo, to commitunbound-paws add --pick prose=stop-slop writing   # skip the promptunbound-paws add writing/humanizer-pr             # one rule (category/name)unbound-paws list                                 # packs, portal skills, how often each firedunbound-paws remove writing                       # its rules, and skills only it needed

Some packs offer a choice, such as which writing skill to use. add asks in a terminal and takes the default otherwise. --pick group=option answers ahead of time. --project works with add, remove and list, and uses the repo's .paws/packs, .claude/skills and .paws/installed.yaml.

Browse the same catalog by skill on the catalog page, or run unbound-paws ui.

Packs that ship

PackWhat it loads, and before what
writinghumanizer or stop-slop before PR bodies, commit messages and MCP sends. Choice: prose.
gitCheck work with real command output before every commit and push. Keep commit messages short Conventional Commits.
testingA TDD skill before source under src/ changes while no test has been touched. Choice: tdd, superpowers or mattpocock.
planningExplore or stress-test a design with you before a plan or spec file is written. Choice: planner, brainstorming or grilling.
disciplineKarpathy's guidelines and ponytail at session start and before new source files, against overbuilding and drive-by changes.
frontendA design skill before components and stylesheets change.
browseragent-browser before Playwright or Chrome MCP calls.
awsS3 buckets private, encrypted and tagged. IAM writes without wildcards or self-escalation. Terraform applies from a saved plan.
databasePostgres writes. Count before UPDATE or DELETE, use a transaction, migrations for schema changes, a backup before mass deletes.
dependenciesNew npm and pip/uv dependencies. Lockfiles, audits, install-script checks and license review.
secretsStaged changes scanned before each commit, .env and secrets/ kept out of git, Vault values never echoed.
shell-safetyList before recursive deletes, read back device targets before dd, state the reach of recursive chmod and chown.

How skills install

  • paws fetches a third-party skill from its upstream repo at a pinned commit, and refuses it if the content hash doesn't match the catalog. The paws repo redistributes nothing.
  • A skill you already have is left alone, and so is one paws installed that you've since edited. paws marks what it installs with a .paws-skill.json file and only replaces or removes a skill whose content still matches.
  • If add finds no paws hook in this project or globally, it tells you to run unbound-paws init.