Skills and rules for Claude Code
Skills teach your agent how to do specific tasks. Rules tell it what it must and must not do. Both are pure leverage — until they all live in one ever-growing CLAUDE.md that every session pays for. Praxix treats them as a library instead.
The one-big-file problem
The default way to give Claude Code standing knowledge is CLAUDE.md: one file, always loaded. It starts clean. Six months later it holds your release checklist, your SQL conventions, three abandoned experiments, and a rule about a client you no longer have — and every session, on every task, spends tokens reading all of it.
Worse than the token cost is the attention cost. An agent whose context is stuffed with irrelevant instructions follows the relevant ones less reliably. Focused context isn’t just cheaper — it produces better work.
A library, not a file
Praxix keeps skills, rules, and reference documents as separate, named pieces in a library. Each piece does one job: a deploy checklist, a code-review standard, an API convention doc, a testing rule. You see everything you have in one place — and every session declares which pieces it loads.
Your always-on CLAUDE.md shrinks back to what genuinely belongs everywhere. Everything else loads on demand, in the sessions where it earns its tokens.
Scoped to the work
Release sessions get the release rules. Frontend sessions get the design conventions. A quick question gets almost nothing — and starts instantly. Presets capture the combinations you use repeatedly, so scoping is a click, not a ritual. Session defaults per project mean the routine case needs no thought at all.
Knowledge that compounds
Skills and rules aren’t static — sessions surface new gotchas, better checklists, decisions worth keeping. Praxix keeps notes and session history on your machine alongside the library, so what one session learns is there to load into the next. Over months, your library becomes the thing that makes your agent distinctly good at your codebase.
Try Praxix on your next session
Runs on your Mac — your code never leaves it. 30-day refunds.
Frequently asked questions
- What is a Claude Code skill?
- A packaged set of instructions for a specific kind of task — a deploy procedure, a review checklist, a house style. Claude Code loads it when the task calls for it, instead of carrying every instruction all the time.
- What belongs in CLAUDE.md vs. a skill or rule?
- CLAUDE.md should hold only what applies to every session in a project — a short identity-and-conventions card. Anything task-specific (procedures, checklists, domain references) does better as a scoped piece that loads on demand.
- Can I keep using the skills I already have?
- Yes. Praxix drives the official Claude Code CLI, and your existing setup keeps working. Praxix adds the layer where pieces are organized, scoped to sessions, and reused through presets.
- Does scoping actually save money?
- Yes, in two ways: fewer tokens spent loading irrelevant context on every session, and fewer wasted runs caused by an agent that missed the one instruction that mattered in a wall of ones that didn’t.