Use Claude Code, Codex, VSCode, Pi, and OpenCode (and 6 other harnesses) for free (1.3B+ free tokens) from your terminal, app, IDE, or phone, and now from the browser with native browser sessions (multi-harness + multi-model) like OpenClaw (voice supported + ToS friendly)
Python
Add repository agent guidelines (#1704)
Ali Khokhara010b376d006
diff --git a/AGENTS.md b/AGENTS.mdnew file mode 100644index 00000000..bc0803f9--- /dev/null+++ b/AGENTS.md@@ -0,0 +1,65 @@+# AGENTS.md++Behavioral guidelines to reduce common LLM coding mistakes. Merge with project-specific instructions as needed.++**Tradeoff:** These guidelines bias toward caution over speed. For trivial tasks, use judgment.++## 1. Think Before Coding++**Don't assume. Don't hide confusion. Surface tradeoffs.**++Before implementing:+- State your assumptions explicitly. If uncertain, ask.+- If multiple interpretations exist, present them - don't pick silently.+- If a simpler approach exists, say so. Push back when warranted.+- If something is unclear, stop. Name what's confusing. Ask.++## 2. Simplicity First++**Minimum code that solves the problem. Nothing speculative.**++- No features beyond what was asked.+- No abstractions for single-use code.+- No "flexibility" or "configurability" that wasn't requested.+- No error handling for impossible scenarios.+- If you write 200 lines and it could be 50, rewrite it.++Ask yourself: "Would a senior engineer say this is overcomplicated?" If yes, simplify.++## 3. Surgical Changes++**Touch only what you must. Clean up only your own mess.**++When editing existing code:+- Don't "improve" adjacent code, comments, or formatting.+- Don't refactor things that aren't broken.+- Match existing style, even if you'd do it differently.+- If you notice unrelated dead code, mention it - don't delete it.++When your changes create orphans:+- Remove imports/variables/functions that YOUR changes made unused.+- Don't remove pre-existing dead code unless asked.++The test: Every changed line should trace directly to the user's request.++## 4. Goal-Driven Execution++**Define success criteria. Loop until verified.**++Transform tasks into verifiable goals:+- "Add validation" → "Write tests for invalid inputs, then make them pass"+- "Fix the bug" → "Write a test that reproduces it, then make it pass"+- "Refactor X" → "Ensure tests pass before and after"++For multi-step tasks, state a brief plan:+```+1. [Step] → verify: [check]+2. [Step] → verify: [check]+3. [Step] → verify: [check]+```++Strong success criteria let you loop independently. Weak criteria ("make it work") require constant clarification.++---++**These guidelines are working if:** fewer unnecessary changes in diffs, fewer rewrites due to overcomplication, and clarifying questions come before implementation rather than after mistakes.diff --git a/CONTRIBUTING.md b/CONTRIBUTING.mdindex b71435ff..1037a71c 100644--- a/CONTRIBUTING.md+++ b/CONTRIBUTING.md@@ -8,7 +8,6 @@ Thanks for helping improve Free Claude Code. Keep changes focused, test the beha- Do not open Docker integration pull requests.- For bugs, include every model mapping, the active model when the failure occurred, the complete error, and reproducible steps.- Add focused tests for behavior changes and relevant edge cases.-- Read [ARCHITECTURE.md](ARCHITECTURE.md) before changing package boundaries, providers, protocol conversion, launchers, or messaging.## Development Setup