coding-standards

Review code for naming, readability, immutability, and maintainability issues.

Updated May 14, 2026
One-click install
npx skills add https://github.com/WUIX69/e-lock --skill coding-standards-wuix69
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: coding-standards
Source: https://github.com/WUIX69/e-lock/tree/main/.agent/.agents/skills/coding-standards
Command: npx skills add https://github.com/WUIX69/e-lock --skill coding-standards-wuix69

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a shared baseline for code quality so teams can keep naming, structure, readability, and refactoring decisions consistent across projects.

Core Features & Use Cases

  • Naming and Structure Guidance: Helps choose clear identifiers, simpler control flow, and maintainable file organization.
  • Quality Review Standards: Enforces readability, immutability, DRY, KISS, and YAGNI when reviewing or refactoring code.
  • Common Use Cases: Use it to assess TypeScript or JavaScript code, improve React component patterns, tighten error handling, and align tests and API code with consistent conventions.

Quick Start

Ask the coding-standards skill to review your code for naming, immutability, readability, and maintainability issues.

Frequently Asked Questions about coding-standards

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

FAQPage Schema
How do I review TypeScript code for maintainability and readability issues?

Code review for maintainability involves checking naming clarity, simple architecture, strong error handling, and adherence to best practices. Evaluate TypeScript and React components for readability, immutability, and DRY principles to ensure consistent cross-project quality.

What are the best practices for enforcing immutability in React component patterns?

Best practices for enforcing immutability in React components involve applying consistent rules for naming clarity, DRY, and KISS during code review. Ensure components have simple architecture, strong error handling, and adhere to API and testing conventions.

Does this code review approach work for both TypeScript and JavaScript refactoring?

Yes, this code review approach works for both TypeScript and JavaScript refactoring. It assesses code to improve React component patterns, tighten error handling, and align tests and API code with consistent conventions across projects.

When do I need a general convention check instead of a framework-specific linting tool?

You need a general convention check when no narrower framework-specific skill is available. Use it for cross-project code quality reviews and refactors to enforce DRY, KISS, and YAGNI principles, ensuring consistent structure and readability.

How to check API code for consistent error handling and naming conventions?

Check API code for consistent error handling and naming conventions by reviewing identifiers, architecture simplicity, and test alignment. Apply code quality standards to ensure readability, immutability, and adherence to general API best practices.