coding-standards

Codify TypeScript, JavaScript, React, and Node.js coding standards for team workflows.

3|1|Updated Jan 24, 2026
One-click install
npx skills add https://github.com/monch1962/everything-opencode --skill coding-standards-monch1962
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: coding-standards
Source: https://github.com/monch1962/everything-opencode/tree/main/skills/coding-standards
Command: npx skills add https://github.com/monch1962/everything-opencode --skill coding-standards-monch1962

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill codifies universal coding standards for TypeScript, JavaScript, React, and Node.js development, helping teams avoid inconsistent code and reduce review time.

Core Features & Use Cases

  • Consistent naming conventions, code formatting, and self-documenting patterns across the codebase.
  • Immutability and safe state management principles to minimize bugs.
  • Clear error handling, testing-ready patterns, and React component best practices for scalable apps.
  • Use Case: A new team onboarding a large TS/React project can adopt these standards to align across frontend and backend modules.

Quick Start

Start by integrating the guidelines into your lint rules (e.g., ESLint/TypeScript tooling), adopting the formatting and naming conventions in code reviews, and progressively refactoring existing modules to align with the standards.

Frequently Asked Questions about coding-standards

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

FAQPage Schema
How do I standardize code quality across a TypeScript and React project?

Standardize code quality by codifying universal coding standards for TypeScript, JavaScript, React, and Node.js that enforce immutability, explicit naming, consistent error handling, and React patterns. Integrate these guidelines into ESLint and TypeScript tooling, apply them during code reviews, and progressively refactor existing modules to align with the standards.

What naming conventions and formatting rules should a JavaScript team adopt?

Adopt consistent naming conventions, code formatting, and self-documenting patterns across your codebase to improve readability and reduce review time. This Skill provides defined guidelines and example snippets for TypeScript, JavaScript, React, and Node.js that teams can integrate into lint rules and apply across frontend and backend modules.

How do immutability principles reduce bugs in React state management?

Immutability and safe state management principles minimize bugs by preventing unintended state mutations. This Skill codifies immutability patterns for React development alongside explicit naming and structured error handling to create more reliable and maintainable applications.

Can I use these coding standards during code reviews?

Yes. These coding standards are designed specifically for team code reviews and baseline project setups. They provide explicit guidelines for React patterns, error handling, API design, and naming conventions that reviewers can reference to ensure consistency and reduce review time across frontend and backend projects.

What's the best way to onboard a large team to coding standards?

A new team can adopt these standards by integrating guidelines into ESLint and TypeScript tooling first, then applying formatting and naming conventions during code reviews, and progressively refactoring existing modules. This approach aligns the team across frontend and backend while maintaining workflow continuity.

Do these standards include error handling and testing patterns?

Yes. This Skill codifies clear error handling, testing-ready patterns, and React component best practices alongside immutability, naming, and formatting conventions. These patterns create scalable applications ready for consistent testing and maintainability across your codebase.