agentleFS
Sign inStart free
Stephen-studyingStephen-studying/tech-route-maker/CLAUDE.md

tech-route-maker

CLAUDE.md2 starsChanged 4 months agoMITView on GitHub

Use this repository as a Claude-compatible project context or skill folder. Read SKILL.md first. It is the source of truth for when to use tech-route-maker, how to select default presets, when to ask necessary questions, and how to render editable outputs. When a user asks for a technical route diagram, paper framework figure, engineering route, project roadmap, method flowchart, workflow, pipeline, or editable diagram: If the user asks for copyable Draw.io or diagrams.net code, render drawio-code and tell them to…

2 other projects use a version of this.

Adopted by

Most recently taken up by

  • Other versions2 projects use a version of this.

    Word for word · 2

    1. cjh-solver/MathModeling-Skills-Arsenal★ 14100% same
    2. hua695/MathModeling-Skills-Arsenal★ 12100% 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 repository4 other files it gives its agents.

The file

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

6 rules. About 0 are common, 2 are distinctive, and 4 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.

  • 4

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use this repository as a Claude-compatible project context or skill folder.

    line 3
  2. Very specific:

    Read SKILL.md first. It is the source of truth for when to use tech-route-maker, how to select default presets, when to ask necessary …

    line 5
  3. Distinctive:

    When a user asks for a technical route diagram, paper framework figure, engineering route, project roadmap, method flowchart, workflow, …

    line 7
  4. Very specific:

    Read references/domain-profiles.md when the discipline is unclear or unfamiliar.

    line 11
  5. Very specific:

    If the user asks for copyable Draw.io or diagrams.net code, render drawio-code and tell them to paste tech-route.drawio-code.xml into …

    line 19
  6. Very specific:

    Use --allow-draft only for an explicitly unfinished draft.

    line 21

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

Claude Adapter

Use this repository as a Claude-compatible project context or skill folder.

Read SKILL.md first. It is the source of truth for when to use tech-route-maker, how to select default presets, when to ask necessary questions, and how to render editable outputs.

When a user asks for a technical route diagram, paper framework figure, engineering route, project roadmap, method flowchart, workflow, pipeline, or editable diagram:

  1. Inspect source evidence.
  2. Establish domain_context: discipline, subfield, project type, research object, method family, data/materials, constraints and evaluation metrics.
  3. Read references/domain-profiles.md when the discipline is unclear or unfamiliar.
  4. Build tech-route.json.
  5. Inventory local sources with trm ingest and record stable source IDs and SHA-256 hashes.
  6. Offer the closest preset, then confirm missing domain and final delivery choices instead of guessing them.
  7. Run trm validate <route> --strict.
  8. Render selected formats with trm render only after final blockers are resolved.
  9. Report QUALITY_REPORT.md findings and required manual revision.

If the user asks for copyable Draw.io or diagrams.net code, render drawio-code and tell them to paste tech-route.drawio-code.xml into diagrams.net / draw.io through Extras > Edit Diagram.

Use --allow-draft only for an explicitly unfinished draft. Do not render screenshots as the main editable output, and do not present inferred nodes as evidence.

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