aa-sdk / rules
Cursor rule321 starsChanged 5 months agoMITView on GitHub
package publish and post-merge docs workflow guidance
We split this release-workflows.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: line 15
Keep --no-private, --no-verify-access, and the PR_BYPASSER app token on the publish job — Lerna pushes the version commit + tag past branch …
- Distinctive: line 18
Keep secrets in GitHub Actions secrets and preserve least-privilege workflow permissions.
- Very specific: line 20
Read .agents/skills/release-workflows/ before changing release automation.
≈ “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: package publish and post-merge docs workflow guidance globs: ".github/workflows/*.yml,.github/actions/**/*.yml,lerna.json,packages/*/inject-version.ts" alwaysApply: false --- # Release Workflows - `publish-package.yml` is a manual dispatch with a `publish` boolean. It must publish from the dispatched branch (`main` for v5, `v4.x.x` for legacy backports) — do not hardcode a `ref:` that overrides the dispatch. - `revalidate-sdk-content.yml` and `trigger-sdk-indexer.yml` are post-merge hooks on `main` that call external docs systems. Do not trigger or broaden them without approval. - Keep `--no-private`, `--no-verify-access`, and the `PR_BYPASSER` app token on the publish job — Lerna pushes the version commit + tag past branch protection using that token. - Keep secrets in GitHub Actions secrets and preserve least-privilege workflow permissions. - Read `.agents/skills/release-workflows/` before changing release automation. - The legacy `publish-v5-beta.yml` and `update-v5-docs.yml` workflows were retired when v5 graduated to `main` on 2026-05-20. Do not resurrect them.
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 repository16 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- .github/copilot-instructions.mdCopilot instructions
- .cursor/rules/docs-reference.mdcCursor rule
- .cursor/rules/docs-reviewer.mdcCursor rule
- .cursor/rules/error-handling.mdcCursor rule
- .cursor/rules/package-exports.mdcCursor rule
- .cursor/rules/testing.mdcCursor rule
- documentationSkill
- error-handlingSkill
- package-exportsSkill
- release-workflowsSkill
- smart-accountsSkill
- testingSkill
- toolingSkill
- wallet-apisSkill
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.