← ClaudeAtlas

agents-mdlisted

Create, review, or update concise AGENTS.md and CLAUDE.md instructions for code repositories. Use when a project needs agent setup, scoped instructions, verified commands, or links to authoritative project documentation.
thestratcore/My-skills · ★ 0 · AI & Automation · score 62
Install: claude install-skill thestratcore/My-skills
# Maintain repository agent instructions Write the smallest instruction file that helps an agent work correctly in this repository. Preserve the user's requested scope and any existing project policy. ## Inspect 1. Read existing `AGENTS.md` and `CLAUDE.md` files in the repository and its ancestor directories. Inspect nested files when the task touches their subtrees. Treat nested instructions as narrower guidance; resolve conflicts using authority and scope, not a blanket “closest file wins” rule. 2. Check the README, relevant project docs and policies, package manifest and lockfile, task runners, CI workflows, code layout, tests, and generated-file rules. Use this evidence to identify the actual package manager, commands, and constraints. 3. For Stratcore projects under `/Users/admin/Documents/CodeProjects/`, read [CodeProjects AGENTS.md Methodology](</Users/admin/Documents/Obsidian-Stratcore/CodeProjects AGENTS.md Methodology.md>) and locate the corresponding vault project note when one exists. Before using vault notes as requirements or editing them, read the vault root `AGENTS.md` and respect note status and credential rules. ## Scope and content - Put repository-wide rules in the root file. Add a nested file only for distinct subtree behavior; keep shared rules in the parent. - State the project's purpose in one sentence, then include only instructions that change behavior: authoritative references, non-obvious constraints, generated files, required tools, and relev