You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: .agents/AGENTS.md
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -25,9 +25,9 @@
25
25
- Parity: Don't reinvent the wheel. Before designing APIs or architecture, study how proven OSS projects solve the same problem — Drizzle (schema/ORM), tRPC (procedures/middleware), shadcn (CLI/codegen), better-auth (plugin system/auth). Adopt their patterns when applicable. Do `ls` in `..` directory to find the respective repositories, then inspect their source code when needed.
26
26
- DX: Optimize for the absolute best developer experience. CLI must be first-class for agents — deterministic, machine-readable output (--json), non-interactive defaults (--yes), composable commands. Every API surface should be intuitive for both humans and AI agents.
27
27
- Docs (www/): NEVER write changelog-style language ("has been removed", "new feature", "previously", "now supports"). Docs are user-facing reference for the LATEST state only. Write as if no prior version exists. No migration notes, no "what changed" — just document what IS. Follow docs/solutions/style.md for writing tone/structure.
28
-
- Docs sync: When updating www/ docs, also update the corresponding content in packages/kitcn/skills/convex/SKILL.md or packages/kitcn/skills/convex/references/ to stay synced. Follow packages/kitcn/skills/convex/references/setup/doc-guidelines.md for compression/placement rules.
29
-
- Plugins: ALWAYS read packages/kitcn/skills/convex/references/features/create-plugins.md before creating or modifying plugins. Keep it synced when any plugin API changes in the package.
30
-
- Intent maintainer loop: use `bunx intent scaffold` when you need new skills or a major skill reshuffle; for normal work, update docs and `packages/kitcn/skills/convex/**` in the same diff; run `bunx intent validate skills` and `bunx intent stale`; keep `@tanstack/intent`, `bin/intent.js`, `bin.intent`, and package `files` wired; verify with `npm pack --json --dry-run ./packages/kitcn`; after release, treat `intent feedback` as product input — tighten the skill if wording is wrong, fix the API if the same workaround keeps repeating.
28
+
- Docs sync: When updating www/ docs, also update the corresponding content in packages/kitcn/skills/kitcn/SKILL.md or packages/kitcn/skills/kitcn/references/ to stay synced. Follow packages/kitcn/skills/kitcn/references/setup/doc-guidelines.md for compression/placement rules.
29
+
- Plugins: ALWAYS read packages/kitcn/skills/kitcn/references/features/create-plugins.md before creating or modifying plugins. Keep it synced when any plugin API changes in the package.
30
+
- Intent maintainer loop: use `bunx intent scaffold` when you need new skills or a major skill reshuffle; for normal work, update docs and `packages/kitcn/skills/kitcn/**` in the same diff; run `bunx intent validate skills` and `bunx intent stale`; keep `@tanstack/intent`, `bin/intent.js`, `bin.intent`, and package `files` wired; verify with `npm pack --json --dry-run ./packages/kitcn`; after release, treat `intent feedback` as product input — tighten the skill if wording is wrong, fix the API if the same workaround keeps repeating.
31
31
- Always use @.agents/rules/changeset.mdc when updating packages to write a changeset before completing
32
32
- After any package modification, run `bun --cwd packages/kitcn build`
33
33
- Use tdd skill for package updates that add or change live behavior.
Dig into /tmp/cc-repos/drizzle-v1 for Drizzle v1 and /tmp/cc-repos/drizzle-orm-docs for Drizzle ORM docs - it's the latest version of Drizzle.
2
2
Make sure we maximize mirroring drizzle-v1 - dont forget all ts answers are in drizzle repo, dig into it when needed. they master more typescript than you. drizzle has many db integrations so just pick the most relevant one - making sure we mirror all typing magic - dig into /tmp/cc-repos/convex-backend if you need to dig into convex typing, testing or src code. We also have /tmp/cc-repos/convex-ents if needed. Any "new features" not part of drizzle-v1 should feel like an extension of drizzle parity. Not "separate helpers". If you need to read convex docs, see /tmp/cc-repos/convex-backend/npm-packages/docs/docs.
3
-
SAME for testing / type testing - but when you need to test convex part, see `.claude/skills/convex/references/testing.md` or convex-backend/npm-packages tests. Use tdd skill `.agents/skills/tdd/SKILL.md` when relevant. We don't want to reinvent the wheel, but we want the closest API to Drizzle. At the end of each package change, make sure you didn't break the types: `bun typecheck` at root and `bun run test` at root.
3
+
SAME for testing / type testing - but when you need to test convex part, see `.claude/skills/kitcn/references/testing.md` or convex-backend/npm-packages tests. Use tdd skill `.agents/skills/tdd/SKILL.md` when relevant. We don't want to reinvent the wheel, but we want the closest API to Drizzle. At the end of each package change, make sure you didn't break the types: `bun typecheck` at root and `bun run test` at root.
0 commit comments