monorepos, different developers need different AI Coding Agent rules Different teams with different needs Working on different services Not always opened from repository root Often opened from specific service directories Context provided to AI tends to become large 6
In a monorepo, different developers work on different directories with different teams and tech stacks Each team has slightly different coding conventions and tech stacks Rules helpful for one team might be disruptive for others... Unused or unnecessary rules waste context window space and create noise 8
Add .clinerules/ and .roo/rules/ to .gitignore to avoid git tracking Place .gitkeep in each to preserve the directories Manage rules in a separate directory under git control 10
Copying desired rules from Rules Bank to .clinerules/ or .roo/rules is tedious Created github.com/upamune/airule - a fuzzy finder with preview to pick rules easily Works with both Cline and Roo Code using airule --from /path/to/source --to /path/to/destination Cline: airule --from /path/to/rules-bank --to .clinerules Roo Code: airule --from /path/to/rules-bank --to .roo/rules Supports environment variables for those who want to just run airule without specifying paths each time 12
Inc. In monorepos, it's common to open workspace from the service directory you're developing When this happens, Cline and Roo Code can't recognize the rules Rules aren't loaded because there's no .clinerules/ or .roo/ directory in the opened directory 15
Inc. Solution: Created a tool to distribute rules to required directories github.com/upamune/airulesync Provide a config file like below and it syncs the rules 16
the tools I introduced!" but rather... AI Coding Agent barriers can be solved with AI Coding Agents You can quickly develop tools tailored to your organization's specific challenges, and if they're general enough, make them OSS Off Topic: When adding more tools increases installation time... There's an elegant tool called aqua that handles this, but let's discuss that at the after-party if we have time... Lightning-fast local environment setup with aqua in the age of everyone coding - LayerX Engineer Blog 17
LayerX Inc. Context window fills up quickly when referencing many files Gemini 2.5 Pro with its large context window solves the size issue, but performance degrades rapidly with large contexts Roo Code recently added Intelligent Context Condensing which summarizes early context when window is full, but I haven't really felt the improvement Too many files to search through, hard to find the right ones Roo Code recently added Codebase Indexing, so I set up an environment to test it... Uses OpenAI or Ollama (Local) for embedding models, creates embeddings, and uses Qdrant vector database Codebase Indexing - Roo Code Cline doesn't do Codebase Indexing ref. Why Cline Doesn't Index Your Codebase (And Why That's a Good Thing) 23
Records) / Design Doc / Spec Developed internal tool to automatically fetch from Notion and convert to Markdown Technical decision records and specifications Provides "why we chose this design" in a format AI can understand DB Schema Information Using k1low/tbls Tool that auto-generates documentation from DB schema Generates ER diagrams, table definitions, and relation info in Markdown format Generate and commit to repository More accurate than CREATE TABLE SQL definitions 28
LayerX Inc. Store internal best practices in Markdown format under docs/libraries Writing from scratch is tedious, so use MCP servers to create drafts while documenting how to use libraries and how we want them to be used Context7: Access latest documentation Deep Wiki: Provides wiki by analyzing GitHub repositories 29
for AI to generate files and output modification proposals Place for files like plan.md containing implementation plans Add this to .gitignore The name of this directory might be controversial depending on people/organizations lol 32
has been said many times, but for complex implementations, it's best to plan first Cline has Plan mode, Roo Code has Architect mode, Claude Code got Plan mode today(?) Have AI output to z/plan.md or similar and review it If the content is good, start implementation based on that However, things don't always go smoothly... Task breakdown is necessary Roo Code's Orchestrator mode and Claude Code can take you far when you feed them plan.md 33
have standard procedures. It's recommended to document these as "implementation playbooks" For example, "adding a product usage flag for users" - a defined workflow Even when AI creates implementation plans, if many files are involved, things get missed in the plan, and humans don't remember what needs to be touched, leading to "it doesn't work" after implementation Creating this documentation becomes useful for humans too 34
down large tasks into subtasks and executes them while switching to appropriate modes Fun with many experimental features Codebase Indexing Intelligent Context Condensing Concurrent File Reads Open development - if you have issues, contribute and implement it yourself feat: Add support for .roorules configuration files by upamune #2309 feat: enhance rule file loading with .roo/rules directory support by upamune #2354 40
it after Claude Sonnet 4 / Claude Opus 4 launched Using about $300-$400 per day Works well even without setting up rules As mentioned earlier, works quite well even in monorepos About 90% of things I thought "this vague instruction probably won't work..." actually worked Haven't had any major failures yet, so I haven't experienced disappointment - would love to hear about disappointing experiences 45
things work pretty well without much effort on rules/prompts Actually, our software engineers' excitement about Claude Code is greater than for any previous AI Coding Agent Code reviews have increased dramatically When I use AI Coding Agent, it's essentially code review, and others are also accelerating development with AI Coding Agents, speeding up PR creation Searching for good methods... Copilot Review, AI Coding Agent reviews, CodeRabbit, Greptile, etc... 47
solved with AI Coding Agents themselves Well-prepared context is an asset that transcends tools Have AI help prepare rules and workflows too Roo Code's appeal is customizable modes (especially the powerful Orchestrator mode) Claude Code's arrival produces decent output without excessive rule preparation If you haven't tried AI Coding Agents, start with the Pro plan ($20/month) and experience it! When starting seriously, I strongly recommend reading the official docs thoroughly Claude Code Overview 48
upamune
tammyeverts
sarafernandez
tammielis
baasie
samlambert
gurzu
tapps
aleyda
davidcarrasco
soysaucechin
rkendrick25
