groundwork / rules
Cursor rule0 starsChanged 50 days agoMITView on GitHub
Drizzle schema and migration rules (packages/db)
In this repository15 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- .github/copilot-instructions.mdCopilot instructions
- .cursor/rules/000-project.mdcCursor rule
- .cursor/rules/010-typescript.mdcCursor rule
- .cursor/rules/020-api.mdcCursor rule
- .cursor/rules/030-web.mdcCursor rule
- .cursor/rules/050-worker.mdcCursor rule
- .cursor/rules/060-testing.mdcCursor rule
- llms.txtllms.txt
- add-endpointSkill
- db-migrationSkill
- new-moduleSkill
- verifySkill
- write-testsSkill
The file
Files
--- description: Drizzle schema and migration rules (packages/db) globs: ['packages/db/**'] alwaysApply: false --- See `packages/db/AGENTS.md`. Every schema change ships with `pnpm db:generate --name <descriptive_name>`. Never edit an applied migration. `timestamptz` everywhere, explicit `onDelete`, index foreign keys, secrets encrypted, tokens hashed.
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.