coding-standards

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

Updated May 9, 2026
One-click install
npx skills add https://github.com/kk20300113-png/my-claude-skills --skill coding-standards-kk20300113-png
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: coding-standards
Source: https://github.com/kk20300113-png/my-claude-skills/tree/main/coding-standards
Command: npx skills add https://github.com/kk20300113-png/my-claude-skills --skill coding-standards-kk20300113-png

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill eliminates the frustration of inconsistent code quality, hard-to-maintain codebases, and slow onboarding for TypeScript, JavaScript, React, and Node.js development teams by providing clear, actionable coding standards and best practices.

Core Features & Use Cases

  • Universal Coding Standards: Consistent rules for variable and function naming, formatting, and file organization across all supported languages and frameworks.
  • Best Practice Guidance: Concrete do's and don'ts for immutability, error handling, async patterns, React component structure, state management, API design, and performance optimization.
  • Code Quality Enforcement: Built-in guidance for detecting code smells like long functions, deep nesting, and magic numbers, plus standards for test structure and documentation.
  • Use Case: Use this Skill when setting up a new Next.js project to establish consistent component and file naming conventions, or during code reviews to catch anti-patterns like direct state mutation.

Quick Start

Use the coding-standards skill to review your latest React component code for adherence to immutability rules and proper prop typing.

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 TypeScript and React coding standards?

TypeScript and React coding standards enforce consistent variable naming, immutability, proper prop typing, and file organization to eliminate maintainability issues and improve code review workflows across development teams.

How do I set up coding standards for a new Node.js project?

Set up Node.js coding standards by configuring linting and formatting rules, establishing API design guidelines, and defining error handling patterns to ensure consistent code quality from project initialization.

How do I review React component code for anti-patterns and direct state mutation?

Review React component code by checking for adherence to immutability rules, proper prop typing, and detecting code smells like deep nesting or magic numbers during the standard code review workflow.

Does this coding standards guidance work for contributor onboarding workflows?

Yes, coding standards guidance applies directly to contributor onboarding by providing actionable rules for variable naming, file organization, and test structure to accelerate new developer integration into TypeScript and React codebases.

What are the limitations of enforcing universal coding standards across JavaScript frameworks?

Enforcing universal coding standards requires configuring framework-specific patterns like React component structure and Node.js async error handling separately, as general rules do not automatically adapt to specialized framework conventions.