coding-standards

Enforce naming, immutability, and structural conventions across TypeScript, React, and REST APIs.

Updated Jul 8, 2026
One-click install
npx skills add https://github.com/nazrulsoftwaredev/NIT_CRM_2 --skill coding-standards-nazrulsoftwaredev
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: coding-standards
Source: https://github.com/nazrulsoftwaredev/NIT_CRM_2/tree/main/.agents/.agents/skills/coding-standards
Command: npx skills add https://github.com/nazrulsoftwaredev/NIT_CRM_2 --skill coding-standards-nazrulsoftwaredev

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill addresses inconsistency in codebases by providing a unified set of rules for naming, structure, and quality, reducing technical debt and onboarding friction.

Core Features & Use Cases

  • Standardized Conventions: Defines clear rules for TypeScript/JavaScript naming, immutability, and error handling.
  • Quality Assurance: Provides a framework for code reviews, focusing on readability, KISS, DRY, and YAGNI principles.
  • Use Case: Use this skill when performing a pull request review to ensure the submitted code adheres to the project's established patterns for React components, API design, and testing.

Quick Start

Use the coding-standards skill to review the current module for adherence to naming conventions and error handling patterns.

Frequently Asked Questions about coding-standards

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

FAQPage Schema
How do I enforce consistent coding standards across a TypeScript and React codebase?

Enforce consistent coding standards by applying unified rules for TypeScript naming, immutability, and React component structure. This ensures cross-project maintainability and readability while satisfying clean code principles like KISS, DRY, and YAGNI.

What are the best practices for performing a code review on a React and TypeScript pull request?

Best practices for code reviews involve checking submitted code against established patterns for React components, REST API design, and error handling. This framework focuses on readability and structural consistency to reduce technical debt and onboarding friction.

How do I apply clean code principles like DRY and YAGNI during module development?

Apply clean code principles like DRY and YAGNI by standardizing cross-project coding conventions during new module development. This enforces structural consistency, proper naming, and immutability across frontend and backend architectures.

Can I use this coding standards framework for both frontend and backend architectures?

Yes, you can use this coding standards framework for both frontend and backend architectures. It standardizes cross-project conventions for naming, error handling, and REST API design to improve overall maintainability.

When do I need to standardize coding conventions for refactoring tasks?

Standardize coding conventions for refactoring tasks when you need to reduce inconsistency and technical debt in your codebase. Applying unified rules for structure and quality ensures the refactored code adheres to established readability and error handling patterns.