coding-standards

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

1|Updated Oct 11, 2025
One-click install
npx skills add https://github.com/ibytechaos/claude --skill coding-standards-ibytechaos
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: coding-standards
Source: https://github.com/ibytechaos/claude/tree/main/plugins/everything-claude-code/skills/coding-standards
Command: npx skills add https://github.com/ibytechaos/claude --skill coding-standards-ibytechaos

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Inconsistent naming, mutation bugs, missing error handling, and unclear structure slow down teams and introduce defects. This Skill provides a single reference of universal coding standards so code reviews, refactors, and new modules follow the same conventions. ## Core Features & Use Cases - TypeScript/JavaScript Standards: Naming conventions, immutability patterns, error handling, async/await parallelism, and type safety rules with good/bad examples. - React Best Practices: Typed functional components, custom hooks, state updates, conditional rendering, memoization, and lazy loading patterns. - API & Project Conventions: REST endpoint design, consistent response schemas, Zod input validation, file organization, and testing standards (AAA pattern). - Use Case: When reviewing a pull request, activate this Skill to check the diff against immutability rules, early-return patterns, magic-number detection, and descriptive test naming. ## Quick Start Review this TypeScript module against the coding standards and list any violations with suggested fixes.

Frequently Asked Questions about coding-standards

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

FAQPage Schema
How do I enforce coding standards in a TypeScript project?

Apply the conventions in this Skill during code reviews and refactoring: descriptive naming, immutability via spread operators, typed function signatures, and comprehensive error handling. Pair with linting and type-checking tools for automated enforcement.

What are React best practices for functional components?

Define a typed props interface, use destructured parameters with defaults, and keep components small. Use custom hooks for reusable logic, functional state updates, memoization with useMemo and useCallback, and lazy loading for heavy components.

How should I validate API request bodies in Node.js?

Use Zod schemas to define expected shapes, then parse incoming JSON in the route handler. On ZodError, return a 400 response with a consistent error structure including validation details.

Why should I avoid mutating objects and arrays directly?

Direct mutation breaks React change detection and causes stale-state bugs. Use the spread operator to create updated copies, such as {...user, name: 'New Name'} or [...items, newItem], keeping updates predictable and traceable.

When should I not add comments to code?

Avoid comments that restate what the code obviously does, like 'increment counter'. Reserve comments for explaining why a decision was made, such as performance trade-offs or non-obvious workarounds, and use JSDoc for public APIs.