quests / rules
Cursor rule464 starsChanged 10 months agoApache-2.0View on GitHub
Rules for the Studio.
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,144 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 repository7 other files it gives its agents.
- .cursor/rules/general.mdcCursor rule
- .cursor/rules/react.mdcCursor rule
- .cursor/rules/tests.mdcCursor rule
- .cursor/rules/typescript.mdcCursor rule
- .cursor/rules/workspace.mdcCursor rule
- changelogSkill
- pre-push-reviewSkill
The file
We split this studio-client.mdc into the rules it gives an agent
2 rules. About 0 are common, 0 are distinctive, and 2 are 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.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 12
Use shadcn Tailwind colors (e.g.
- Very specific: line 16
Use the cn helper from @/client/lib/utils for conditional or composed Tailwind classes.
≈ “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: Rules for the Studio.
globs: apps/studio/**/*
alwaysApply: true
---
## Project
Studio is an Electron app. The renderer is a React 19 app using TanStack Router (file-based routes), shadcn UI components, and oRPC to talk to the main process. The main process also calls a remote API (accounts, plans, Stripe); that is only exposed to the UI via main-process RPC, not by the client calling HTTP directly.
- React 19: use the newer APIs. Because we behave as a desktop app, we don't use `cursor: pointer` for links.
- Use shadcn Tailwind colors (e.g. `bg-background`), not raw colors like `bg-white`.
- `rpcClient` methods can be called with `.call()` but will throw unless wrapped in `import { safe } from "@orpc/client";`. Use `.call()` when imperative outside React.
- Queries: `useQuery` and `rpcClient.method.name.queryOptions({ input: { ... } })`. To conditionally skip, pass `skipToken` as `input`: `rpcClient.foo.queryOptions({ input: value ?? skipToken })`.
- External links: `<ExternalLink href="..." />` or `rpcClient.utils.openExternalLink`.
- Use the `cn` helper from `@/client/lib/utils` for conditional or composed Tailwind classes.
- For types derived from RPC calls, always use `RPCInput` / `RPCOutput` from `@/client/rpc/client` (e.g. `RPCOutput["workspace"]["project"]["list"]`). Never manually redeclare types that can be inferred this way.
## Where things are
- **Client app**: Renderer code under `src/client`. Routes are file-based in `src/client/routes/` (TanStack Router; layout/auth under `_app/`).
- **UI**: shadcn in `src/client/components/ui`; shared components in `src/client/components/`.
- **Debug**: Routes under `_app/debug/` and `settings/debug` are for experimentation only; not for end users.
- **RPC**: Main process handlers in `src/electron-main/rpc/routes/`; workspace at `rpcClient.workspace.*`. Client in `src/client/rpc/client.ts` talks to main over MessageChannel only (no direct remote HTTP).
- **Remote API**: Main process only, in `src/electron-main/api/`. UI gets that data via main-process RPC (e.g. `user.me`, `plans.get`).
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.