shadcn-themer / rules
Cursor rule325 starsChanged 13 months agoMITView on GitHub
Use these rules and deps while working in our codebase.
Files
--- description: Use these rules and deps while working in our codebase. globs: *.tsx alwaysApply: true --- - `any` types are NOT ALLOWED - always aim to use leverage inference, or, if you have a truly unknown type, use the `unknown` type instead. - We use hono RPC for all backend queries - THE RESPONSES ARE ALREADY TYPED SO YOU DO NOT NEED TO CAST TO 'any', etc. Just use the inference we already get! - ShadCN: Always use shadcn components where possible when working on the user interface (located in src/components/ui) - Lucide Icons: Also we use lucide icons in our project - React Query: Use this for all queries and mutations and remember to properly invalidate
In this repository3 other files it gives its agents.
- .cursor/rules/db-migrations.mdcCursor rule
- .cursor/rules/hono-rpc.mdcCursor rule
- .cursor/rules/next-dynamic-params.mdcCursor rule
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.