Catalyst-Forge-LLCCatalyst-Forge-LLC/ember-dossier/.cursor/rules/npm-publish.mdc

ember-dossier / rules

Cursor rule0 starsChanged 47 days agoMITView on GitHub

npm publish is allowed in this repo when the user wants it

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-lessons-mcp.mdcCursor rule
- .cursor/rules/forgetrail-phase-status.mdcCursor rule
- .cursor/rules/git-user-commits.mdcCursor rule
- .cursor/rules/smellcheck.mdcCursor rule
- ember-dossierSkill
- ember-dossierSkill

The file

We split this npm-publish.mdc into the rules it gives an agent

3 rules. About 0 are common, 1 is distinctive, and 2 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.
2
Very specific
Tied to their project's names, files or tools. Probably skip.

Common
Distinctive
Very specific

Very specific:
If the working tree is dirty, commit first so pnpm publish git-checks pass.
line 11
Very specific:
Use pnpm publish --access public (or the OTP form if 2FA requires it).
line 13
Distinctive:
Do not apply smellcheck’s “agents must not publish” rule here.
line 14

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

npm-publish.mdc

---
description: npm publish is allowed in this repo when the user wants it
alwaysApply: true
---

# npm publish

The owner publishes this package. When they ask to publish, or say to
always allow npm publish, **do it**.

- If the working tree is dirty, **commit first** so `pnpm publish`
  git-checks pass. Do not reach for `--no-git-checks` unless they ask.
- Use `pnpm publish --access public` (or the OTP form if 2FA requires it).
- Do not apply smellcheck’s “agents must not publish” rule here.

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