How to prepare a repository for coding agents

Structure, rules, and tests that noticeably improve output quality.

I use it for larger tasks that need autonomous work across a project, not just autocomplete.

What works in practice

• A short project map beats a long prompt.
• Run and test commands should work without guesswork.
• Keep local rules close to the code they govern.
• Make verification failures actionable.

Where the boundary is

A repository that is hard for a new developer is usually hard for an agent too.