agent-instructions

Solid

Writing or restructuring AGENTS.md or CLAUDE.md, adding a rule ('remember this'), or after an agent ignored a rule it had: make each rule get met when it applies.

AI & Automation 633 stars 85 forks Updated today MIT

Install

View on GitHub

Quality Score: 91/100

Stars 20%
93
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
80
License 10%
100
Description 5%
100

Skill Content

# Agent instructions — rules met at the moment they apply **Meet each rule at the moment it applies.** A rule written down is not yet a rule an agent follows. This skill writes and maintains an app repository's instruction file as the product grows. **Use the entry file to route every session's context.** The entry file is `AGENTS.md`, `CLAUDE.md`, or both. It is where every session enters and what routes the rest. The method is stack-independent; examples come from repositories named by kind. 1. **The entry file routes; the depth lives where the moment sends you.** A rule the agent is not looking at when it acts does not exist for that act. 2. **Make rules that depend on memory at decisive moments into code paths.** Use a test, script or required argument, because prose loses that contest. 3. **Maintain the file at every release and fix every mistake with its receipt.** Maintain it rather than accumulating rules. ## The shape: a chain, not a manual **Root routes to entry points; entry points route to operative files; operative files link to evidence.** Each layer points down; none restates the layer below. ``` entry file (loaded every session) — routes; holds only what every session needs └─ router rows: "when you are…" — the rule that is easy to miss, and what to open └─ operative files (docs/, skills) — the procedure, the depth, the gotchas └─ evidence — receipts, tables, postmortems, case studies ``` - **Route, don't summarize.** ...

Details

Author
phuryn
Repository
phuryn/product-engineering
Created
2 weeks ago
Last Updated
today
Language
Python
License
MIT

Similar Skills

Semantically similar based on skill content — not just same category

AI & Automation Listed

agent-writing

Write instructions that agents actually follow: skills (name, description, trigger phrases, body), CLAUDE.md / AGENTS.md rule files, and briefs for subagents or other agents (objective, DONE criteria, verification, report shape). Covers what to cut, length budgets, examples over adjectives, and a pre-ship checklist. Use for a subagent or agent brief, a system prompt, trimming a rules file that has grown too long, or when an agent keeps ignoring an instruction. For the full style reference on writing skill and doc files, use `writing-for-agents`.

5 Updated 2 days ago
ychampion
AI & Automation Listed

writing-agents-md

Author lean AGENTS.md/CLAUDE.md instruction files — resident system-prompt context where every line pays rent. Use when writing an agent instruction file from scratch, auditing or trimming a bloated one, or gating whether a new rule earns residence and at which scope. Don't use for on-demand skills (use writing-skills) or human-facing docs and READMEs.

3 Updated 1 weeks ago
dougcunha
AI & Automation Listed

rc-agents-md

Author lean AGENTS.md/CLAUDE.md instruction files — resident system-prompt context where every line pays rent. Use when writing an agent instruction file from scratch, trimming a bloated one, or gating whether a new rule earns residence and at which scope. Do not use for on-demand skills (rc-skill-best-practices), for measuring what the whole config surface costs in tokens (rc-context-budget), or for human-facing docs and READMEs (rc-readme).

21 Updated 3 months ago
rodolfochicone