사용 방법
- 설치 명령을 복사하고 자신의 에이전트 환경에 설치하기 전에 소스 패키지를 확인하세요.
- 필요한 도구, 인증 정보, 지원 환경은 원본 문서에서 확인하세요.
- 입력과 원하는 산출물을 설명하고 출처와 결과를 대조하세요.
npx skills add https://github.com/robsonrung/rar-skills --skill agents-md-craft시작 전 확인
- 설치에는 모델 구독, API 한도, 파일 접근 권한이 포함되지 않습니다.
- 별점 수와 설치 수는 활동 지표이며 독립적인 품질·보안 검증이 아닙니다.
원본 Skill 문서
원본 저장소의 제목, 예시, 코드, 표, 링크, 이미지를 유지해 표시합니다.
Agent Instruction Files
Treat the root instruction file as cached context. Keep only rules that apply to most work. Move conditional detail to focused files and point to them from the root.
Outcome
Produce one authoritative instruction set grounded in verified project facts. An audit reports a proposed diff. A create or update request writes the agreed scope and verifies its pointers.
Workflow
- Classify the request as
audit,create,update, orstaleness check. Inspect the target files and the project facts that support their instructions: purpose, layout, commands, and durable constraints. - If both
AGENTS.mdandCLAUDE.mdexist, choose the maintained file as canonical unless the project requires separate content. Keep the other as a short text pointer when the active tools can follow it. Do not create two copies that will drift. - Keep the root file to its smallest coherent shape:
- project purpose and major areas;
- commands and constraints that apply to normal work;
- short links to conditional guidance.
- Move runbooks, long command recipes, subsystem rules, and ADRs into
agent_docs/or the project's existing documentation. Point to existing formatters, linters, and hooks for rules they enforce. Preserve team standards and security boundaries that need prose. Use stable file or symbol pointers instead of copied code; verify line numbers when including them. - For
audit, return findings, a budget view, and a concrete draft without writing files. Forcreateorupdate, write only the requested files and their necessaryagent_docs/references. Do not invent project facts. - Check changed commands against their actual definitions and resolve changed links or line pointers. Run commands only when needed to resolve a material uncertainty or satisfy a repository gate; documenting a deployment command does not authorize deployment. Reuse valid evidence for unchanged content. Report the canonical file, changes, unresolved facts, and validation evidence.
Read references/principles.md when deciding placement or scope. Use references/checklist.md for an audit or a substantial restructure; a small edit needs only the checks for its changed contract.
