← ClaudeAtlas

vibe.agents-mdlisted

Use when authoring or optimizing AGENTS.md or CLAUDE.md — create the context file or remove discoverable detail while preserving project-specific gotchas.
su-record/vibe · ★ 0 · AI & Automation · score 78
Install: claude install-skill su-record/vibe
# agents-md — Context File Author & Optimizer ## Done Criteria - [ ] 요청된 AGENTS.md 또는 CLAUDE.md가 존재한다. - [ ] 저장소에서 탐색 가능한 일반 정보가 중복 서술되지 않는다. - [ ] 프로젝트 고유 제약과 검증 명령이 남아 있다. - [ ] 두 파일을 함께 관리하면 공통 규칙의 의미가 일치한다. Author and optimize AGENTS.md / CLAUDE.md files. They are the **same doctrine under different filenames** — everything below applies to both. Reference: https://addyosmani.com/blog/agents-md/ ## Core Principles **One-line test**: "Can the agent discover this by reading the code?" → Yes = delete. **Every line has a cost** (Curse of Instructions): LLM compliance drops exponentially with instruction count — roughly 90% at 1 instruction, ~59% at 5, ~44% at 10, ~15% at 15+. A short, precise file beats a long, comprehensive one. **Lost in the Middle**: LLMs attend to the beginning and end of a document and under-weight the middle. Most important rules → top. Frequently violated rules → bottom. Background context → middle (OK if ignored). ## Step 1: Find Target Files Search project root for these files: Use the harness's file-pattern search capability for `AGENTS.md`, `CLAUDE.md`, `.cursorrules`, `.github/copilot-instructions.md`, and `.windsurfrules`. If a target exists → optimize it (Steps 2–3). If none exists and the user wants one → author it (Step 1b), then run the same optimization pass on the draft. ## Step 1b: Authoring From Scratch Explore before writing: `package.json` (stack, scripts), `*.config.*`, `tsconfig.json`, `.env.example`, `Makefile`, `docker-