Few days ago, I posted fileGOD - browser-based PDF tools where files never leave your device. Got some good feedback, but I buried the lede.The part I should have led with: fileGOD works completely offline. Open it once, install it as a PWA, turn off your Wi-Fi, and compress/merge/split PDFs or convert images. Everything still works. No spinner, no "connection lost" error. Just works.I haven't...
Just got tired of uploading passports, tax forms, and business contracts to iLovePDF and others after I've read they all store data. That made me built fileGOD. PDF compress, merge, split, and image conversion that runs entirely in the browser. There is no server endpoint that accepts file uploads. The processing pipeline uses WASM and runs on your device.We've ended up with full platform with...
1. Don't watch it work. Give CC a clear task with success criteria, then go do something else, directory submissions, Quora answers, whatever. Come back to finished work or a clear error.
2. Batch related work into one session. Instead of "fix this button" then "add this feature" - give it a full plan with 6-8 items. It enters plan mode, works through them sequentially, and you review once at the end.
3. CLAUDE.md with workflow rules. CC reads it at session start. Mine includes "never mark a task complete without proving it works" and "after any correction, update lessons.md." This eliminated the cycle of fix break ask fix.
4. Accept the async mental model. Agentic coding isn't pair programming. It's more like delegating to a junior who's incredibly fast but needs clear specs. Write the spec well, step away, review the output.
The broken rhythm only hurts when you try to synchronously watch and steer. The moment I started treating CC sessions like async tasks, everything clicked.
Key rules that made the biggest difference:
1. Plan Mode Default — enter plan mode for any task with 3+ steps. If something goes sideways, STOP and re-plan instead of pushing forward.
2. Self-Improvement Loop — after ANY correction, CC updates tasks/lessons.md with the pattern. It stops making the same mistake twice.
3. Verification Before Done — never mark complete without proving it works. "Would a staff engineer approve this?"
6. Autonomous Bug Fixing — when given a bug report, just fix it. Don't ask for hand-holding. Zero context switching from the user.
Before this, CC would ask permission for everything and repeat mistakes across sessions. Now it plans first, fixes autonomously, and learns from corrections.
The CLAUDE.md file persists across sessions — it's basically giving CC a working memory and engineering standards in one file.
- SEO audits (checking structured data, hreflang across 25 language versions) - Batch blog translations (40 articles × 25 languages) - Performance debugging (found that our entire SSR body was empty, LazyAuthProvider with ssr:false was wrapping all content) - Admin dashboard analytics queries
The biggest unlock was giving it a good CLAUDE.md with workflow rules. It stops asking permission and starts fixing things autonomously.
Building a browser-based file tools product and CC handles probably 80% of the iteration cycle at this point.