zeroagent-studio / rules
Cursor rule4 starsChanged 4 months agoMITView on GitHub
Version and changelog guidance for ZeroAgent Studio releases.
We split this release-versioning.mdc into the rules it gives an agent
3 rules. About 0 are common, 0 are distinctive, and 3 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.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 21
Update CHANGELOG.md (Keep a Changelog format) if shipping user-visible changes.
- Very specific: line 22
Update #/guide / README if user-facing behavior changed.
- Very specific: line 24
Run npm ci then npm run ci.
≈ “Common” is an estimate: at least 1 in 5 of the 6,350 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: Version and changelog guidance for ZeroAgent Studio releases. globs: package.json, README.md, CHANGELOG.md alwaysApply: false --- # Release Versioning ZeroAgent Studio uses SemVer in `package.json`. ## Bump guidance | Bump | When | |------|------| | **Major** | Breaking workflow format, removed brain providers, deploy URL/path change | | **Minor** | New brain provider, new tool type, new node type | | **Patch** | Bug fixes, UI polish, dependency updates, docs | ## Release checklist 1. Update `CHANGELOG.md` (Keep a Changelog format) if shipping user-visible changes. 2. Update `#/guide` / README if user-facing behavior changed. 3. Bump `package.json` version. 4. Run `npm ci` then `npm run ci`. 5. Deploy: push to `main` (GitHub Actions `deploy.yml`) or `npm run deploy` (gh-pages CLI fallback). ## Current deployment - Static export to `dist/` - `vite.config.ts` uses `base: './'` (any GitHub Pages subpath) - Live site: `https://sakurablush.github.io/zeroagent-studio/` - Catalog counts: `src/lib/siteStats.ts` — do not hardcode tool numbers in copy
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 3,978 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 repository15 other files it gives its agents.
- AGENTS.mdAGENTS.md
- .cursor/rules/pre-commit-quality-gate.mdcCursor rule
- .cursor/rules/zeroagent-advisor.mdcCursor rule
- .cursor/rules/zeroagent-debugger.mdcCursor rule
- .cursor/rules/zeroagent-engineer.mdcCursor rule
- .cursor/rules/zeroagent-planner.mdcCursor rule
- .cursor/rules/zeroagent-reviewer.mdcCursor rule
- .cursor/rules/zeroagent-security-auditor.mdcCursor rule
- .cursor/rules/zeroagent-test-engineer.mdcCursor rule
- add-brain-providerSkill
- add-browser-toolSkill
- pre-commit-ciSkill
- release-versioningSkill
- review-before-mergeSkill
- ship-patchSkill
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.