coding-standards

Enforce coding standards and best practices for TypeScript, JavaScript, React, and Node.js projects.

1|Updated Mar 20, 2024
One-click install
npx skills add https://github.com/flag3/dotfiles --skill coding-standards-flag3
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: coding-standards
Source: https://github.com/flag3/dotfiles/tree/main/.claude/skills/coding-standards
Command: npx skills add https://github.com/flag3/dotfiles --skill coding-standards-flag3

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Inconsistent coding styles and scattered best practices across TypeScript, JavaScript, React, and Node.js projects slow development, reduce code quality, and hinder collaboration. This Skill codifies widely adopted patterns to promote readability, maintainability, and reliability across teams.

Core Features & Use Cases

  • Code Quality Principles: Readability, simplicity, DRY principles, and YAGNI to keep code clear and maintainable.
  • Type Safety & Naming: Enforce descriptive names, proper typing, and immutability to prevent bugs.
  • React & Component Patterns: Use typed props, consistent component structure, and predictable state management.
  • Error Handling & Testing: Standard error handling, validation, and testable interfaces across modules.
  • Use Case: New projects or refactors apply a shared standard so onboarding engineers can contribute quickly with confidence.

Quick Start

Provide a new or existing codebase with a baseline of conventions: rename and reorganize files according to the standards, add type annotations where missing, and adopt the immutability patterns described.

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 JavaScript team?

Enforce consistent coding standards by codifying widely adopted patterns for file naming, type safety, immutability, and error handling across TypeScript, JavaScript, React, and Node.js projects. This reduces inconsistency, improves code quality, and accelerates onboarding by establishing shared conventions the entire team follows.

What are best practices for React component structure and state management?

Best practices for React include using typed props, maintaining consistent component structure, and adopting predictable state management patterns. These practices ensure components are maintainable, testable, and collaborative across teams working on the same codebase.

Can I apply coding standards to an existing codebase or only new projects?

Coding standards apply to both new projects and refactors of existing codebases. Rename and reorganize files, add missing type annotations, and adopt immutability patterns incrementally to establish a shared baseline without requiring a complete rewrite.

Why is type safety and proper naming important in JavaScript projects?

Type safety and descriptive naming prevent bugs, improve code readability, and reduce maintenance overhead in JavaScript projects. Combined with immutability patterns, they make codebases more predictable and easier for teams to collaborate on confidently.

What error handling and testing standards should I follow?

Adopt standard error handling and validation patterns that make modules testable and predictable. Establish clear interfaces for error propagation and test coverage to ensure reliability across TypeScript, JavaScript, React, and Node.js projects.

Do coding standards work for teams of any size?

Coding standards apply to codebases of any size and team scale. They provide guidance for file naming, type safety, component patterns, and error handling that scale from solo projects to large collaborative teams.