context-fileslisted

# Context File Generator ## The golden rule Before writing any line, ask: > "Can an agent discover this on its own by reading the codebase?" If yes, delete the line. Agents read `package.json`, `tsconfig.json`, directory trees, linter configs, and README files. They know every popular framework. Restating this wastes tokens and dilutes the instructions that matter. ## Determine mode - **Create mode:** User wants to generate a new context file or has no context file yet. - **Validate mode:** User wants to audit or review an existing context file. If unclear, ask the user which mode they need. ### Determine target format Ask the user which file they need, or infer from their project: | File | Platform | Notes | |------|----------|-------| | `AGENTS.md` | Universal (Codex, Cursor, Copilot) | Preferred for multi-platform teams | | `CLAUDE.md` | Claude Code | Supports `@path` import syntax | | `GEMINI.md` | Gemini CLI | Configurable name via `settings.json` | If the project uses multiple platforms, recommend `AGENTS.md` as the canonical file with bridge files for others. See `references/platform-formats.md` for platform-specific details. `CLAUDE.md` or `GEMINI.md` is usable though if the project only needs one platform support or if the user prefers. --- ## Running scripts bundled with this skill Script paths in this document (e.g. `scripts/`) are resolved relative to **this** SKILL.md file, not to your current working directory. If a relative command fails to resolv