coding-standards

Enforce standardized coding practices across TypeScript, JavaScript, React, and Node.js projects.

302|21|Updated May 10, 2026
One-click install
npx skills add https://github.com/virgo777/buddyme --skill coding-standards-virgo777
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: coding-standards
Source: https://github.com/virgo777/buddyme/tree/main/buddyMe/skill_library/skills/coding-standards
Command: npx skills add https://github.com/virgo777/buddyme --skill coding-standards-virgo777

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill codifies and enforces consistent coding standards, best practices, and patterns across TypeScript, JavaScript, React, and Node.js projects, helping teams maintain readability, reduce bugs, and accelerate onboarding.

Core Features & Use Cases

  • Language and framework conventions: TypeScript/JavaScript naming, function naming, API design, React component patterns, and file naming standards.
  • Code Quality Principles: Readability First, KISS, DRY, YAGNI, immutability, and robust error handling guidelines.
  • Team enablement: Onboarding new contributors, guiding code reviews, and enabling automated linting/formatting rules.

Quick Start

Review a module in your TS/JS/React/Node project and refactor it to follow the standards described above.

Frequently Asked Questions about coding-standards

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

FAQPage Schema
What coding standards should I follow for TypeScript and React projects?

Coding standards for TS/JS/React/Node enforce naming conventions, immutability, robust error handling, and React component patterns. They apply during project initialization and refactors to ensure consistent style across modules.

How do I enforce consistent code quality and best practices across a Node.js team?

You can enforce code quality by applying standardized rules during code reviews and project setup. This skill provides guidelines on KISS, DRY, YAGNI, and error handling to help teams maintain readability and accelerate onboarding.

Can I use these coding standards to guide refactoring an existing JavaScript module?

Yes, you can review a module in your TS/JS/React/Node project and refactor it to follow the standardized coding practices. This ensures consistent style, proper error handling, and improved readability during refactors.

What is the best way to standardize file naming and API design across TypeScript and Node.js?

The best way to standardize file naming and API design is to codify unified conventions applied during initialization and code reviews. This skill provides specific guidelines for file organization and API design across TS and Node.js projects.

Do I need to configure automated linting rules separately when adopting these React and Node best practices?

While this skill defines the standards, it also enables automated linting and formatting rules. You can use these guidelines to configure your linter and enforce the codified patterns during development and code reviews.