quests / rules
Cursor rule464 starsChanged 10 months agoApache-2.0View on GitHub
Rules for the workspace package (agents, tools, RPC, runtime).
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/studio-client.mdcCursor rule
- .cursor/rules/tests.mdcCursor rule
- .cursor/rules/typescript.mdcCursor rule
- changelogSkill
- pre-push-reviewSkill
The file
We split this workspace.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 18
Prefer neverthrow Result for fallible operations.
≈ “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 workspace package (agents, tools, RPC, runtime). globs: packages/workspace/**/* alwaysApply: true --- ## Structure - **RPC**: Router in `src/rpc/index.ts` (app, message, project, registry, runtime, session). Handlers in `src/rpc/routes/`. Base and `toORPCError` in `src/rpc/base.ts`. Exposed to Studio as `workspaceRouter` via `@quests/workspace/electron`. - **Tools**: `src/tools/`. Each tool is built with `setupTool()` from `create-tool.ts`; register in `all.ts`. Use neverthrow `Result` for fallible tool logic; map to tool output or throw for oRPC. - **Agents**: `src/agents/`. `main` and `retrieval` in `all.ts`. Main agent runs the session; tools are selected per agent in `create-agent.ts`. - **Workspace server**: Hono app in `src/logic/server/index.ts`. Serves shim script/iframe, assets, heartbeat, redirect, and proxies app traffic. AI gateway is mounted at `AI_GATEWAY_API_PATH` when provided. - **Schemas**: `src/schemas/` (paths, subdomains, store-id, session, app-state, file-upload, etc.). Use these for RPC and tool I/O where applicable. - **Machines**: XState in `src/machines/` (workspace, session, agent). `WorkspaceActorRef` is the main process handle; RPC context gets `workspaceRef` and `workspaceConfig`. ## Conventions - Prefer neverthrow `Result` for fallible operations; use `toORPCError` when throwing from RPC handlers. - Tools use Zod input/output schemas and the shared `create-tool` / `setupTool` pattern.
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.