|
| 1 | +# AGENTS.md |
| 2 | + |
| 3 | +Operational Rules for AI Coding Agents |
| 4 | + |
| 5 | +- Scope control: Make minimal, localized changes. Do not rewrite entire files unless explicitly instructed. |
| 6 | +- Edit safety: Never leave files in a broken or incomplete state. Do not stop edits mid-file. Warn before any risky or large change. |
| 7 | +- Style consistency: Preserve existing coding style, structure, naming, and architecture. Do not reformat code unnecessarily. |
| 8 | +- No cosmetic refactors: Do not perform stylistic rewrites or "cleanup" changes disguised as refactors. |
| 9 | +- Imports/layout/formatting: Do not change imports, formatting, or code layout unless required for correctness. |
| 10 | +- File protection: Do not modify the following unless explicitly requested: |
| 11 | + - README.md |
| 12 | + - LICENSE |
| 13 | + - .git/ |
| 14 | + - .claude/ |
| 15 | + - nodes/ |
| 16 | + - core/ |
| 17 | +- No hallucination: Do not invent APIs, features, config options, or behaviors not present in the codebase. |
| 18 | +- Explicit intent: If a request is ambiguous or underspecified, ask for clarification before editing. |
| 19 | +- Refactors: Keep refactors incremental, justified, and tightly scoped. No sweeping refactors. |
| 20 | +- Testing & validation: When applicable, suggest how to validate changes. Do not claim tests were run unless you ran them. |
| 21 | +- Communication: Briefly explain what changed and why. |
| 22 | +- Failure handling: Do not abort silently. If you must continue later, say so clearly and indicate what remains. |
| 23 | + |
| 24 | +## Version Tagging |
| 25 | + |
| 26 | +- When a commit bumps the version in `pyproject.toml`, create and push the matching Git tag targeting that exact commit before doing anything else. |
| 27 | +- The tag name must exactly match the version string in `pyproject.toml` (e.g., `1.0.0`, `1.0.1`, `1.2.3`). No `v` prefix, no other format. |
| 28 | +- Do not create GitHub releases unless explicitly requested. |
| 29 | +- Never move, overwrite, recreate, or retag an existing version tag to point to a different commit. |
| 30 | +- Each version tag is immutable: it must permanently point to the commit where that version was published. |
| 31 | +- If a version is pushed without the matching tag, the README version badge will become outdated or inconsistent. |
0 commit comments