Topic
13 articles found
Have you ever set up a CLAUDE.md file, dropped in 200 lines of rules, and then watched the AI completely ignore half of them anyway? You are not alone. The irony of writing instructions for AI coding assistants is that the same productivity trap applies to you: more rules ≠ better results. Here are
Originally published on TechSaaS Cloud Originally published on TechSaaS Cloud The fastest way to waste a coding agent is to ask it to infer your repository rules from scattered files. It will usually find the package manager. It may find the test command. It will not reliably infer which migration t
CLAUDE.md for Android and Jetpack Compose: 13 Rules That Make AI Write Modern, Production-Ready Android Code Android development has two eras of AI output quality. The first era: AI that reaches for XML layouts, AsyncTask, SharedPreferences, and findViewById. Code that compiles on Android 14 but was
I've been using Claude Code daily for months. And I kept hitting the same wall: The agent would just start doing things. No plan. No approval. Just... acting. It deleted files I didn't want deleted. It refactored things I didn't ask it to refactor. It made "helpful" assumptions that broke my archite
Quick follow-up to my earlier post about scanning 492 public CLAUDE.md files. Takeaway from that scan: median compliance with the 12-rule baseline was 3/12. The top-missed rules were rules 9, 10, 12, and 1 — the behavior-file equivalent of skipping unit tests. The fix is easy: run a linter. The hard
I recently started a side project, and I want to do something I've never done before: build it in public. Not with the daily "Day N" theatrics, but milestone by milestone, with honest write-ups of how it actually went. This is post number one. What's worth writing about isn't the app — it's how I st
Most AI-assisted coding projects fail long before the model writes bad code. The failure usually starts with context. Developers hand an autonomous coding agent a massive repository, a vague objective, and a 2,000-line CLAUDE.md filled with contradictory instructions, outdated architecture notes, an
You ask Claude to "add caching to the user profile endpoint," and 30 seconds later you ship something that looks fine in review: SET user_42 — flat key, no namespace, collides the moment a second service shares the cluster. No TTL — the entry lives forever until maxmemory evicts your hottest keys. K
I use Claude Code a lot. One thing kept annoying me: not the mistakes, not the occasional wrong assumption, not even the weird confidence. The annoying part was having to re-explain the same project context in new sessions. Things like: this module looks legacy but still supports a critical flow thi
Course does not shows the instructions in claude.md file which should be crucial in SDD 1 post - 1 participant Read full topic
One Big File Doesn't Scale Claude Code reads a CLAUDE.md file at the root of your project. It's the primary way to give the agent project-specific instructions. And for small projects, it works great. For this project, it didn't. The root CLAUDE.md grew to cover architecture, testing conventions, AP
Transform your CLAUDE.md from a vague wishlist into a precise, hierarchical configuration file that gives Claude Code the context it needs to execute complex tasks autonomously. Claude Code is not a junior developer you manage. It's a force multiplier for senior engineers who know how to direct it.
Originally published at heyuan110.com This is Part 2 of the Harness Engineering series. Most CLAUDE.md files are bad — not because people don't try, but because they optimize for the wrong thing. ETH Zurich researchers tested 138 agentfiles across multiple AI coding agents. The results: Human-writte
