How does it treat magic numbers?

The skill identifies hardcoded values and suggests moving them to named constants or environment variables to improve maintainability and configuration.

What languages does this skill support?

While the logic and examples are tailored for TypeScript and modern web frameworks, the naming and architectural principles are applicable to most C-style programming languages.

Can this skill help prevent bugs?

Yes, by enforcing immutability, banning the 'any' type, and requiring explicit return types, it significantly reduces the likelihood of runtime errors and type-related bugs.

How does this skill handle file organization?

It recommends keeping files between 200-400 lines and provides a specific 3-tier import hierarchy (external, internal absolute, and relative paths) to ensure readability.

Does it provide guidance on naming conventions?

Yes, it defines specific rules for camelCase (variables/functions), PascalCase (classes/types), kebab-case (files), and UPPER_SNAKE_CASE (constants).

Coding Standards

Name: Coding Standards
Author: tadokoro-ryusuke

bytadokoro-ryusuke

Developer Tools

Enforces consistent naming conventions, file structures, and TypeScript best practices for clean, maintainable code.

About

This skill provides a comprehensive framework for Claude Code to maintain high code quality by adhering to standardized naming conventions, optimal file sizes, and robust TypeScript patterns. It acts as a domain-specific guide for implementing functional programming concepts like immutability and early returns while preventing common anti-patterns such as magic numbers and the use of the 'any' type. It is an essential tool for developers looking to automate style consistency and ensure their AI-generated code meets production-grade standards.

Key Features

File size and import organization guidelines for better modularity
Standardized naming conventions for variables, classes, constants, and files
Functional programming patterns such as immutability and early returns
Strict TypeScript safety rules including 'any' prohibition and explicit return types
0 GitHub stars
Hardcoding prevention and environment variable management

Use Cases

Refactoring legacy code into modern, type-safe, and readable TypeScript patterns
Automating code reviews to ensure new logic aligns with established style guides
Scaffolding new modules or files with the correct naming and directory structure

About

Key Features

File size and import organization guidelines for better modularity
Standardized naming conventions for variables, classes, constants, and files
Functional programming patterns such as immutability and early returns
Strict TypeScript safety rules including 'any' prohibition and explicit return types
0 GitHub stars
Hardcoding prevention and environment variable management

Use Cases

Refactoring legacy code into modern, type-safe, and readable TypeScript patterns
Automating code reviews to ensure new logic aligns with established style guides
Scaffolding new modules or files with the correct naming and directory structure