standards

Enforce TypeScript coding standards, naming, JSDoc, and commit practices.

Updated Apr 25, 2026

Search Tags:#typescript #documentation #standards #coding #conventions #best-practices #code-review

Ready to run

npx skills add https://github.com/bymaxone/bymax.claude-code --skill standards-bymaxone

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: standards
Source: https://github.com/bymaxone/bymax.claude-code/tree/main/plugins/bymax-workflow/skills/standards
Command: npx skills add https://github.com/bymaxone/bymax.claude-code --skill standards-bymaxone

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Universal coding standards eliminate drift in style, architecture, and documentation across projects, enabling faster onboarding and more reliable collaboration.

Core Features & Use Cases

Enforces TypeScript strictness and naming conventions to reduce bugs and confusion.
Standardizes JSDoc guidance, layered architecture, error handling, and commit discipline to improve maintainability and reviewability.
Applies at project initiation, PR reviews, and scaffolding, ensuring every new codebase starts from a consistent baseline.

Quick Start

Apply these universal standards to every new codebase before writing any non-trivial code.

Frequently Asked Questions about standards

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

FAQPage Schema

How do I enforce consistent TypeScript coding standards across multiple projects?▼

To enforce consistent TypeScript coding standards, apply strict TypeScript configurations, naming conventions, and JSDoc policies across all projects. This eliminates style drift and ensures maintainability through standardized layered architecture and error handling.

What are the best practices for standardizing code review conventions in TypeScript?▼

Best practices for standardizing code review conventions include enforcing strict TypeScript discipline, JSDoc documentation, layered architecture, and conventional commits. These standards improve reviewability and reduce bugs during pull request evaluations.

Can I use these universal coding standards for non-TypeScript software projects?▼

Yes, you can use these universal coding standards for general software projects beyond TypeScript. They enforce naming conventions, English-only comments, error handling, and commit discipline that apply broadly across different architectures and tech stacks.

How do I set up coding conventions and JSDoc standards when scaffolding a new project?▼

To set up coding conventions and JSDoc standards during scaffolding, apply universal coding standards before writing non-trivial code. This establishes a consistent baseline for naming, documentation, layered architecture, and conventional commits from project initiation.

Why does code quality drift across projects and how do coding standards solve it?▼

Code quality drifts across projects due to inconsistent styles, architectures, and documentation. Universal coding standards solve this by enforcing strict TypeScript configurations and standardized practices, enabling faster onboarding and reliable collaboration.

Do I need a strict TypeScript configuration to follow these coding standards?▼

Yes, a strict TypeScript configuration is required to follow these coding standards. Enforcing strict TypeScript discipline reduces bugs and confusion, forming the foundation for consistent naming, documentation, and error handling across your codebase.