jumpstarter / rules
Cursor rule233 starsChanged 37 days agoApache-2.0View on GitHub
This rule helps with creating Jumpstarter Enhancement Proposals (JEPs). JEPs use this format for individual decisions:
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 repository8 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- .cursor/rules/creating-new-drivers.mdcCursor rule
- .cursor/rules/e2e-doc-sync.mdcCursor rule
- .cursor/rules/project-structure.mdcCursor rule
- .cursor/rules/releasing-operator.mdcCursor rule
- .cursor/rules/working-with-operator.mdcCursor rule
- releaseSkill
- propose-jepSkill
The file
We split this jep-process.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
Choose the next JEP number: Look at existing files in docs/source/contributing/jeps/ and pick the next available incrementing integer.
- Distinctive: line 32
Test Plan (unit, integration, HiL, manual)
- Very specific: line 60
All JEPs should be merged as PRs so the documentation is part of the Jumpstarter docs/source
≈ “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
--- alwaysApply: false --- # JEP Process This rule helps with creating Jumpstarter Enhancement Proposals (JEPs). ## When to Use - **JEP**: Cross-cutting changes that affect multiple components, change public APIs or protocols, or require community consensus. ## Creating a JEP 1. **Choose the next JEP number**: Look at existing files in `docs/source/contributing/jeps/` and pick the next available incrementing integer. JEP-0000 through JEP-0009 are reserved for process/meta-JEPs, so start from JEP-0010 for regular proposals. 2. **Create the file**: Copy the template from `docs/source/contributing/jeps/JEP-NNNN-template.md` to `docs/source/contributing/jeps/JEP-NNNN-short-title.md`, replacing `NNNN` with the zero-padded number and `short-title` with a descriptive slug. 3. **Fill in the metadata table**: - Set the JEP number (incrementing integer, NOT the PR number) - Set the title, author(s) with GitHub handle and email - Set the type: `Standards Track`, `Informational`, or `Process` - Set the status to `Draft` initially, then `Discussion` when the PR is ready for review - Set the created date to today 4. **Fill in all mandatory sections**: - Abstract (3-5 sentences) - Motivation (concrete problem description) - Proposal (written as if teaching the feature) - Design Decisions (use DD-N pattern with alternatives and rationale) - Design Details (architecture, data flow, error handling) - Test Plan (unit, integration, HiL, manual) - Backward Compatibility - Consequences (positive and negative) - Rejected Alternatives 5. **Open a PR** against main with the `jep` label. ## Design Decision Format (DD-N) JEPs use this format for individual decisions: ```markdown ### DD-N: Decision title **Alternatives considered:** 1. **Option A** - Brief description. 2. **Option B** - Brief description. **Decision:** Option A. **Rationale:** Explain why this option was chosen. ``` ## Key Rules - JEP numbers are incrementing integers, NOT derived from PR numbers - JEPs live in `docs/source/contributing/jeps/` - All JEPs should be merged as PRs so the documentation is part of the Jumpstarter docs/source - Rejected JEPs are normally not merged, but can be merged with "Rejected" status if there is an architectural reason to preserve them - The license for all documents is Apache-2.0
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.