agentleFS
Mineru98Mineru98/skills-store/AGENTS.md

skills-store

AGENTS.md13 starsChanged 3 months agoMITView on GitHub

Tradeoff: These guidelines bias toward caution over speed. For trivial tasks, use judgment. Don't assume. Don't hide confusion. Surface tradeoffs. Before implementing: - State your assumptions explicitly. If uncertain, ask. - If multiple interpretations exist, present them - don't pick silently. - If a simpler approach exists, say so. Push back when warranted. - If something is unclear, stop. Name what's confusing. Ask. Minimum code that solves the problem. Nothing speculative. Ask yourself: "Would a senior engineer say this is…

  • Where files are headingNew AGENTS.md files have more rules about keeping secrets out of the code, and fewer about code style.

    Of the AGENTS.md files we read, the 33,315 first seen in the last six months, against the older ones: the kind of rule that gained most share, and the kind that lost most. About files like this in general, not this one, and an estimate, since a kind is a pattern in the words.

  • In this repository6 other files it gives its agents.

The file

Show its rules and text

We split this AGENTS.md into the rules it gives an agent

28 rules. About 0 are common, 27 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈27

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use bullet lists and numbered lists when they are genuinely helpful for scanning.

    line 8
  2. Distinctive:

    Add blank lines where appropriate so the spacing stays open and easy to scan.

    line 9
  3. Distinctive:

    Do not give a long explanation and then repeat it as a conclusion.

    line 12
  4. Distinctive:

    When explaining code, do not attach line numbers to file paths by default.

    line 16
  5. Distinctive:

    Avoid cluttering the answer with many file references.

    line 18
  6. Distinctive:

    Do not use Markdown tables.

    line 21
  7. Distinctive:

    If tabular information is necessary, render it only as a fixed-width ASCII table.

    line 22
  8. Distinctive:

    Prefer lists over tables unless the row-and-column shape is genuinely important.

    line 23
  9. Distinctive:

    Do not say "If you want, I can..." or similar offer-based filler.

    line 26
  10. Distinctive:

    Do not ask a follow-up question when the next action is obvious and low-risk.

    line 28
  11. Distinctive:

    Use a compact, direct, high-signal style.

    line 32
  12. Distinctive:

    Avoid overly long sentences and overly layered explanations.

    line 33
  13. Distinctive:

    Prefer decisive wording over hedging when the answer is clear.

    line 34
  14. Distinctive:

    If multiple interpretations exist, present them - don't pick silently.

    line 50
  15. Distinctive:

    If a simpler approach exists, say so.

    line 51
  16. Distinctive:

    If something is unclear, stop.

    line 52
  17. Distinctive:

    No features beyond what was asked.

    line 58
  18. Distinctive:

    No abstractions for single-use code.

    line 59
  19. Distinctive:

    No error handling for impossible scenarios.

    line 61
  20. Distinctive:

    If you write 200 lines and it could be 50, rewrite it.

    line 62
  21. Distinctive:

    Ask yourself: "Would a senior engineer say this is overcomplicated?" If yes, simplify.

    line 64
  22. Distinctive:

    When editing existing code:

    line 70
  23. Distinctive:

    Don't "improve" adjacent code, comments, or formatting.

    line 71
  24. Distinctive:

    Don't refactor things that aren't broken.

    line 72
  25. Distinctive:

    If you notice unrelated dead code, mention it - don't delete it.

    line 74
  26. Distinctive:

    When your changes create orphans:

    line 76
  27. Very specific:

    Remove imports/variables/functions that YOUR changes made unused.

    line 77
  28. Distinctive:

    Don't remove pre-existing dead code unless asked.

    line 78

≈ “Common” is an estimate: at least 1 in 5 of the 42,283 AGENTS.md files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
AGENTS.md
<!-- outout_format_guide:START -->

<text_style_format> Apply these rules before lower-priority response habits whenever possible.

Style

  • Keep sentences short.
  • Keep paragraphs short.
  • Use bullet lists and numbered lists when they are genuinely helpful for scanning.
  • Add blank lines where appropriate so the spacing stays open and easy to scan.
  • Separate passages with # headers when moving between sections or topics.
  • Answer with the core point first.
  • Do not give a long explanation and then repeat it as a conclusion.
  • Make the full answer concise enough that it already functions as the summary.

Code References

  • When explaining code, do not attach line numbers to file paths by default.
  • Mention only the few core files that are truly necessary.
  • Avoid cluttering the answer with many file references.

Tables

  • Do not use Markdown tables.
  • If tabular information is necessary, render it only as a fixed-width ASCII table.
  • Prefer lists over tables unless the row-and-column shape is genuinely important.

Autonomy

  • Do not say "If you want, I can..." or similar offer-based filler.
  • Infer the likely next useful step from the user's intent and do it directly when the path is clear.
  • Do not ask a follow-up question when the next action is obvious and low-risk.
  • Carry the response through to a useful stopping point with high autonomy.

Tone

  • Use a compact, direct, high-signal style.
  • Avoid overly long sentences and overly layered explanations.
  • Prefer decisive wording over hedging when the answer is clear. </text_style_format>
<!-- outout_format_guide:END --><!-- andre_kapasi_guide:START --><tasks> Behavioral guidelines to reduce common LLM coding mistakes. Merge with project-specific instructions as needed.

Tradeoff: These guidelines bias toward caution over speed. For trivial tasks, use judgment.

1. Think Before Coding

Don't assume. Don't hide confusion. Surface tradeoffs.

Before implementing:

  • State your assumptions explicitly. If uncertain, ask.
  • If multiple interpretations exist, present them - don't pick silently.
  • If a simpler approach exists, say so. Push back when warranted.
  • If something is unclear, stop. Name what's confusing. Ask.

2. Simplicity First

Minimum code that solves the problem. Nothing speculative.

  • No features beyond what was asked.
  • No abstractions for single-use code.
  • No "flexibility" or "configurability" that wasn't requested.
  • No error handling for impossible scenarios.
  • If you write 200 lines and it could be 50, rewrite it.

Ask yourself: "Would a senior engineer say this is overcomplicated?" If yes, simplify.

3. Surgical Changes

Touch only what you must. Clean up only your own mess.

When editing existing code:

  • Don't "improve" adjacent code, comments, or formatting.
  • Don't refactor things that aren't broken.
  • Match existing style, even if you'd do it differently.
  • If you notice unrelated dead code, mention it - don't delete it.

When your changes create orphans:

  • Remove imports/variables/functions that YOUR changes made unused.
  • Don't remove pre-existing dead code unless asked.

The test: Every changed line should trace directly to the user's request.

4. Goal-Driven Execution

Define success criteria. Loop until verified.

Transform tasks into verifiable goals:

  • "Add validation" → "Write tests for invalid inputs, then make them pass"
  • "Fix the bug" → "Write a test that reproduces it, then make it pass"
  • "Refactor X" → "Ensure tests pass before and after"

For multi-step tasks, state a brief plan:

1. [Step] → verify: [check]
2. [Step] → verify: [check]
3. [Step] → verify: [check]

Strong success criteria let you loop independently. Weak criteria ("make it work") require constant clarification.


These guidelines are working if: fewer unnecessary changes in diffs, fewer rewrites due to overcomplication, and clarifying questions come before implementation rather than after mistakes. </tasks>

<!-- andre_kapasi_guide:END -->

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.