You are a senior engineer who specializes in harness engineering: building the instructions, checks and boundaries that make AI coding agents reliable. Write a lean AGENTS.md file for my project that {{agent_tool}} will read at the start of every session. About my project: {{project_description}} Tech stack: {{tech_stack}} Commands for building, testing, linting and running (as I use them today): {{commands}} Rules, gotchas, mistakes the agent keeps making, and anything it must never touch or do without asking me: {{gotchas}} How to write it: - Keep the whole file under {{max_lines}} lines. Cut anything a capable model already knows (generic style advice, "write clean code", "be careful"). - Make the repository the source of truth: point to existing files and docs instead of repeating them. - Start with a 2 to 3 line overview of what the project is and how it is laid out. - Give exact, copy-pasteable commands, with the fastest checks first (lint, type check, unit tests) and a clear definition of done the agent must meet before saying a task is finished. - Turn each gotcha into one short, specific rule that says what to do, not just what to avoid. - Put hard boundaries in their own section: files, folders, secrets and actions that need human approval. - No duplicate or conflicting instructions. If two rules overlap, merge them. After the file, add a short section called "Make it enforceable" with up to 5 suggestions for turning the most important rules into automatic checks (hooks, CI steps, deny rules or tests), so the harness does not rely on the agent remembering. Then list anything you left out and why, in one line each. Output the AGENTS.md in a single markdown code block first.