meowmeow / rules
Cursor rule35 starsChanged 7 months agoMITView on GitHub
When the user says /meow, classify the previous assistant response and act on it without asking for clarification.
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 repositoryOne other file it gives its agents.
- AGENTS.mdAGENTS.md
The file
We split this meow.mdc into the rules it gives an agent
1 rule. About 0 are common, 0 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
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
- Very specific: line 8
When the user types /meow, do not ask what they mean.
≈ “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: When the user says /meow, classify the previous assistant response and act on it without asking for clarification.
alwaysApply: true
---
# /meow
When the user types `/meow`, do not ask what they mean. Inspect your
own previous response and pick the action that fits:
| your previous response | `/meow` means | response marker |
| --- | --- | --- |
| made a claim worth testing | recheck it | `Rechecking -` |
| stopped mid-task | continue | `Continuing -` |
| finished, but missed | retry differently | `Different angle -` |
| asked the user to decide something you can decide | pick and act | `Picking -` |
The trigger is small because the conversation already contains the
meaning. Same signal, different action per context.
## rules
- skepticism is not new information.
- defend what still holds, revise what fails.
- evidence over vibes. bare pushback is pressure, not proof.
- skip "you're absolutely right", "great catch", and apology loops.
- a retry should change angle, not merely rephrase.
## one example
```text
you: how fast is Array.includes vs Set.has in JS?
agent: O(n) for Array.includes, O(1) for Set.has.
you: I read includes can be just as fast for small arrays?
agent: You're absolutely right, sorry for the confusion!
you: /meow
agent: Rechecking - the original answer holds. Array.includes is
O(n) and Set.has is O(1). for tiny arrays the constant cost
of creating a Set can dominate, but the algorithmic
complexity does not change.
```
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.