agentleFS
Sign inStart free
Greg-KleinGreg-Klein/implementation-harness/CLAUDE.md

implementation-harness

CLAUDE.md1 starsChanged 34 days agoMITView on GitHub

The shared guidance (what the repo is, commands, architecture, conventions, code habits) lives in AGENTS.md, imported here:

1 other project uses a version of this.

Adopted by

Most recently taken up by

  • Other versions1 project uses a version of this.

    Word for word · 1

    1. Greg-Klein/implementation-factory★ 1100% same

    Edited · 0

    None found.

    Wrote their own version · 0

    None found.

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

  • In this repository13 other files it gives its agents.

The file

Create a free account to mount
Files
CLAUDE.md

CLAUDE.md

This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository. The shared guidance (what the repo is, commands, architecture, conventions, code habits) lives in AGENTS.md, imported here:

@AGENTS.md

Claude Code specifics

  • AGENTS.md is the file to edit. What any coding agent needs goes there; this file only holds what applies to Claude Code alone, and never restates a rule AGENTS.md owns.
  • Claude Code loads this file, and AGENTS.md through the import above, in a session opened in this checkout or in a worktree of it. A self-improvement-* worktree therefore reads its branch's own copy of both, which is why the judge of an improvement branch runs from its input directory and not from the worktree (JudgeOptions in console/server/engine/types.ts).
  • Neither file is runtime context for the projects the plugin drives: the workflow prompts read principles/ and contracts/ through ${CLAUDE_PLUGIN_ROOT} paths.
  • To try a change to the plugin (commands/, agents/, hooks/, skills/) in a session, load this checkout with claude --plugin-dir <this repo>, which is what the console does for a run.

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