viberepo: Cursor rule for Cursor

Project Rules for viberepo

Generated by VibeRepo — https://github.com/user/viberepo

Stack: Node.js | Language: typescript | ORM: none

Project Context

You are working on "viberepo", a Node.js application. Always read PROJECT_MAP.md first to understand the full project structure. Always read llms.txt for a quick overview of the codebase.

Architecture Rules

• Follow the existing file structure and naming conventions.
• Keep files focused and single-responsibility.
• Do NOT create files outside the established directory structure without asking.
• When creating new features, follow the patterns established in existing code.

General Rules

• Follow the conventions established in the existing codebase.
• Prefer clarity over cleverness.

Code Quality

• Write strict TypeScript — never use any. Use unknown with type guards instead.
• Handle all error cases explicitly. Never swallow errors silently.
• Write pure functions when possible. Minimize side effects.
• Add JSDoc comments for all public functions and complex logic.
• Keep functions small (<30 lines). Extract when complexity grows.

Testing

• Every new feature must include tests.
• Test behavior, not implementation details.
• Use descriptive test names: "should [expected behavior] when [condition]".

Git Discipline

• Make atomic commits — one logical change per commit.
• Use conventional commits: feat:, fix:, refactor:, docs:, test:, chore:.
• Never commit console.log, debugger, or TODO without a tracking issue.

Context Management

• Do NOT read node_modules, dist, build, .next, or coverage directories.
• Reference docs/ai-context/ for architecture and conventions.
• After making structural changes, remind the user to run viberepo sync.