使い方
- インストールコマンドをコピーし、自分の環境へ導入する前にソースを確認します。
- 必要なツール、認証情報、対応環境を原文で確認します。
- 入力と成果物を指定し、出力を資料と照合します。
npx skills add https://github.com/robsonrung/rar-skills --skill agents-md-craft開始前の確認
- 導入にはモデル契約、API枠、ファイルへのアクセス許可は含まれません。
- スター数や導入数は活動の指標であり、独立した品質・安全性試験ではありません。
リポジトリの原文
見出し、例、コード、表、リンク、参照画像を含む原文を表示しています。
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.
