# Cc Skill Coding Standards

> Universal coding standards, best practices, and patterns for TypeScript, JavaScript, React, and Node.js development.

- Skill: `newmindsgroup/cc-skill-coding-standards` (Agent Skill, multi-file: 2 files)
- Install (CLI): `npx skillmds@latest add newmindsgroup/cc-skill-coding-standards`
- Raw SKILL.md: https://api.skillmd.com/api/skills/newmindsgroup/cc-skill-coding-standards/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Web & Frontend
- License: MIT
- Author: newmindsgroup (https://skillmd.com/u/newmindsgroup)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/newmindsgroup/cc-skill-coding-standards

---


# Coding Standards & Best Practices

Universal coding standards applicable across all projects.

## When to Use
- This skill is applicable to execute the workflow or actions described in the overview.

## Core Workflow
1. Confirm the request matches this skill's trigger, scope, and risk profile.
2. Use the topic map to identify the relevant pattern, checklist, or example before writing detailed guidance or code.
3. Load `references/full-guidance.md` when implementation details, examples, anti-patterns, validation checks, or edge cases are needed.
4. Apply only the relevant guidance instead of loading or repeating the entire reference by default.
5. Verify the result against any validation checks, limitations, security notes, or platform constraints in the reference.

## Topic Map
- Code Quality Principles
- Readability First
- KISS (Keep It Simple, Stupid)
- DRY (Don't Repeat Yourself)
- YAGNI (You Aren't Gonna Need It)
- TypeScript/JavaScript Standards
- Variable Naming
- Function Naming
- Immutability Pattern (CRITICAL)
- Error Handling
- Async/Await Best Practices
- Type Safety
- React Best Practices
- Component Structure
- Custom Hooks
- State Management
- Conditional Rendering
- API Design Standards

## Reference Map
- `references/full-guidance.md` preserves the complete original guidance, including examples and detailed edge cases.

## Limitations
- Use this skill only when the task clearly matches the scope described above.
- Do not treat the output as a substitute for environment-specific validation, testing, or expert review.
- Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.

## Progressive Loading
Keep this `SKILL.md` as the compact routing and workflow entrypoint. Load the reference file only when the user task requires the deeper implementation material.