cc-skill-coding-standards
Universal coding standards, best practices, and patterns for TypeScript, JavaScript, React, and Node.js development.
Target: Software development & testing. Automatically collected · unverified.
Excerpt from the author’s documentation
Extracted from a fixed version of SKILL.md in its original language. This is the author’s documentation; installation, compatibility and runtime results have not been verified by this site.
Read the original English text
Topics in the source
- Coding Standards & Best Practices
- Code Quality Principles
- 1. Readability First
- 2. KISS (Keep It Simple, Stupid)
- 3. DRY (Don't Repeat Yourself)
- 4. YAGNI (You Aren't Gonna Need It)
- TypeScript/JavaScript Standards
- Variable Naming
Universal coding standards applicable across all projects. Code is read more than written Clear variable and function names Self-documenting code preferred over comments Consistent formatting Simplest solution that works Avoid over-engineering No premature optimization Easy to understand > clever code Extract common logic into functions Create reusable components Share utilities across modules Avoid copy-paste programming Don't build features before they're needed Avoid speculative generality Add complexity only when required Start simple, refactor when needed Watch for these anti-patterns: Remember: Code quality is not negotiable. Clear, maintainable code enables rapid development and confident refactoring.
- Source repository
- davila7/claude-code-templates
- Source file
- cli-tool/components/skills/development/cc-skill-coding-standards/SKILL.md
- Fixed revision
- 21be197f100a12b8d0dd9a211cc244c8179f84d3
Sources and evidence
This record was collected automatically. Its documentation, suitability and runtime behavior have not been manually verified.
Author: davila7/claude-code-templates · original repository metadata. Documentation review: Not reviewed. Last source check: 2026-11-09T14:01:44.144Z.
Categories are inferred from names, descriptions and paths. They do not establish compatibility.
License and attribution
MIT. Third-party content and copyright remain with their authors. Refer to the original license and terms.
Original license ↗Synchronization, copying and user-reported success do not mark a resource as runtime-tested.
Limitations and notes
- Collecting metadata does not mean this site has installed, adapted, runtime-tested or security-reviewed the resource.