temper-pass / rules
Cursor rule0 starsChanged 47 days agoMITView on GitHub
Implementation detail — ForgeTrail MCP searchLessons + getAntiPatterns (also see forgetrail-lessons-gate.mdc)
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,157 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 repository8 other files it gives its agents.
- AGENTS.mdAGENTS.md
- .forgetrail/AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- .forgetrail/CLAUDE.mdCLAUDE.md
- .cursor/rules/commit-messages.mdcCursor rule
- .cursor/rules/forgetrail-lessons-gate.mdcCursor rule
- .cursor/rules/forgetrail-phase-status.mdcCursor rule
- .cursor/rules/git-user-commits.mdcCursor rule
The file
We split this forgetrail-lessons-mcp.mdc into the rules it gives an agent
1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 24
Product-facing users: Do not mention MCP, tool names, or this rule in user-visible text unless they ask how the workflow is wired up.
≈ “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.
Files
--- description: Implementation detail — ForgeTrail MCP searchLessons + getAntiPatterns (also see forgetrail-lessons-gate.mdc) globs: pages/**,posts/**,passes/**,site/** alwaysApply: false --- # ForgeTrail lessons + anti-patterns (MCP) **Workflow:** **`forgetrail-lessons-gate.mdc`** defines **when** to run tools before larger tasks. This file adds **density** when you are already editing app code: still run **`getAntiPatterns`** + **`searchLessons`** if the gate applies and you have not run them in this task block. **Adjust `globs`** in the frontmatter above to match your repo (e.g. add `src/lib/server/**`, e2e paths, or product-specific folders). For **UI/UX**, **data/API**, **export or document pipelines**, **progress/loading**, **user-facing copy**, or **LLM prompt tone**: 1. **`searchLessons`** (ForgeTrail MCP — typically configured as the `forgetrail` server in `.cursor/mcp.json`) - Pass a short **`query`** string (keywords, not sentences), e.g. `wizard tabs progress`, `empty state copy`, `export loading`, `LLM JSON`, `Svelte backdrop`. - Optional **`limit`** (default 10). 2. **`getAntiPatterns`** (same server, no arguments) - Skim for failure modes that apply (vague specs, schema drift, untested refactors, jargon in empty states). **When to skip:** trivial one-line edits, pure type renames with no UX impact, or when the user explicitly asks not to broaden scope — consistent with the lessons gate. **Product-facing users:** Do not mention MCP, tool names, or this rule in user-visible text unless they ask how the workflow is wired up.
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
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.