Brainfile is a maintained operating system for Claude Code — the rules it works by, the memory files that hold how you work, and a weekly feed that keeps both current as the platform changes. It is built for owners who want to run their business on AI and think about infrastructure never.
Not ready for the trial? Get the free Brainfile email: a Claude Code tip every Tuesday and Thursday, plus a Sunday recap of the week.
Everything on this page is in the product today. If it has not shipped, it is not listed and it is not sold.
This is not a mockup. It is a real excerpt of the sanitized operating file this business runs on, served from this site.
### Law #19: Build-and-Verify (EP directive 2026-03-20) After building ANY script, feature, or pipeline component, verify the FULL chain — not just "it exists": 1. **Runs:** Does it execute without errors? (`python3 script.py` succeeds) 2. **Output correct:** Does it produce the expected output? (Spot-check, not just "no errors") 3. **Consumed:** Is the output read by something downstream? (Dashboard, email, another script) 4. **Wired:** Is it scheduled to run automatically? (LaunchAgent, cron, pipeline hook) - **"Script exists" ≠ "script runs" ≠ "output consumed."** All four must be true. - Root cause: 3+ `ep_had_to_ask` entries from build-and-forget pattern (ITC pipeline, dashboard generators, scripts not wired to cron). - After EVERY build task: verify all 4 links in the chain before marking done.
A capable assistant with no memory of how you work will do what you literally asked. The same assistant, running on your Brainfile, does what you actually needed — because the rules it loaded remember your setup and make it check its own work before it says done.
1 · It remembers your business. It catches your mistakes.
Done. I opened the homepage, found the price, and changed it to $49.
Your prices live in one source file, and the pages are generated from it — hand-editing the HTML would be wiped on the next build, so I updated the source.
Rebuilt the 3 pages that display a price.
Then checked the rest: an FAQ answer still quoted the old $99. Fixed that too.
All four places now read $49 — confirmed on the live pages before calling it done.
2 · It stays current.
Nothing tells you. The setup keeps running the old way until something quietly stops working, and the first sign is the thing that didn't happen.
Your next pull carries the updated pattern, and the weekly freshness note says in plain English what changed and what it means for your setup.
Two illustrations of what the shipped pattern files and the weekly freshness feed produce — the same kind of rule you can read in full above, applied to a real request, and the maintenance that keeps it true afterwards. Not testimonials, not mockups.
You can download a set of rules today for nothing. Here is the honest argument for paying for one instead.
Claude Code ships roughly weekly. A configuration pointing at a retired model or a removed setting does not throw an error — it quietly stops working, and there is no way for a non-technical owner to know. Perishability is the whole reason antivirus is a subscription.
Your decisions, preferences and context build up in plain files on your own disk. After six months that folder is genuinely yours and could not be recreated in an afternoon. It is the one asset in this product a competitor cannot copy, because it is not ours.
Claude Code changes most weeks. We check those changes against the files you run and ship the fixes as a versioned weekly feed you pull. With a downloaded rule set nobody does that for you; you would be the one reading release notes.
Everything below is live right now and verifiable. This list is the product: if something is not on it, we do not sell it.
This is the actual payload, not a mock-up:
# Brainfile update — v16 (2026-10-12)
Merged from the Brainfile Freshness Feed. These are cadence updates to apply to how
Claude works in this project.
## Apply these patterns
- Stay current: why a new model stays greyed out after you update, and the fix: Paid packs: the rule .claude/rules/stay-current.md is included, so Claude runs the two-line check itself when you say a model is missing. Bundle: add stay_current/claude_current.py --hook as a SessionStart hook (snippet in stay_current/README.md) to get told at session start. Open repo: brainfile/STAY-CURRENT.md.
- The red-green guard rule now ships in every paid role pack (shared-rules layer): Keep shared rules in ONE file and overlay it into every profile you ship or reuse, rather than editing N copies. Then check the drift the same way we do: measure how far each surface trails your newest improvement, and put a heartbeat on the surface with the longest gap so the drift pages you instead of being discovered.
- guards/ — prove your own checks can still fail (red-green contract + prove.py): Copy guards/prove.py next to your checks and give each one a selftest(inject_defect) that returns prove_cases(...). Run both phases and capture the exit code into a variable — never pipe a red phase to tail, because $? after a pipeline is the last stage's status and is therefore always 0. Then paste the GUARDS.md rule block into your own CLAUDE.md so your agent applies the contract to every new check without being asked.
… (full feed ships in the pack)
This is the real v16 feed — the latest one shipping in the pack (2026-10-12). The next feed ships with the next real change — we never backfill fake updates.
Start free. Basic is the running system. Pro adds the 15 role packs and the stay-current rule. Every line on these cards is in the product today.
30 days of the full Basic pull, no card. Every file you pull is yours to keep.
Email only. One email address, one trial.
Billed monthly, cancel anytime.
Basic runs the system: pattern files, freshness feed and guardrails. Pro adds the 15 role packs.
or $999/yr — $83/mo billed annually.
Card only at the end of the trial. Cancel any time and keep every file.
Not ready for a subscription? We audit your existing Claude Code or agent setup and send back a scored report and a prioritized fix list, worst first.
Team and company setups are arranged per organization. There is no public team price and no team checkout. Tell us who it is for and how many people, and a person writes back.
Most trials end with a locked door. That is a bad fit for a product whose value is a folder of your own decisions — so ours is designed the other way round.
You keep every file you pulled, permanently, including your memory folder. The weekly feed stops at the last version you pulled. There is nothing to uninstall and nothing to hand back.
A practical Claude Code tip every Tuesday and Thursday, plus a Sunday recap of the week.
Double opt-in. Unsubscribe in one click. We never sell or share your address.
You keep them. All of them, permanently — the rules, your accumulated memory folder, and the last freshness feed you pulled. It is plain text on your own disk and we will not try to take it back. What stops is the running service: new feed versions and, on Pro, the role packs' updates.
No. Brainfile runs inside your own Claude Code on your own machine. Your files never leave it. The only thing that crosses the network is the pull that fetches your setup, which is authenticated with a licence token and sends us nothing about your work.
No, and deliberately so. There are no zips and no download links on this site. Your setup is pulled from a licence-gated endpoint each time, which is what lets it stay current without you ever downloading, installing or merging anything.
You need to be able to open Claude Code in a folder and paste one line. After that you type start and answer 10 plain-English questions; Claude writes your files from the answers. If you would rather we look at an existing setup for you, that is the Setup Audit.
The 30-day free trial, the cloud pull, interview onboarding, the 10 pattern files, the conversation saver and the weekly freshness feed. Pro adds the 15 role packs and the stay-current rule. That is the whole product; nothing on this page is a promise of something later.
You should not, if a static file is what you want — there are good free ones, including our own Free Starter Kit. You pay for the part a file cannot do: staying current with a platform that ships weekly, and a memory of your business that builds up in files you own.
One click in the billing portal, or email [email protected] and we will do it. No retention call, no exit survey, and the refund policy is published.