coding-standards

Enforce cross-project JavaScript and TypeScript coding conventions for reviews and refactoring.

1|Updated Apr 9, 2026

Search Tags:#typescript #react #readability #standards #coding #code-quality #immutability

Ready to run

npx skills add https://github.com/hbvg234/jnmt.vn --skill coding-standards-hbvg234

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: coding-standards
Source: https://github.com/hbvg234/jnmt.vn/tree/main/.claude/skills/coding-standards
Command: npx skills add https://github.com/hbvg234/jnmt.vn --skill coding-standards-hbvg234

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Baseline coding conventions applicable across projects to improve readability, maintainability, and consistency, serving as the shared floor rather than a framework-specific playbook.

Core Features & Use Cases

Establishes readability-first principles, naming guidelines, and formatting rules.
Defines immutability practices, error-handling expectations, and DRY/KISS guidance.
Provides guidance across TypeScript/JavaScript, React, and API design to align teams during onboarding, code reviews, and refactoring.

Quick Start

Apply these baseline conventions to the next coding task by enforcing descriptive naming, immutability, and consistent formatting from the outset.

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 across TypeScript and React projects?▼

To enforce coding standards across TypeScript and React projects, apply baseline conventions for naming, immutability, and formatting to align teams during onboarding, code reviews, and refactoring without framework-specific biases.

What are the best practices for immutability and error handling in JavaScript?▼

Best practices for immutability and error handling in JavaScript involve applying readability-first principles, defining immutability practices, and setting clear error-handling expectations to ensure maintainable and consistent code.

How do I establish naming conventions and formatting rules for code reviews?▼

To establish naming conventions and formatting rules for code reviews, enforce cross-project coding guidelines that prioritize readability, DRY/KISS principles, and consistent formatting across frontend and backend JavaScript environments.

Does this coding standards guide work for both frontend and backend development?▼

Yes, this coding standards guide works for both frontend and backend development by providing universal guidelines for TypeScript, JavaScript, React, and API design without relying on framework-specific playbooks.

Why should I use universal coding conventions instead of framework-specific playbooks?▼

You should use universal coding conventions instead of framework-specific playbooks to establish a shared baseline of readability, maintainability, and consistency that applies seamlessly across diverse projects and team onboarding processes.