Cursor Rules
ai agent specialist - Claude MCP Skill
You are a senior full-stack developer specializing in TypeScript, React, and Node.js.
SEO Guide: Enhance your AI agent with the ai agent specialist tool. This Model Context Protocol (MCP) server allows Claude Desktop and other LLMs to you are a senior full-stack developer specializing in typescript, react, and node.js.... Download and configure this skill to unlock new capabilities for your AI workflow.
Documentation
SKILL.mdYou 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. > WHY: Lighter weight, better TypeScript support, less boilerplate. ## Error Handling - Custom AppError hierarchy with HTTP status codes. Throw for exceptional, return Result for expected failures. > WHY: Clear intent — callers know which errors to catch vs handle. - Structured logging with Winston. Never log sensitive data (passwords, tokens, PII). > WHY: Observability without security risk. Structured logs enable alerting. ## Testing - 80% unit coverage, 100% critical paths. Use factory functions for test data. > WHY: Factory functions are maintainable and composable. Fixtures become stale. - Mock only external dependencies (APIs, DB). Never mock internal logic. > WHY: Tests should reflect reality. Over-mocking hides real bugs. ## Security - Validate all input with Zod schemas at API boundaries. > WHY: Runtime validation catches what TypeScript can't — malformed external data. - Rate limit all public endpoints. Use helmet middleware. > WHY: Defense in depth against abuse and common web vulnerabilities. ## Git - Max 400 lines per PR. Conventional commits: feat/fix/refactor/test/docs. > WHY: Small PRs get reviewed faster and have fewer bugs.
Signals
Information
- Repository
- PatrickJS/awesome-cursorrules
- Author
- PatrickJS
- Last Sync
- 5/12/2026
- Repo Updated
- 5/12/2026
- Created
- 5/12/2026
Reviews (0)
No reviews yet. Be the first to review this skill!
Related Skills
upgrade-nodejs
Upgrading Bun's Self-Reported Node.js Version
cursorrules
CrewAI Development Rules
README
Agents — Working Implementations
cn-check
Install and run the Continue CLI (`cn`) to execute AI agent checks on local code changes. Use when asked to "run checks", "lint with AI", "review my changes with cn", or set up Continue CI locally.
Related Guides
Bear Notes Claude Skill: Your AI-Powered Note-Taking Assistant
Learn how to use the bear-notes Claude skill. Complete guide with installation instructions and examples.
OpenAI Whisper API Claude Skill: Complete Guide to AI-Powered Audio Transcription
Learn how to use the openai-whisper-api Claude skill. Complete guide with installation instructions and examples.
Mastering the Oracle CLI: A Complete Guide to the Claude Skill for Database Professionals
Learn how to use the oracle Claude skill. Complete guide with installation instructions and examples.