agentleFS
Sign inStart free
finograficfinografic/ai-agent-pipeline/AGENTS.md

ai-agent-pipeline

AGENTS.md0 starsChanged 4 months agoMITView on GitHub

Promote durable findings from memory → handoff, priorities and follow-ups → roadmap. Reference: docs/process/PROJECT_MEMORY_MODEL.md Rules are canonical in .github/instructions/ — see README.md there for folder structure. Shared across Claude Code, Cursor, and GitHub Copilot. Documentation - Padded pipes: one space on each side of every |, including the separator row. - Do NOT manually align column widths or pad cells to equal width. oxfmt (run automatically by lint-staged on commit and by pnpm format:fix) fixes table alignment automatically. Spending tokens…

  • 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 31,542 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 repository5 other files it gives its agents.

The file

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

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 6

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Check ROADMAP.md before proposing new initiatives.

    line 17
  2. Very specific:

    Use ROADMAP.md#next for small follow-ups and manual validation.

    line 18
  3. Very specific:

    Keep detailed plans in docs/todo/TODO_*.md.

    line 19
  4. Very specific:

    Do not reference @workspace/* — all imports and deps must use published package names.

    line 27
  5. Very specific:

    Do not include Co-Authored-By lines in commit messages.

    line 77
  6. Very specific:

    Always-on rules: .cursor/rules/ (alwaysApply — entry point is AGENTS.md, same as CLAUDE.md)

    line 84

≈ “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 — AI Assistant Guide

Project Memory Model

  • docs/todo/ROADMAP.md = milestone plan, near-term tasks, and completed history.
  • .agents/handoff.md = stable current project state.
  • .agents/memory.md = chronological session log.

Promote durable findings from memory → handoff, priorities and follow-ups → roadmap.

Reference: docs/process/PROJECT_MEMORY_MODEL.md

Roadmap and Planning Docs

  • Check ROADMAP.md before proposing new initiatives.
  • Use ROADMAP.md#next for small follow-ups and manual validation.
  • Keep detailed plans in docs/todo/TODO_*.md; graduate completed plans to DONE_*.md.
  • Follow .github/instructions/documentation/todo-done-docs.instructions.md.

Rules — Project-Specific

  • Project-specific rules live in .github/instructions/project/**/*.instructions.md.
  • Do not reference @workspace/* — all imports and deps must use published package names.

Rules — Global

Rules are canonical in .github/instructions/ — see README.md there for folder structure. Shared across Claude Code, Cursor, and GitHub Copilot.

General

  • General baseline: .github/instructions/general.instructions.md

Code

  • TypeScript patterns: .github/instructions/code/typescript-patterns.instructions.md
  • Modern TS patterns: .github/instructions/code/modern-typescript-patterns.instructions.md
  • Oxlint & style: .github/instructions/code/linting-code-style.instructions.md
  • Provider/context patterns: .github/instructions/code/provider-context-patterns.instructions.md
  • Picocolors CLI styling: .github/instructions/code/picocolors-cli-styling.instructions.md

Naming

  • File naming: .github/instructions/naming/file-naming.instructions.md
  • Variable naming: .github/instructions/naming/variable-naming.instructions.md

Documentation

  • Documentation: .github/instructions/documentation/documentation.instructions.md
  • README standards: .github/instructions/documentation/readme-standards.instructions.md
  • Agent-facing markdown: .github/instructions/documentation/agent-facing-markdown.instructions.md
  • Feature design specs: .github/instructions/documentation/feature-design-specs.instructions.md
  • TODO/DONE docs: .github/instructions/documentation/todo-done-docs.instructions.md

Git

  • Git policy: .github/instructions/git/git-policy.instructions.md

Rules — Markdown Tables

  • Padded pipes: one space on each side of every |, including the separator row.
  • Do NOT manually align column widths or pad cells to equal width. oxfmt (run automatically by lint-staged on commit and by pnpm format:fix) fixes table alignment automatically. Spending tokens counting characters and iterating on spacing is wasted effort — write the content, let the formatter handle alignment.

Git Policy

  • Do not include Co-Authored-By lines in commit messages.
  • .github/instructions/git/git-policy.instructions.md (see Commits and Releases sections)

Cursor

  • Always-on rules: .cursor/rules/ (alwaysApply — entry point is AGENTS.md, same as CLAUDE.md)

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.

Check your setup, free