agentleFS
willdadywilldady/platypus/.agents/skills/humanizer/AGENTS.md

platypus / humanizer

AGENTS.md130 starsChanged 5 days agoMITView on GitHub

Guidance for AI coding agents (Claude Code, Codex, Warp, etc.) working in this repository. A Claude Code / OpenCode skill implemented entirely as Markdown. The runtime artifact is SKILL.md: the agent reads its YAML frontmatter (metadata + allowed tools) followed by the editor prompt. There is no build step and no code to run. SKILL.md and README.md must stay in sync. When you change behavior or content:

3 other projects use a version of this.

Adopted by

Most recently taken up by

The file

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

1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Non-obvious fixes: if you change the prompt to handle a tricky failure mode (a repeated mis-edit, an unexpected tone shift), add a short …

    line 20

≈ “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

Guidance for AI coding agents (Claude Code, Codex, Warp, etc.) working in this repository.

What this repo is

A Claude Code / OpenCode skill implemented entirely as Markdown. The runtime artifact is SKILL.md: the agent reads its YAML frontmatter (metadata + allowed tools) followed by the editor prompt. There is no build step and no code to run.

Key files

  • SKILL.md — the skill itself. YAML frontmatter (name, version, description, allowed-tools) followed by the canonical, numbered pattern list with before/after examples. This is the source of truth.
  • README.md — for humans: installation, usage, a summary table of the patterns, and a version history.

The maintenance contract

SKILL.md and README.md must stay in sync. When you change behavior or content:

  • Patterns: the skill currently defines 33 numbered patterns. If you add, remove, or renumber any, update the README pattern table, its "N Patterns Detected" heading, and every cross-reference in the same change. Keep numbering stable unless you are deliberately renumbering.
  • Version: SKILL.md frontmatter has a version: field and README.md has a "Version History" section. Bump both together.
  • Non-obvious fixes: if you change the prompt to handle a tricky failure mode (a repeated mis-edit, an unexpected tone shift), add a short note to the README version history explaining what was fixed and why.

Editing SKILL.md

  • Preserve valid YAML frontmatter (formatting and indentation).
  • The prompt below the frontmatter is the product. Edit it like a careful instruction document, not code.

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.