agentleFS
mikeparcewskimikeparcewski/wicked-garden/AGENTS.md

wicked-garden

AGENTS.md9 starsChanged 7 months agoMITView on GitHub

The canonical agent instructions for this repository live in .claude/CLAUDE.md. Read that file — it is the single source of truth for how to work in wicked-garden: conventions, v11/v12 architecture, evidence-re-derivation, delegation, code search, memory, storage, and security. Why (identity): see ETHOS.md for what wicked-garden believes / refuses / optimizes for. CLAUDE.md is how to act; ETHOS.md is why. This file is intentionally a thin pointer so there is exactly one source of truth. Other AI coding tools (Codex, Cursor,…

The file

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

1 rule. About 0 are common, 0 are distinctive, and 1 is 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.

  • 1

    Very specific

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

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

    Read that file — it is the single source of truth for how to work in wicked-garden: conventions, v11/v12 architecture, …

    line 4

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

Agent Instructions

The canonical agent instructions for this repository live in .claude/CLAUDE.md. Read that file — it is the single source of truth for how to work in wicked-garden: conventions, v11/v12 architecture, evidence-re-derivation, delegation, code search, memory, storage, and security.

Why (identity): see ETHOS.md for what wicked-garden believes / refuses / optimizes for. CLAUDE.md is how to act; ETHOS.md is why.

This file is intentionally a thin pointer so there is exactly one source of truth. Other AI coding tools (Codex, Cursor, Aider, OpenCode, Zed/ACP, …) that read AGENTS.md: follow the link above to .claude/CLAUDE.md.

Cross-CLI skills (portability rule) — mirrored from .claude/CLAUDE.md

A skill's text must work wherever it is installed — Claude Code (plugin), Codex, OpenCode, Pi and Antigravity (skills-only, flat by name) and wicked-crew's snapshot. Therefore, under skills/: (1) refer to your own files by a path relative to the skill's base directory (refs/plan.md), never ${CLAUDE_PLUGIN_ROOT}, ${CLAUDE_SKILL_DIR} or ../; (2) refer to another skill by its name (wicked-garden-qe, "its refs/review.md"), never by a filesystem path — the installer lays skills out flat by name; every wicked-garden-<x> token must resolve to a declared skill, and an identifier that merely looks like one (an evaluator id, a sibling plugin) is marked right after the token: `wicked-garden-x` <!-- not-a-skill --> (token-scoped — a marker elsewhere on the line exempts nothing); (3) run shared runtime code only through the launcher: wicked-garden run scripts/<path> [args] (or wicked-garden path <dir>, wicked-garden python -c …), include the standard ## Runtime block once (exact text in tests/portability_rules.garden.json; the shared rules crew also enforces are the vendored canonical tests/portability_rules.json), and give a manual alternative for hosts without it; (4) write harness features with a fallback: "invoke skill X (Skill tool) — otherwise open its SKILL.md and follow it inline", "ask the user (AskUserQuestion where available, else plain text and wait)"; (5) context: fork and allowed-tools are Claude Code loading hints, fine to keep — say in the body what to do when the harness cannot fork. Hooks (hooks/) are Claude-plugin mechanics and keep ${CLAUDE_PLUGIN_ROOT}. tests/test_skill_portability.py fails the build on any violation; run python3 scripts/wg/portability_codemod.py --dry-run to see the fix. The launcher lives once in scripts/wicked-garden.mjs (twins scripts/wicked-garden, scripts/wicked-garden.cmd; npm bin wicked-garden run|python|path|root|doctor); root order WICKED_GARDEN_ROOT → CLAUDE_PLUGIN_ROOT → its own package; it never writes under the root.

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.