Your project has .gitignore — where's your .rules/?
Every developer in 2026 is using AI to write code. Almost none of them have a system for governing the output. I built one. The Problem Nobody Talks About AI writes code. But it also breaks code. I...

Source: DEV Community
Every developer in 2026 is using AI to write code. Almost none of them have a system for governing the output. I built one. The Problem Nobody Talks About AI writes code. But it also breaks code. It removes imports you need. It truncates files to save tokens. It changes function signatures that three other modules depend on. It ignores your naming conventions, your architecture decisions, your project's entire history — because it doesn't know any of it. Every new AI session starts from zero. No memory of the time it broke your auth middleware. No memory that you use camelCase for services and PascalCase for components. No memory that you spent four hours last Tuesday fixing the code it "improved." We solved this problem for everything else years ago. Linting has .eslintrc. Formatting has .prettierrc. Editor behavior has .editorconfig. Git has .gitignore. But AI behavior? Nothing. No standard. No convention. No file that says "here's how AI should behave in this codebase." The result i