skills / rules
Cursor rule0 starsChanged 2 months agoMITView on GitHub
Markdown writing conventions for marslo
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,183 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 repository32 other files it gives its agents.
- .claude/CLAUDE.mdCLAUDE.md
- .cursor/rules/base-rule.mdcCursor rule
- .cursor/rules/bash-style.mdcCursor rule
- .cursor/rules/groovy-implicit-return.mdcCursor rule
- .cursor/rules/groovy-style.mdcCursor rule
- .cursor/rules/python-style.mdcCursor rule
- automateSkill
- autopilotSkill
- canvasSkill
- create-hookSkill
- create-ruleSkill
- create-skillSkill
- create-subagentSkill
- cursor-blameSkill
- git-messageSkill
- goalSkill
- loopSkill
- migrate-to-skillsSkill
- new-repoSkill
- onboardSkill
- originSkill
- rename-chatSkill
- review-bugbotSkill
- review-securitySkill
- reviewSkill
- sdkSkill
- shareSkill
- shellSkill
- split-to-prsSkill
- statuslineSkill
- update-cli-configSkill
- update-cursor-settingsSkill
The file
We split this markdown-style.mdc into the rules it gives an agent
4 rules. About 0 are common, 4 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈4
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 14
Results / focus only: No narration, no filler, no restating the obvious.
- Distinctive: line 15
Prefer tables / code / lists over prose: If a table or code block conveys it, don't write a paragraph.
- Distinctive: line 16
Comment code sparingly: Add short inline comments only where a snippet isn't self-evident.
- Distinctive: line 17
No 80-column wrapping: Don't hard-wrap prose to guess an 80-char width.
≈ “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: Markdown writing conventions for marslo globs: **/*.md alwaysApply: false --- # Markdown Style Concise, scannable Markdown. Describe **what / how**; skip **why / rationale**. ## Rules - **What & how, not why.** State the result / step / key point. Drop background and rationale. Only if the logic is genuinely complex, add 1–2 lines of explanation — no more. - **Results / focus only.** No narration, no filler, no restating the obvious. - **Prefer tables / code / lists over prose.** If a table or code block conveys it, don't write a paragraph. - **Comment code sparingly.** Add short inline comments only where a snippet isn't self-evident; keep them terse. - **No 80-column wrapping.** Don't hard-wrap prose to guess an 80-char width. Break lines by logic / context (one idea per line); let the line run as long as it reads naturally. - **Use GitHub callouts** for emphasis / tips / references — not bold prose (**files only**, **never in use chat/agent/assistant replies**). : | callout | use for | |---|---| | `> [!NOTE]` | context / reference | | `> [!TIP]` | optional advice | | `> [!IMPORTANT]` | must-know | | `> [!WARNING]` | gotcha / risk | | `> [!CAUTION]` | danger / data loss | Scope — **files only**: use callouts **only** when writing or editing an actual Markdown document/file (`*.md`, README, docs, etc.). In chat / assistant replies, **never** use `> [!NOTE]` / `> [!TIP]` etc. — even though the reply is rendered as Markdown, callout syntax is for files, not conversation. ## Prefer ```diff - Because the cache can grow without bound on long-running hosts and eventually - cause memory pressure, you should periodically call `.clear()`, which frees the - backing store so that ... + Call `.clear()` periodically to cap memory. ``` > [!TIP] > One idea per line. If you're explaining *why*, cut it.
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.