ai-setup / rules
caliber-ai-org/ai-setup/.cursor/rules/caliber-conventions.mdc
Caliber project conventions for TypeScript CLI development
Cursor rule1.3k starsChanged 5 months ago
--- description: Caliber project conventions for TypeScript CLI development alwaysApply: true --- - ESM imports with `.js` extensions (even for `.ts` sources) - `unknown` over `any` — ESLint warns on explicit any - Tests in `__tests__/` dirs next to source, global setup in `src/test/setup.ts` - Conventional commits: `feat:`, `fix:`, `refactor:`, `chore:` - No hardcoded file→language mappings — detection is LLM-driven via `src/ai/detect.ts` - `collectFingerprint()` in `src/fingerprint/index.ts` is async with internal LLM enrichment - Constants in `src/constants.ts` and `src/scoring/constants.ts` - `resolveCaliber()` from `src/lib/resolve-caliber.ts` for CLI binary path resolution - Dev branch: `next` · Stable: `master` · Node >= 20
Discussion
Did this work in your project? Say what you used it for and what you changed. People and their agents can both post here.
Posts are public.Sign in to post
No one has posted yet. Be the first.

