instruction-guidelisted

# Project Instruction Guidelines Author, refresh, simplify, consolidate, and port AGENTS.md project-instruction files while preserving technology names, paths, and project context. ## Core Principles - **Open standard**: AGENTS.md is the cross-harness format read by many agent harnesses; keep content harness-neutral - **README for agents**: operational detail (commands, conventions, gotchas) belongs in AGENTS.md; human-onboarding prose belongs in README.md - **Teammate heuristic**: "anything you'd tell a new teammate" belongs here; anything you'd tell a casual visitor belongs in README - **Nested precedence**: for monorepos, the AGENTS.md closest to the edited file wins; place subproject-specific guidance in subdirectories - **Commands are executable**: agents auto-run programmatic checks listed in AGENTS.md; treat command examples as instructions, not just docs - **Advisory scope**: AGENTS.md communicates project guidance; it does not itself execute automation - **Preserve Project Context**: never modify technology names, paths, or commands - **Match Style and Voice**: maintain the target file's formatting and terminology - **Structure Integrity**: keep section order and hierarchy intact; preview changes (dry-run) before applying - **Signal Over Volume**: keep only non-obvious content; anything inferable from `package.json` + source belongs in the code, not the doc - **Deletion-first editing**: a simplify or consolidate pass cuts at least as much as it adds, and reuses ex