agentic-ui / rules
Cursor rule233 starsChanged 7 months agoMITView on GitHub
2 other projects use a version of this.
Adopted by
Most recently taken up by
- ant-design/agentic-uiword for word, first seen Oct 9, 2026
- ant-design/pro-componentsword for word, first seen Oct 8, 2026
Other versions2 projects use a version of this.
Word for word · 2
- ant-design/pro-components★ 4.9k100% same
- ant-design/agentic-ui★ 233100% same
Edited · 0
None found.
Wrote their own version · 0
None found.
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
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,181 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 repository30 other files it gives its agents.
- AGENTS.mdAGENTS.md
- .cursor/rules/AGENTS.mdcCursor rule
- .cursor/rules/clean-code.mdcCursor rule
- .cursor/rules/playwright.mdcCursor rule
- .cursor/rules/react.mdcCursor rule
- .cursor/rules/test.mdcCursor rule
- llms.txtllms.txt
- agentic-ui-developmentSkill
- agentic-ui-usageSkill
- component-agentic-layoutSkill
- component-agent-run-barSkill
- component-ai-labelSkill
- component-answer-alertSkill
- component-bubbleSkill
- component-chat-boot-pageSkill
- component-chat-layoutSkill
- component-historySkill
- component-markdown-editorSkill
- component-markdown-input-fieldSkill
- component-pluginsSkill
- component-quote-backtoSkill
- component-schemaSkill
- component-sharedSkill
- component-task-listSkill
- component-thought-chainSkill
- component-tool-useSkill
- component-welcome-messageSkill
- component-workspaceSkill
- gh-create-prSkill
- markdown-syntax-guideSkill
The file
We split this codequality.mdc into the rules it gives an agent
11 rules. About 0 are common, 11 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈11
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 9
Always verify information before presenting it.
- Distinctive: line 18
Avoid giving feedback about understanding in comments or documentation.
- Distinctive: line 21
Don't suggest whitespace changes.
- Distinctive: line 24
Don't summarize changes made.
- Distinctive: line 27
Don't invent changes other than what's explicitly requested.
- Distinctive: line 30
Don't ask for confirmation of information already provided in the context.
- Distinctive: line 33
Don't remove unrelated code or functionalities.
- Distinctive: line 39
Don't ask the user to verify implementations that are visible in the provided context.
- Distinctive: line 42
Don't suggest updates or changes to files when there are no actual modifications needed.
- Distinctive: line 45
Always provide links to the real files, not x.md.
- Distinctive: line 48
Don't show or discuss the current implementation unless specifically requested.
≈ “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: Code Quality Guidelines globs: alwaysApply: false --- # Code Quality Guidelines ## Verify Information Always verify information before presenting it. Do not make assumptions or speculate without clear evidence. ## File-by-File Changes Make changes file by file and give me a chance to spot mistakes. ## No Apologies Never use apologies. ## No Understanding Feedback Avoid giving feedback about understanding in comments or documentation. ## No Whitespace Suggestions Don't suggest whitespace changes. ## No Summaries Don't summarize changes made. ## No Inventions Don't invent changes other than what's explicitly requested. ## No Unnecessary Confirmations Don't ask for confirmation of information already provided in the context. ## Preserve Existing Code Don't remove unrelated code or functionalities. Pay attention to preserving existing structures. ## Single Chunk Edits Provide all edits in a single chunk instead of multiple-step instructions or explanations for the same file. ## No Implementation Checks Don't ask the user to verify implementations that are visible in the provided context. ## No Unnecessary Updates Don't suggest updates or changes to files when there are no actual modifications needed. ## Provide Real File Links Always provide links to the real files, not x.md. ## No Current Implementation Don't show or discuss the current implementation unless specifically requested.
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.