Catalyst-Forge-LLCCatalyst-Forge-LLC/ember-dossier/.cursor/rules/forgetrail-lessons-mcp.mdc

ember-dossier / 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 repository11 other files it gives its agents.
- AGENTS.mdAGENTS.md
- .forgetrail/AGENTS.mdAGENTS.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
- .cursor/rules/npm-publish.mdcCursor rule
- .cursor/rules/smellcheck.mdcCursor rule
- ember-dossierSkill
- ember-dossierSkill

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:
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.
line 21

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

forgetrail-lessons-mcp.mdc

---
description: Implementation detail — ForgeTrail MCP searchLessons + getAntiPatterns (also see forgetrail-lessons-gate.mdc)
globs: skills/**,site/**,docs/**
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 skill, site, or docs.

For **site copy**, **skill contract**, or **example subjects**:

1. **`searchLessons`** (ForgeTrail MCP — server `forgetrail`)
   - Short **`query`** keywords, e.g. `landing copy`, `skill documentation`, `generic examples`.
   - Optional **`limit`** (default 10).

2. **`getAntiPatterns`** (same server, no arguments)

**When to skip:** trivial one-line edits, or when the user explicitly asks not to broaden scope.

**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.

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