instantdb-to-supabase
AGENTS.md1 starsChanged 10 days agoApache-2.0View on GitHub
Standalone Next.js app and Workflow importer. Requires Node 24 and pnpm 11. Run pnpm dev (port 3009), pnpm test, pnpm typecheck, pnpm lint, and pnpm build. Run pnpm test:db (pgTAP, needs supabase start in the repository root) after changing supabase/migrations. Integration and browser checks are described in README.md. Use pnpm run import for the operator CLI (pnpm import alone is a package-manager command).
Where files are headingNew AGENTS.md files have more rules about keeping secrets out of the code, and fewer about code style.
Of the AGENTS.md files we read, the 31,439 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 repositoryOne other file it gives its agents.
- CLAUDE.mdCLAUDE.md
The file
We split this AGENTS.md into the rules it gives an agent
2 rules. About 0 are common, 2 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
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 7
Keep SQL composed with safeSql, ident, and literal from the vendored @supabase/pg-meta helpers.
- Distinctive: line 11
Use named exports except framework entry points.
≈ “Common” is an estimate: at least 1 in 5 of the 40,246 AGENTS.md 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
InstantDB to Supabase
Standalone Next.js app and Workflow importer. Requires Node 24 and pnpm 11.
Run pnpm dev (port 3009), pnpm test, pnpm typecheck, pnpm lint, and pnpm build. Run pnpm test:db (pgTAP, needs supabase start in the repository root) after changing supabase/migrations. Integration and browser checks are described in README.md. Use pnpm run import for the operator CLI (pnpm import alone is a package-manager command).
- Keep SQL composed with safeSql, ident, and literal from the vendored @supabase/pg-meta helpers. Never replace these with unchecked string interpolation.
- Credentials, source rows, and file bytes must never enter Workflow arguments/results, browser telemetry, or logs.
- Workflow bodies must be deterministic; perform I/O and read clocks only inside steps.
- Generated RLS must never be more permissive than the source. Leave ambiguous rules closed and include them in the handoff.
- Use named exports except framework entry points. Preserve the Supabase components and semantic Tailwind tokens; use U.S. English.
- vendor/ is a pinned upstream snapshot. Run pnpm vendor:check to verify it. Update with the documented sync command and review upstream changes and dependencies. Do not format or casually edit vendored files.
- supabase/ is the private service project. Change its schema only by adding a new file to supabase/migrations; never add runtime DDL or edit applied migrations.
- Environment files, uploaded backups, workflow data, and build output must never be committed.
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.