AI coding needs written rules to avoid repeated mistakes
A post on r/vibecoding argues that AI-assisted coding breaks down when project rules are not documented. The practical point is simple: clear rules can help an AI agent waste fewer tries, tokens, and fixes.
The post title says, “Vibe coding is broken until we document the rules.” In plain terms, it says that asking AI to write code by feel is fragile unless the project has clear instructions. This is not a major product launch or a benchmark claim; it is a community call to define better working rules.
For someone using AI agents, the lesson is useful. A short rules file can tell the AI what not to touch, how to test changes, and what standards matter. That can reduce repeated explanations, bad edits, and token cost caused by long back-and-forth correction.
Key points
- The post argues that AI coding works better when project rules are written down.
- Clear rules can reduce repeated AI mistakes and save tokens.
- This is a practical workflow point, not a new tool release or hard performance result.
- Useful rules include testing steps, protected files, security limits, and coding standards.
Quick term guide
- vibecoding
- A way of making software where a person just describes the overall idea and feel in plain English, and the AI does all the actual programming.
- AI agent
- An AI program that can inspect information and suggest what to do next.
- vibe coding
- Building software by describing what you want to an AI tool and refining the result.
- benchmark
- A test used to compare speed, quality, or cost.
- AI agents
- AI agents are AI tools that can carry out steps toward a goal, not just answer once.
- token cost
- The money or usage spent when sending text to an AI model and getting text back.
- workflow
- A repeatable set of steps for getting a task done.
- testing
- The process of checking that software does what it's supposed to do, usually by running it and looking for errors.