Standardize the current GitHub repository's durable project context for coding agents by default. Use when asked to create or update AGENTS.md routing, scaffold or normalize docs/ project documentation, separate consumer README content from contributor/developer docs, or apply a reusable repo documentation convention with root README.md, CONTRIBUTING.md, RELEASE.md, and docs/README.md.
75
94%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Passed
No known issues
Guidance for AI coding agents working in this repository.
Before making changes, read:
CONTRIBUTING.md for contribution, PR, testing, commit, and agent-specific expectations.RELEASE.md for release workflow details.README.md for user-facing behavior, install/use examples, and package or app overview.docs/README.md for the project documentation index.docs/development.md for local setup and development workflows.docs/testing.md for test strategy, commands, and verification expectations.docs/architecture.md for project structure, boundaries, and important invariants.docs/conventions.md for project-specific coding, documentation, and maintenance conventions.Treat those files as the source of truth. Do not duplicate or reinterpret their rules here.
docs/; keep root files focused on their standard audiences.docs/README.md and update this file only when they become important entry points for future agents.CONTRIBUTING.md.CONTRIBUTING.md.RELEASE.md for release workflow and changeset creation steps.RELEASE.md and any changeset guidance in CONTRIBUTING.md as authoritative.