coding-standards

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

2|Updated Feb 25, 2026
One-click install
npx skills add https://github.com/adamreger/ecc-antigravity --skill coding-standards-adamreger
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: coding-standards
Source: https://github.com/adamreger/ecc-antigravity/tree/main/skills/coding-standards
Command: npx skills add https://github.com/adamreger/ecc-antigravity --skill coding-standards-adamreger

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Inconsistent code style, weak error handling, and poor structure slow down reviews and create technical debt. This Skill provides a single reference of conventions so every module follows the same naming, typing, testing, and API design rules. ## Core Features & Use Cases - Language Standards: Naming, immutability, async/await, and type-safety rules for TypeScript and JavaScript with good/bad code examples. - React & API Conventions: Component structure, custom hooks, state updates, REST endpoint design, response formats, and Zod-based input validation. - Quality Guardrails: Testing patterns (AAA structure), code smell detection (long functions, deep nesting, magic numbers), and performance practices like memoization and lazy loading. - Use Case: When reviewing a pull request or scaffolding a new Next.js module, activate this Skill to check the code against consistent conventions before merging. ## Quick Start Review this TypeScript file against the coding standards and point out violations in naming, error handling, and type safety.

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 consistent naming conventions, immutability with spread operators, proper error handling, and strict typing instead of any. Activate this Skill during code reviews or refactoring to check code against these documented rules with concrete examples.

What are React best practices for components and hooks?▼

Use typed functional components with explicit props interfaces, extract reusable logic into custom hooks like useDebounce, and update state with functional setters. Memoize expensive computations with useMemo and callbacks with useCallback.

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

Use Zod schemas to define expected shapes with constraints like string lengths and datetime formats, then parse incoming bodies in route handlers. Return a 400 response with structured error details when validation fails.

Does this cover async/await error handling patterns?▼

Yes, it documents try/catch wrapping with HTTP status checks, parallel execution with Promise.all for independent calls, and rethrowing descriptive errors. It also shows anti-patterns like unhandled fetch calls to avoid.

What code smells should I watch for during review?▼

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