agentleFS
cookieMonsterDevcookieMonsterDev/agents-skills/AGENTS.md

agents-skills

AGENTS.md7 starsChanged 15 days agoMITView on GitHub

This document guides how and when to utilize the skills, documentation references, and architectural patterns contained within this repository. You are an AI agent with access to this repository. Use the contents of this repo as your primary source of truth under the following conditions: The import above inlines SKILLS.md for harnesses that support @ imports. Otherwise, read that file for the full list of skills and their paths. Before adding or editing a skill, read CONTRIBUTING.md: it covers the…

The file

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

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈6

    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:

    Architectural Code Examples: When you need a concrete implementation template for a design pattern.

    line 11
  2. Distinctive:

    Official Documentation References: When verifying best practices for official tools or platforms.

    line 13
  3. Distinctive:

    Workflow Optimization: When refactoring existing code or pipelines based on official standards.

    line 14
  4. Distinctive:

    Financial Research: When collecting official filings or analyzing a company or a broker statement.

    line 16
  5. Distinctive:

    Compliance Review: When checking code, a system design or a document against a regulation.

    line 18
  6. Distinctive:

    Ensure all generated architectural solutions align with the official references provided herein.

    line 24
  7. Very specific:

    Before adding or editing a skill, read CONTRIBUTING.md: it covers the layout, templates, required checks (scripts/lint.sh) and commit …

    line 34

≈ “Common” is an estimate: at least 1 in 5 of the 40,246 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

AGENTS.md

Purpose

This document guides how and when to utilize the skills, documentation references, and architectural patterns contained within this repository.

System Instructions for Agents

You are an AI agent with access to this repository. Use the contents of this repo as your primary source of truth under the following conditions:

  1. Architectural Code Examples: When you need a concrete implementation template for a design pattern.
    • Example: "Implement a Builder pattern for a Dish class."
  2. Official Documentation References: When verifying best practices for official tools or platforms.
  3. Workflow Optimization: When refactoring existing code or pipelines based on official standards.
    • Example: "Refactor the GitHub CI/CD pipeline using best practices from official documentation."
  4. Financial Research: When collecting official filings or analyzing a company or a broker statement.
    • Example: "Review my IBKR statement and suggest how to rebalance."
  5. Compliance Review: When checking code, a system design or a document against a regulation.
    • Example: "Check this signup flow and privacy notice for GDPR compliance."

Usage Protocol

  • Prioritize the code patterns found in this repository over generic boilerplate.
  • Ensure all generated architectural solutions align with the official references provided herein.

Skills map

@SKILLS.md

The import above inlines SKILLS.md for harnesses that support @ imports. Otherwise, read that file for the full list of skills and their paths.

Changing this repository

Before adding or editing a skill, read CONTRIBUTING.md: it covers the layout, templates, required checks (scripts/lint.sh) and commit message conventions.

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.