agentleFS
Sign inStart free
Stephen-studyingStephen-studying/tech-route-maker/.cursor/rules/tech-route-maker.mdc

tech-route-maker / rules

Cursor rule2 starsChanged 4 months agoMITView on GitHub

Use tech-route-maker to create evidence-grounded editable research and engineering route diagrams.

  • Where files are headingNew Cursor rule files have more rules about planning and tracking tasks, and fewer about code style.

    Of the Cursor rule files we read, the 4,183 first seen in the last six months, against the older ones: the kind of rule that gained most share, and the kind that lost most. About files like this in general, not this one, and an estimate, since a kind is a pattern in the words.

  • In this repository4 other files it gives its agents.

The file

We split this tech-route-maker.mdc into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    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. Distinctive:

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

    line 8
  2. Distinctive:

    Run strict validation before final rendering.

    line 14
  3. Very specific:

    Keep PPTX/SVG/Draw.io/Excalidraw outputs editable.

    line 16
  4. Very specific:

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

    line 17
  5. Distinctive:

    Use one concise grouped question rather than guessing final choices.

    line 19

≈ “Common” is an estimate: at least 1 in 5 of the 6,668 Cursor rule 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
tech-route-maker.mdc
---
description: Use tech-route-maker to create evidence-grounded editable research and engineering route diagrams.
alwaysApply: true
---

# tech-route-maker Cursor Rule

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

1. Read `SKILL.md`.
2. Build or update `tech-route.json` before rendering.
3. Inventory sources and record stable IDs, locators and SHA-256 hashes.
4. Offer the closest preset, then confirm missing domain and final delivery choices.
5. Run strict validation before final rendering; inference and unresolved questions are draft-only.
6. Report `QUALITY_REPORT.md` findings and required manual revision.
7. Keep PPTX/SVG/Draw.io/Excalidraw outputs editable; do not use screenshots as the main artifact.
8. If the user asks for copyable Draw.io or diagrams.net code, include `drawio-code` and explain how to paste `tech-route.drawio-code.xml` into [diagrams.net / draw.io](https://app.diagrams.net/) through **Extras > Edit Diagram**.

Use one concise grouped question rather than guessing final choices.

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