coding-standards

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

Updated Mar 26, 2026
One-click install
npx skills add https://github.com/inuishan/PET --skill coding-standards-inuishan
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: coding-standards
Source: https://github.com/inuishan/PET/tree/main/.codex/skills/coding-standards
Command: npx skills add https://github.com/inuishan/PET --skill coding-standards-inuishan

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Inconsistent code style, missing error handling, and weak type safety slow down reviews and introduce bugs. This Skill provides a single reference of universal coding standards so teams write readable, maintainable TypeScript, JavaScript, React, and Node.js code. ## Core Features & Use Cases - Code Quality Principles: Applies readability-first, KISS, DRY, and YAGNI rules with concrete good/bad examples. - Language & Framework Standards: Covers naming, immutability, async/await, type safety, React components, hooks, state management, and conditional rendering. - API & Project Conventions: Defines REST endpoint patterns, consistent response formats, Zod input validation, file organization, and testing standards. - Use Case: When reviewing a pull request, activate this Skill to check for direct state mutation, missing error handling, deep nesting, and magic numbers before approving. ## Quick Start Review this TypeScript module against the coding standards and flag any immutability, error handling, or type safety violations.

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 documented conventions for naming, immutability, error handling, and type safety during code reviews and refactoring. The standards include concrete good and bad examples for variables, functions, async code, and interfaces.

What are React best practices for components and hooks?▼

Use functional components with typed props, extract reusable logic into custom hooks like useDebounce, and update state with functional updates. Avoid untyped props and nested ternary conditional rendering.

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

Use Zod schemas to parse and validate incoming JSON bodies before processing. Return a consistent error response with status 400 and validation details when parsing fails.

Does this cover REST API design conventions?▼

Yes, it defines standard REST endpoint patterns for list, get, create, update, and delete operations, plus query parameter filtering and a consistent ApiResponse structure with success, data, error, and meta fields.

What code smells should I watch for during review?▼

Watch for functions longer than 50 lines, nesting deeper than a few levels, and unexplained magic numbers. Fix them by splitting functions, using early returns, and replacing literals with named constants.