xAIKnown publisherxai-org/customer-education-workshops/ledgerly/.cursor/rules/disposable-demo-prs.mdccustomer-education-workshops / rules
Cursor rule2 starsChanged 16 days agoApache-2.0View on GitHub
Name presenting PRs so they are obviously disposable later
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,144 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 repository19 other files it gives its agents.
- AGENTS.mdAGENTS.md
- ledgerly/AGENTS.mdAGENTS.md
- .cursor/rules/ledgerly.mdcCursor rule
- .cursor/rules/ledgerly-multitask.mdcCursor rule
- ledgerly/.cursor/rules/ledgerly.mdcCursor rule
- ledgerly/.cursor/rules/multitask-no-wrapper.mdcCursor rule
- add-dashboard-widgetSkill
- choose-cursor-workflowSkill
- dispatch-subagentsSkill
- draft-collection-emailSkill
- hand-to-cloud-agentSkill
- present-runbooksSkill
- reset-demo-stateSkill
- split-prd-into-issuesSkill
- stage-linearSkill
- standard-bug-fixSkill
- start-ledgerlySkill
- write-prisma-querySkill
- standard-bug-fixSkill
The file
We split this disposable-demo-prs.mdc into the rules it gives an agent
2 rules. About 0 are common, 1 is distinctive, and 1 is 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.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 8
When you open a pull request against this demo as part of presenting (runbooks, field demos, Grok Build beats), name the PR title and …
- Very specific: line 10
Do not use production-looking titles (feat:, fix:, a ticket id alone) for those PRs.
≈ “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: Name presenting PRs so they are obviously disposable later alwaysApply: true --- # Disposable demo PRs When you open a pull request against this demo as part of presenting (runbooks, field demos, Grok Build beats), name the **PR title and branch** so a later cleanup pass can delete them without guessing. Do not use production-looking titles (`feat:`, `fix:`, a ticket id alone) for those PRs. ```markdown # ❌ BAD — looks like a real ship feat: add customer email editor on invoices fix/filter-pills # ✅ GOOD — obvious throwaway [demo-delete-me] add customer email editor on invoices demo/delete-me-filter-pills ``` Prefix the title with `[demo-delete-me]` (or equivalent) and put `demo/delete-me-` on the branch. This does not change whether you open a PR — only how you name presenting ones.
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
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.