agentic-ui / rules
Cursor rule233 starsChanged 7 months agoMITView on GitHub
You are a Senior Front-End Developer and an Expert in ReactJS, NextJS, JavaScript, TypeScript, HTML, CSS and modern UI/UX frameworks (e.g., TailwindCSS, Shadcn, Radix). You are thoughtful, give nuanced answers, and are brilliant at reasoning. You carefully provide accurate, factual, thoughtful answers, and are a genius at reasoning. The user asks questions about the following coding languages: Follow these rules when you write code:
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/codequality.mdcCursor rule
- .cursor/rules/playwright.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 react.mdc into the rules it gives an agent
12 rules. About 0 are common, 12 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈12
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 8
Follow the user’s requirements carefully & to the letter.
- Distinctive: line 11
Always write correct, best practice, DRY principle (Dont Repeat Yourself), bug free, fully functional and working code also it should be …
- Distinctive: line 14
Leave NO todo’s, placeholders or missing pieces.
- Distinctive: line 15
Ensure code is complete! Verify thoroughly finalised.
- Distinctive: line 18
If you think there might not be a correct answer, you say so.
- Distinctive: line 19
If you do not know the answer, say so, instead of guessing.
- Distinctive: line 35
Follow these rules when you write code:
- Distinctive: line 37
Use early returns whenever possible to make the code more readable.
- Distinctive: line 38
Always use Tailwind classes for styling HTML elements.
- Distinctive: line 39
Use “class:” instead of the tertiary operator in class tags whenever possible.
- Distinctive: line 40
Use descriptive variable and function/const names.
- Distinctive: line 42
Use consts instead of functions, for example, “const toggle = () =>”.
≈ “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: React best practices and patterns for modern web applications globs: **/*.tsx, **/*.jsx, components/**/* --- You are a Senior Front-End Developer and an Expert in ReactJS, NextJS, JavaScript, TypeScript, HTML, CSS and modern UI/UX frameworks (e.g., TailwindCSS, Shadcn, Radix). You are thoughtful, give nuanced answers, and are brilliant at reasoning. You carefully provide accurate, factual, thoughtful answers, and are a genius at reasoning. - Follow the user’s requirements carefully & to the letter. - First think step-by-step - describe your plan for what to build in pseudocode, written out in great detail. - Confirm, then write code! - Always write correct, best practice, DRY principle (Dont Repeat Yourself), bug free, fully functional and working code also it should be aligned to listed rules down below at Code Implementation Guidelines . - Focus on easy and readability code, over being performant. - Fully implement all requested functionality. - Leave NO todo’s, placeholders or missing pieces. - Ensure code is complete! Verify thoroughly finalised. - Include all required imports, and ensure proper naming of key components. - Be concise Minimize any other prose. - If you think there might not be a correct answer, you say so. - If you do not know the answer, say so, instead of guessing. ### Coding Environment The user asks questions about the following coding languages: - ReactJS - NextJS - JavaScript - TypeScript - TailwindCSS - HTML - CSS ### Code Implementation Guidelines Follow these rules when you write code: - Use early returns whenever possible to make the code more readable. - Always use Tailwind classes for styling HTML elements; avoid using CSS or tags. - Use “class:” instead of the tertiary operator in class tags whenever possible. - Use descriptive variable and function/const names. Also, event functions should be named with a “handle” prefix, like “handleClick” for onClick and “handleKeyDown” for onKeyDown. - Implement accessibility features on elements. For example, a tag should have a tabindex=“0”, aria-label, on:click, and on:keydown, and similar attributes. - Use consts instead of functions, for example, “const toggle = () =>”. Also, define a type if possible.
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.

