tamirs-superpowers / rules
Cursor rule2 starsChanged 3 months agoMITView on GitHub
Bump the version in plugin-version.json then run check-version-truth.sh --sync — never hand-edit a manifest. Canonical: rules/dev/plugin-version-bump.md
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 repository46 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- .cursor/rules/commit-conventions.mdcCursor rule
- .cursor/rules/cross-platform-handoff.mdcCursor rule
- .cursor/rules/dev-files-workspace.mdcCursor rule
- .cursor/rules/documentation-standards.mdcCursor rule
- .cursor/rules/gh-cli-preference.mdcCursor rule
- .cursor/rules/github-repository-policy.mdcCursor rule
- .cursor/rules/git-worktree-agent-workflow.mdcCursor rule
- .cursor/rules/hooks-guide.mdcCursor rule
- .cursor/rules/plugin-structure.mdcCursor rule
- .cursor/rules/skill-frontmatter.mdcCursor rule
- .cursor/rules/skill-quality-standards.mdcCursor rule
- .cursor/rules/skills-guide.mdcCursor rule
- .cursor/rules/user-facing-script-standards.mdcCursor rule
- run-tamirs-superpowersSkill
- field-notebook-uiSkill
- diagnose-refusalSkill
- targeted-debugSkill
- decisionSkill
- deliver-devSkill
- diagnose-objectiveSkill
- orchestrate-devSkill
- plan-devSkill
- pr-devSkill
- start-devSkill
- switch-devSkill
- worker-devSkill
- changelog-reviewSkill
- dark-terminal-docSkill
- docs-reviewSkill
- platform-syncSkill
- mcp-builderSkill
- mcp-paginationSkill
- cleanupSkill
- github-policySkill
- multi-agent-repoSkill
- repo-scaffoldSkill
- repo-standardsSkill
- capture-configSkill
- find-skillSkill
- notify-setupSkill
- retroSkill
- session-reportSkill
- skill-creatorSkill
- usage-captureSkill
The file
We split this plugin-version-bump.mdc into the rules it gives an agent
2 rules. About 0 are common, 0 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
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: line 15
After changing shipped content (skills/, hooks/, agents/, core/, manifests, scripts/):
- Very specific: line 22
Never hand-edit .cursor-plugin/plugin.json's version.
≈ “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: "Bump the version in plugin-version.json then run check-version-truth.sh --sync — never hand-edit a manifest. Canonical: rules/dev/plugin-version-bump.md"
alwaysApply: false
---
<!-- GENERATED FILE — DO NOT EDIT.
Source: rules/dev/plugin-version-bump.md (frontmatter + summary: platforms/cursor/rules.map.json)
Generator: scripts/build-cursor-rules.sh
Regenerate: make cursor-rules -->
# Plugin version bump
Canonical rule: `rules/dev/plugin-version-bump.md`.
After changing shipped content (`skills/`, `hooks/`, `agents/`, `core/`, manifests, `scripts/`):
1. Edit the version in **`plugin-version.json` only** — a targeted string replace on the version line, never a `jq`/`json.dump` rewrite.
2. `bash scripts/check-version-truth.sh --sync` propagates it to every consumer (all platform manifests, README badge, `platform-targets.json`).
3. Promote the `CHANGELOG.md` entry and update anything else the change falsified (skill counts, install docs).
4. `make validate`, open a PR, and after merge run the Release workflow to cut `vX.Y.Z` — then verify the tag contains the change.
Never hand-edit `.cursor-plugin/plugin.json`'s version. Never move a version backwards past a cut release.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
Reviews can't be read right now.
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.