Cursor Rules & AGENTS.md Generator

PROJECT — AI ASSISTANT RULES


TECH STACK
- Language: TypeScript
- Framework: Next.js
- Package manager: pnpm (always use pnpm, never mix package managers)
- Testing: Vitest

CODE STYLE
- Write strict, fully-typed code. Do not use `any` — use `unknown` with narrowing or define a proper type.
- Prefer pure functions and a functional style over classes where practical.
- Use named exports. Avoid default exports.
- Use descriptive, intention-revealing names. No single-letter variables except loop indices.
- Keep functions small and single-purpose. Extract logic rather than nesting deeply.
- Use early returns / guard clauses instead of deep if/else nesting.
- Use async/await. Avoid raw .then() chains and callback-style code.
- Comment the non-obvious WHY, not the WHAT. Skip comments that just restate code.

CORRECTNESS & SAFETY
- Handle errors explicitly at system boundaries (user input, network, file I/O). Do not swallow errors silently.
- Do not invent APIs, packages or file paths. If unsure, check the codebase first.
- Match existing patterns and conventions in the surrounding code.
- Do not introduce new dependencies without a clear reason.
- Remove debug `console.log` / `print` statements before finishing.
- Write accessible markup: semantic HTML, alt text, labels, keyboard support.

TESTING
- Add or update Vitest tests for any new behavior or bug fix.
- Cover the golden path plus the obvious edge cases. Do not test framework internals.

GIT & COMMITS
- Use Conventional Commits (feat:, fix:, chore:, docs:, refactor:, test:).
- Keep commits focused and atomic. Write the WHY in the body, not just the WHAT.

WORKFLOW
- When asked to change this project, make the minimal change that fully solves the task.
- Do not refactor unrelated code, add speculative features, or leave half-finished work.
- After a change, ensure the project still builds and existing tests pass.

Save as .cursorrules in your project root.