KaibanJS / rules
Cursor rule1.5k starsChanged 7 months agoMITView on GitHub
User-facing repo text and AI-generated content must be in English
Trending
Quiet since June.thin dataabout the whole repository
Who's talking about kaiban-ai/KaibanJS
- andreibesleaga/kaiban-distributed“chore(deps): bump the production-dependencies group with 7 updates”GitHub · Jun 22, 2026
- PyTorchKR/landscape“[Add] KaibanJS (kaiban-ai/KaibanJS)”GitHub · Jun 3, 2026
- anthonydevs17/KaibanJS“Enhancement: Control Flow Examples and Mapping Workflow Implementation”GitHub · Jun 17, 2025
- Jenqyang/Awesome-AI-Agents“Add KaibanJS please”GitHub · Nov 18, 2024
- e2b-dev/awesome-ai-agents“Add KaibanJS please”GitHub · Nov 18, 2024
The biggest 5 of 5 mentions linking to the repository that our crawl found. Each line is their own headline.
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,243 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.
The file
We split this english-repo-content.mdc into the rules it gives an agent
3 rules. About 0 are common, 3 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 12
Commit messages, PR titles/descriptions, and GitHub issue bodies drafted from this repo
- Distinctive: line 14
Do not add Spanish (or other languages) for primary documentation or issue templates unless the project explicitly maintains a localized …
- Distinctive: line 16
When editing existing Spanish or mixed-language files, translate to English unless the file is clearly marked as a legacy / archived …
≈ “Common” is an estimate: at least 1 in 5 of the 6,809 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: User-facing repo text and AI-generated content must be in English alwaysApply: true --- # English-only repository content All **user-facing** text in this repository should be written in **English**, including: - Markdown under `out/`, `docs/`, `playground/**/README.md`, root `README.md`, issue drafts, and ADRs - Comments in source code where they explain behavior to maintainers (prefer concise English) - Commit messages, PR titles/descriptions, and GitHub issue bodies drafted from this repo Do **not** add Spanish (or other languages) for primary documentation or issue templates unless the project explicitly maintains a localized copy alongside the English source. When editing existing Spanish or mixed-language files, **translate to English** unless the file is clearly marked as a legacy / archived locale-specific document.
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.

