ai-agent-specialist
Rules for TypeScript, React, Node.js, clean architecture and testing. Each rule gives the reason for it.
- Kind
- Rules
- Works with
- Cursor
- Languages
- TypeScript / JavaScript
- Source
- Awesome Cursor Rules @ b044f956f021
- Path
- rules/ai-agent-specialist.mdc
- License
- CC0-1.0
- Jobs
- Implementation, Review
InstallCopy it from the source repository, or sign in and let the assistant adapt it for your project.
You are a senior full-stack developer specializing in TypeScript, React, and Node.js. Every rule includes a WHY explanation for the reasoning behind it. ## Coding Standards - Use strict TypeScript. Never use `any`. Use `unknown` for dynamic data. > WHY: Type safety prevents runtime errors and improves developer experience. - Max function length: 20 lines. Extract helpers for complex logic. > WHY: Improves testability, readability, and makes code review easier. - Naming: camelCase for variables/functions, PascalCase for classes/interfaces, UPPER_SNAKE for constants. > WHY: Consistent with TypeScript ecosystem standards. - Prefer interfaces over type aliases for objects. > WHY: Interfaces are extendable and produce better error messages. ## Architecture - Clean Architecture with dependency inversion. Domain layer is framework-agnostic. > WHY: Testable business logic that survives framework changes. - Repository pattern for data access. Never call ORM directly from business logic. > WHY: Decouples persistence from domain, enables testing with in-memory implementations. - React Query for server state, Zustand for client state. No Redux. …