project-context-generation

Analyze the repository to identify build, test, and lint commands, module boundaries, and conventions, then write them as concise actionable guidance. Capture only instructions future sessions repeatedly need rather than restating the whole codebase.

Include build, test, lint, and verification commands, command ordering when it matters, non-obvious project structure, stack conventions, setup quirks, and references to existing rules files. Keep it concise and specific to the project.

Improve the existing AGENTS.md in place when one is present. Preserve useful content, remove stale or generic advice, and add newly discovered commands or conventions rather than overwriting the file.

Common mistakes include restating the entire codebase, adding generic advice not specific to the project, and writing prose meant for humans instead of actionable instructions. Keep the file useful for future agent execution, not as a general README.

Output from tools like `hero scan` provides package structure, key symbols, dependency graphs, and hot files. Including this orients future sessions quickly without requiring them to re-scan the repository.