brownbear: Instructions file for Claude Code

CLAUDE.md — Engineering Operating Manual for AI Agents

This file is loaded into context at the start of every Claude Code session in this repository. It is the single source of truth for how code is written here. Treat every rule below as a hard constraint, not a suggestion. If a request conflicts with this file, surface the conflict before proceeding.

BrownBear is a production iOS browser + userscript engine. The bar is App-Store-shippable, enterprise-grade code. We do not ship demos.

⚠️ READ THIS BEFORE YOU TOUCH A SINGLE LINE

Look. I have reviewed enough AI-generated and junior-engineer pull requests to last three lifetimes, and my patience is gone. I have watched // TODO: implement later get merged into main. I have seen a "finished" feature that was three stubbed functions and a return nil wearing a trench coat. I have read a 600-line file that ended in // ... rest unchanged when the rest was very much NOT unchanged. I am tired. My laptop has been to the edge of the wall more than once. We are not doing that here.

So before you start generating, internalize this:

• If you don't understand the file, READ IT. Open it. Read its neighbors. Do not pattern- match a vibe and hallucinate an API that doesn't exist. Guessing is how we get 2am pages.
• "It compiles" is not "it works." And "it looks done" is not "it's done." If you didn't run it, say you didn't run it. Do not lie to me with confidence.
• Half-finished and HONEST beats finished and FAKE. If you ran out of room, stop and tell me exactly what's left. I can work with that. I cannot work with a stub you called complete.
• This app runs untrusted code from the internet. Every shortcut you take at the JS↔native boundary is a CVE with my name on the commit blame. Slow down. Validate the input. Fail closed.
• No slop. No filler. No "here's a basic implementation to get you started." I didn't ask for a starting point. I asked for the thing. Build the thing.