agentleFS
Sign inStart free
hlhr202hlhr202/Conductor-for-all/CLAUDE.md

Conductor-for-all

CLAUDE.md52 starsChanged 8 months agoApache-2.0View on GitHub

If a user mentions a "plan" or asks about the plan, and they have used the conductor extension in the current session, they are likely referring to the conductor/tracks.md file or one of the track plans (conductor/tracks/<track_id>/plan.md). PROTOCOL: How to locate files. To find a file (e.g., "Product Definition") within a specific context (Project Root or a specific Track): 1. Identify Index: Determine the relevant index file: - Project Context: conductor/index.md - Track Context: a. Resolve and read the Tracks…

The file

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

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

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

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

    If a user mentions a "plan" or asks about the plan, and they have used the conductor extension in the current session, they are likely …

    line 3
  2. Distinctive:

    Check Index: Read the index file and look for a link with a matching or semantically similar label.

    line 20
  3. Very specific:

    Resolve Path: If a link is found, resolve its path relative to the directory containing the index.md file.

    line 22
  4. Distinctive:

    Fallback: If the index file is missing or the link is absent, use the Default Path keys below.

    line 25

≈ “Common” is an estimate: at least 1 in 5 of the 26,980 CLAUDE.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
CLAUDE.md

Conductor Context

If a user mentions a "plan" or asks about the plan, and they have used the conductor extension in the current session, they are likely referring to the conductor/tracks.md file or one of the track plans (conductor/tracks/<track_id>/plan.md).

Universal File Resolution Protocol

PROTOCOL: How to locate files. To find a file (e.g., "Product Definition") within a specific context (Project Root or a specific Track):

  1. Identify Index: Determine the relevant index file:
    • Project Context: conductor/index.md
    • Track Context: a. Resolve and read the Tracks Registry (via Project Context). b. Find the entry for the specific <track_id>. c. Follow the link provided in the registry to locate the track's folder. The index file is <track_folder>/index.md. d. Fallback: If the track is not yet registered (e.g., during creation) or the link is broken: 1. Resolve the Tracks Directory (via Project Context). 2. The index file is <Tracks Directory>/<track_id>/index.md.
  2. Check Index: Read the index file and look for a link with a matching or semantically similar label.
  3. Resolve Path: If a link is found, resolve its path relative to the directory containing the index.md file.
    • Example: If conductor/index.md links to ./workflow.md, the full path is conductor/workflow.md.
  4. Fallback: If the index file is missing or the link is absent, use the Default Path keys below.
  5. Verify: You MUST verify the resolved file actually exists on the disk.

Standard Default Paths (Project):

  • Product Definition: conductor/product.md
  • Tech Stack: conductor/tech-stack.md
  • Workflow: conductor/workflow.md
  • Product Guidelines: conductor/product-guidelines.md
  • Tracks Registry: conductor/tracks.md
  • Tracks Directory: conductor/tracks/

Standard Default Paths (Track):

  • Specification: conductor/tracks/<track_id>/spec.md
  • Implementation Plan: conductor/tracks/<track_id>/plan.md
  • Metadata: conductor/tracks/<track_id>/metadata.json

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