coding-standards

Enforce unified coding standards for TypeScript/JavaScript, React, and REST API projects.

Updated Mar 26, 2026
One-click install
npx skills add https://github.com/luongldptit/move-ticket --skill coding-standards-luongldptit
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: coding-standards
Source: https://github.com/luongldptit/move-ticket/tree/main/.agent/.agents/skills/coding-standards
Command: npx skills add https://github.com/luongldptit/move-ticket --skill coding-standards-luongldptit

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill eliminates inconsistent code quality, varying naming conventions, and fragmented best practices across projects that lead to technical debt, onboarding friction, and hard-to-maintain codebases.

Core Features & Use Cases

  • Universal Baseline Conventions: Standardized rules for naming, immutability, readability, error handling, and type safety applicable to all TypeScript/JavaScript projects.
  • Code Quality Review Guardrails: Built-in checks for KISS, DRY, YAGNI principles, and common anti-patterns like long functions, deep nesting, and magic numbers.
  • Use Case: Onboard new team members to unified coding standards, or review pull requests for consistency without needing to reference framework-specific playbooks for core quality rules.

Quick Start

Use the coding-standards skill to review the latest pull request for naming consistency, immutability violations, and missing error handling.

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 TypeScript and React coding standards across multiple projects?

The coding-standards skill checks TypeScript and React code against KISS, DRY, and YAGNI principles to detect anti-patterns like long functions, deep nesting, and magic numbers during code reviews or refactoring.

What is the best way to review a pull request for code quality and anti-patterns?

The best way to review a pull request is to check the code against KISS, DRY, and YAGNI principles to detect anti-patterns like long functions, deep nesting, and magic numbers without needing framework-specific playbooks.

Does this coding convention check work with REST API design and JavaScript projects?

Yes, the coding convention checks apply to TypeScript, JavaScript, React, and REST API development scenarios, enforcing baseline standards for error handling and type safety across these environments.

How do I onboard new contributors to maintainable code practices without framework-specific playbooks?

You can onboard new contributors by applying universal baseline conventions for readability and type safety, ensuring they follow unified cross-project coding rules without needing to reference framework-specific playbooks.

When do I need unified coding conventions for refactoring and new project setup?

You need unified coding conventions during refactoring and new project setup to eliminate technical debt, prevent onboarding friction, and ensure consistent code maintainability across all TypeScript and JavaScript projects.