agentleFS
diriendirien/yet-another-agent-harness/.claude/skills/agent-rules/SKILL.md

agent-rules

Skill19 starsChanged 8 months agoMITView on GitHub

Use when creating or updating AGENTS.md files, .github/copilot-instructions.md, or other AI agent rule files, onboarding AI agents to a project, standardizing agent documentation, or when anyone mentions AGENTS.md, agent rules, project onboarding, or codebase documentation for AI agents.

4 other projects use a version of this, 1 of them edited.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 4 edited versions we read keep these.

  • 0

    Distinctive

    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. Very specific:

    Use --update to preserve human-curated content outside <!-- GENERATED --> markers.

    line 50

“Common” is measured: kept by at least 6 in 10 of the 4 edited versions of this file we could read. “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
SKILL.md

AGENTS.md Generator Skill

Generate and maintain AGENTS.md files following the agents.md convention. AGENTS.md is FOR AGENTS, not humans.

When to Use

  • Creating or updating AGENTS.md for new/existing projects
  • Standardizing agent documentation across repositories
  • Checking if AGENTS.md files are current with recent code changes
  • Onboarding AI agents to an unfamiliar codebase

Scripts

ScriptPurpose
scripts/generate-agents.sh PATHGenerate AGENTS.md files
scripts/validate-structure.sh PATHValidate structure compliance
scripts/check-freshness.sh PATHCheck if files are outdated
scripts/verify-content.sh PATHVerify documented files/commands match codebase
scripts/verify-commands.sh PATHVerify documented commands execute
scripts/detect-project.sh PATHDetect language, version, build tools
scripts/detect-scopes.sh PATHIdentify directories needing scoped files
scripts/extract-commands.sh PATHExtract commands from build configs
scripts/extract-ci-rules.sh PATHExtract CI quality gates and version matrix
scripts/extract-architecture-rules.sh PATHExtract module boundaries
scripts/extract-adrs.sh PATHExtract architectural decision records
scripts/extract-github-rulesets.sh PATHExtract GitHub rulesets and merge rules

See references/scripts-guide.md for full options.

Workflow

  1. Detect: detect-project.sh + detect-scopes.sh to identify stacks and subsystems
  2. Extract: extract-commands.sh, extract-ci-rules.sh, etc. to gather facts
  3. Generate: generate-agents.sh with --style=thin (default) or --verbose
  4. Verify: verify-content.sh + verify-commands.sh -- MANDATORY before done

Use --update to preserve human-curated content outside <!-- GENERATED --> markers.

Core Principles

  • Structured over Prose -- tables parse faster than paragraphs
  • Never Fabricate -- only document what exists; verify every command and path
  • Pointer Principle -- point to files, don't duplicate content
  • Auto Symlinks -- CLAUDE.md/GEMINI.md symlinks by default (see ai-tool-compatibility.md)

References

FileContents
verification-guide.mdVerification steps, design principles
scripts-guide.mdScript options, validation checklist
ai-tool-compatibility.md16-agent compatibility matrix
output-structure.mdRoot/scoped sections
git-hooks-setup.mdHook framework detection and setup
examples/Complete examples
ai-contribution-guidelines.md"3 Cs" framework for AI contributions (Comprehension, Context, Continuity)
directory-coverage.mdFull coverage rationale for scoped AGENTS.md files

Templates

Root: assets/root-thin.md (default), root-verbose.md. Scoped: assets/scoped/ -- backend-go.md, backend-php.md, python-modern.md, typo3.md, symfony.md, skill-repo.md, cli.md, frontend-typescript.md, oro.md.

Supported Projects

Go, PHP (Composer/Laravel/Symfony/TYPO3/Oro), TypeScript (React/Next/Vue/Node), Python (pip/poetry/ruff/mypy), Skill repos, Hybrid (multi-stack with auto-scoping).

See Also

  • agent-harness-skill — broader agent-readiness harness (CI verification, enforcement). Invokes this skill when AGENTS.md is missing.
  • skill-repo-skill — skill-repo structure (plugin.json, split licensing, release workflows).

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.