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/erwinv2k-TKG/AgentesVSC --skill coding-standards-erwinv2k-tkg
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: coding-standards
Source: https://github.com/erwinv2k-TKG/AgentesVSC/tree/main/packs/everything-claude-code/docs/zh-TW/skills/coding-standards
Command: npx skills add https://github.com/erwinv2k-TKG/AgentesVSC --skill coding-standards-erwinv2k-tkg

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Inconsistent code style, weak error handling, and poor naming conventions slow down code reviews and introduce bugs. This Skill provides a single reference of universal coding standards so every generated or reviewed snippet follows the same quality rules. ## Core Features & Use Cases - Language Standards: Naming, immutability, error handling, async/await, and type-safety rules for TypeScript and JavaScript. - React & API Guidelines: Component structure, custom hooks, state management, REST conventions, response formats, and Zod-based input validation. - Quality Checks: Code smell detection (long functions, deep nesting, magic numbers), testing standards (AAA pattern), and performance practices like memoization and lazy loading. - Use Case: When asking an AI to write a new React component or review a pull request, the Skill ensures the output uses typed props, proper error handling, and consistent file organization. ## Quick Start Apply the coding-standards skill to review this TypeScript file and rewrite any code that violates the naming, immutability, or error-handling rules.

Frequently Asked Questions about coding-standards

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

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

Apply consistent rules for naming, immutability, type safety, and error handling across all files. This Skill defines verb-noun function naming, spread-based immutable updates, typed interfaces instead of any, and try-catch patterns for async operations.

What are React best practices for component structure?

Use typed function components with explicit props interfaces, default parameter values, and custom hooks for reusable logic. Memoize expensive computations with useMemo and callbacks with useCallback, and lazy-load heavy components with Suspense.

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

Use Zod schemas to define expected input shapes and parse incoming request bodies before processing. Return a consistent error response with status 400 and validation details when parsing fails.

Does this standard work with Next.js projects?

Yes, the file organization section explicitly covers Next.js App Router structure, including API routes, route groups, and separation of components, hooks, lib utilities, and types directories.

What code smells should I avoid in JavaScript functions?

Avoid functions over 50 lines, nesting deeper than a few levels, and unexplained magic numbers. Split long functions into smaller units, use early returns instead of deep nesting, and replace literals with named constants.