coding-style-guide

Standardize React/TypeScript code with naming, export, and destructuring rules.

Updated Jan 6, 2026
One-click install
npx skills add https://github.com/xxziiko/subagent --skill coding-style-guide
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: coding-style-guide
Source: https://github.com/xxziiko/subagent/tree/main/.claude/skills/coding-style-guide
Command: npx skills add https://github.com/xxziiko/subagent --skill coding-style-guide

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Inconsistent code styles slow teams down and make maintenance harder. This Skill provides a centralized set of conventions for React/TypeScript projects to ensure readability and long-term maintainability.

Core Features & Use Cases

  • Clean Code Principles: readability, simplicity, clarity, and consistency across the codebase.
  • Declarative Naming and Destructuring: guidance on naming, data extraction, and component interfaces.
  • Export and Organization Rules: best practices for component exports, utilities, and file structure to improve maintainability.
  • Practical Examples: patterns for components, hooks, and utilities that teams can apply immediately.

Quick Start

  • Start by applying the guide to a small React/TypeScript component to assess alignment.
  • Refactor an existing module to conform to the naming, export, and destructuring rules.
  • Use a short code review to verify adherence and progressively adopt across the project.

Frequently Asked Questions about coding-style-guide

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

FAQPage Schema
What is the best way to standardize React and TypeScript code conventions across a team?

A React and TypeScript style guide enforces declarative naming, destructuring, and export rules across components and hooks to improve consistency and reduce maintenance overhead.

How do I apply clean code principles to React component patterns and hooks?

Apply clean code principles to React components and hooks by using declarative naming conventions, consistent destructuring, and cohesive file organization rules defined in a TypeScript style guide.

Can I use this coding style guide for both React components and utility files?

Yes, the coding style guide applies across React components, utilities, and hooks, providing practical patterns and organization rules to standardize interfaces and file structure.

How do I start adopting a TypeScript style guide for an existing project?

Start adopting the TypeScript style guide by applying it to a small React component, refactoring an existing module to conform to naming and export rules, and verifying adherence through a short code review.

Does the React TypeScript style guide support custom scripts and reference assets?

Yes, the React TypeScript style guide supports optional scripts, references, and assets directories for extensibility, requiring a YAML frontmatter with a name and description.