agents-md-authorlisted

# agents-md-author Generate cross-vendor project instruction files: `AGENTS.md` for Codex (and most other tools), `CLAUDE.md` for Claude Code, or both kept in sync. Load `references/agents-md-spec.md` if you need the cross-vendor convention details. ## When to activate - User asks to "write AGENTS.md", "create CLAUDE.md", or "set up project instructions for AI" - User wants the same project doc to work in Codex, Claude Code, Cursor, or any tool that follows the AGENTS.md convention - User mentions onboarding a new AI tool to an existing repo and wants conventions captured ## Procedure ### 1. Detect project context (always do this first) Read the project root and determine: - **Project name** — from `package.json` `name`, `pyproject.toml` `[project].name`, `go.mod` `module`, `Cargo.toml` `[package].name`, or fallback to repo dir name - **Language & runtime** — `package.json` (Node + lockfile flavor), `requirements.txt` / `pyproject.toml` (Python), `go.mod` (Go), `Cargo.toml` (Rust), `pom.xml` / `build.gradle` (JVM), `*.csproj` (.NET) - **Common scripts** — Node `scripts.{dev,build,test,lint,typecheck}`; Python `tox.ini` / `Makefile`; Go/Rust task tools - **Test framework** — vitest, jest, pytest, go test, cargo test, etc. - **Repo conventions** — existing `.editorconfig`, `.prettierrc`, `eslint.config.*`, `pre-commit-config.yaml` If the user provided context (e.g., "this is a Next.js + Prisma app"), use it; otherwise infer from files. Don't ask questions you can answer