coding-standards

Enforce coding standards and best practices for TypeScript, JavaScript, React, and Node.js.

Updated Feb 10, 2026
One-click install
npx skills add https://github.com/ihj04982/my-cursor-settings --skill coding-standards-ihj04982
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: coding-standards
Source: https://github.com/ihj04982/my-cursor-settings/tree/main/skills/coding-standards
Command: npx skills add https://github.com/ihj04982/my-cursor-settings --skill coding-standards-ihj04982

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill provides a comprehensive set of universal coding standards, best practices, and common patterns for TypeScript, JavaScript, React, and Node.js development, ensuring code readability, maintainability, and efficiency.

Core Features & Use Cases

  • Code Quality Principles: Enforces readability, simplicity (KISS), don't repeat yourself (DRY), and you ain't gonna need it (YAGNI).
  • Language-Specific Standards: Detailed guidelines for variable/function naming, immutability, error handling, async/await, and type safety in TypeScript/JavaScript.
  • Framework Best Practices: Recommendations for React component structure, custom hooks, state management, and conditional rendering.
  • API Design: Standards for RESTful API conventions, consistent response formats, and input validation using tools like Zod.
  • File Organization & Naming: Guidelines for project structure and file naming conventions.
  • Testing & Documentation: Best practices for test structure (AAA), naming, and JSDoc comments.
  • Performance & Security: Tips on memoization, lazy loading, efficient database queries, and code smell detection.
  • Quick Checklist: A handy checklist for developers to ensure adherence to standards before completing work.
  • Common Patterns: Introduces patterns like the Repository Pattern and guidance on using skeleton projects.

Quick Start

Review the coding standards for TypeScript and React development.

Frequently Asked Questions about coding-standards

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
What are the best practices for React component structure and state management?

React component structure best practices include organizing custom hooks, managing state efficiently, and using conditional rendering. These framework guidelines improve code readability, maintainability, and efficiency across your React development projects.

How do I enforce TypeScript coding standards for type safety and error handling?

TypeScript coding standards enforce type safety, error handling, async/await, and immutability. Implementing these language-specific guidelines ensures consistent variable and function naming, ultimately improving your JavaScript and TypeScript project maintainability.

What's the best way to design RESTful API conventions in Node.js?

Designing RESTful API conventions in Node.js requires consistent response formats and input validation. Using schema validation tools like Zod enforces API design standards, ensuring robust, maintainable, and efficient backend endpoints.

How do I structure test files and documentation for JavaScript projects?

Structure JavaScript test files using the Arrange-Act-Assert (AAA) pattern and clear naming conventions. Complement this with JSDoc comments for documentation to ensure code readability and maintainability across your project.

Can I use the Repository Pattern for file organization in Node.js?

The Repository Pattern is recommended for Node.js architectural organization. Alongside skeleton projects, it separates data access logic, complementing file naming conventions and project structure guidelines to improve overall code maintainability.

Why should I apply KISS and DRY principles to React and Node.js development?

Applying KISS, DRY, and YAGNI principles to React and Node.js development reduces code smells and enforces simplicity. These code quality standards prevent unnecessary complexity, ensuring readable, efficient, and maintainable software.