Skills cc-skill-coding-standards
📦

cc-skill-coding-standards

Safe

Enforce Coding Standards Across Your Codebase

Inconsistent code quality leads to bugs and technical debt. This skill provides universal coding standards, best practices, and patterns for TypeScript, JavaScript, React, and Node.js development to help you write clean, maintainable code.

Supports: Claude Codex Code(CC)
⚠️ 68 Poor
1

Download the skill ZIP

2

Upload in Claude

Go to Settings → Capabilities → Skills → Upload skill

3

Toggle on and start using

Test it

Using "cc-skill-coding-standards". Review this function for coding standards compliance: function get(u) { return fetch(u).then(d=>d.json()) }

Expected outcome:

This function violates multiple standards: unclear naming (get, u, d), no error handling, no type safety, and returns data without checking response.ok. Refactored version includes: descriptive name (fetchMarketData), proper TypeScript types, comprehensive error handling with try/catch, and response validation.

Using "cc-skill-coding-standards". Generate a React button component following the standards

Expected outcome:

Functional component with TypeScript interface (ButtonProps), proper prop types (children, onClick, disabled, variant), default values for optional props, and semantic HTML structure. Includes prop spreading and className composition.

Using "cc-skill-coding-standards". Check if this code follows immutability patterns: user.name = 'New Name'; items.push(newItem);

Expected outcome:

This code violates the immutability principle. Direct mutation of objects and arrays causes unexpected side effects. Correct approach: use spread operator for objects ({...user, name: 'New Name'}) and arrays ([...items, newItem]) to create new references instead of mutating existing ones.

Security Audit

Safe
v1 • 2/25/2026

All 73 static analysis findings are false positives. The detected patterns (backtick execution, weak crypto, system reconnaissance) are Markdown code blocks and documentation examples, not executable code. This is a pure documentation skill with no executable functionality. No security risks identified.

1
Files scanned
528
Lines analyzed
3
findings
1
Total audits
Low Risk Issues (3)
SKILL.md:44-54SKILL.md:58-68SKILL.md:72-84SKILL.md:88-95
Documentation Code Examples Trigger Static Scanner
The static scanner detected 53 instances of 'Ruby/shell backtick execution' patterns. These are Markdown code blocks (```typescript) used for documentation, not actual shell execution. The skill contains only code examples and best practices documentation.
SKILL.md:92SKILL.md:107
Fetch API Examples in Documentation
Detected 2 instances of fetch() calls at lines 92 and 107. These are documentation examples showing proper async/await error handling patterns, not actual network requests made by the skill.
SKILL.md:409
Dynamic Import for React Lazy Loading Example
Detected dynamic import() at line 409. This is a documentation example showing React's lazy() pattern for code splitting, not actual dynamic imports executed by the skill.
Audited by: claude

Quality Score

38
Architecture
90
Maintainability
87
Content
23
Community
99
Security
87
Spec Compliance

What You Can Build

Code Review Assistant

Use this skill during code reviews to validate that pull requests follow established coding standards and best practices.

Onboarding New Developers

Help new team members understand your codebase standards and conventions by providing consistent examples and patterns.

Code Quality Improvement

Apply these standards when refactoring legacy code to improve maintainability and reduce technical debt.

Try These Prompts

Review Code Against Standards 
Review this code against the coding standards and best practices defined in the cc-skill-coding-standards skill. Identify any violations and suggest improvements.
Refactor for Best Practices 
Refactor this code to follow TypeScript and React best practices from the cc-skill-coding-standards skill. Focus on immutability, error handling, and component structure.
Generate Standards-Compliant Code 
Generate a [component/function/module] that follows the coding standards from cc-skill-coding-standards. Include proper types, error handling, and documentation.
Explain Standards Violations 
Explain why this code violates the coding standards in cc-skill-coding-standards. Reference specific principles like KISS, DRY, or YAGNI.

Best Practices

  • Always use descriptive variable and function names that explain intent rather than abbreviated forms
  • Apply immutability patterns consistently using spread operators instead of direct mutation
  • Implement comprehensive error handling for async operations with try/catch blocks and response validation
  • Use TypeScript types and interfaces instead of 'any' to maintain type safety

Avoid

  • Avoid mutation of objects and arrays directly - use spread operators or immutable update patterns
  • Do not use 'any' type in TypeScript - always define proper interfaces and type annotations
  • Never omit error handling in async functions - always include try/catch with proper error messages
  • Avoid deeply nested conditionals - use early returns and guard clauses for clarity

Frequently Asked Questions

Are these coding standards mandatory for all projects?
No, these are recommended best practices. Adapt them to your team's specific needs and existing conventions. The standards provide a foundation for consistent, high-quality code.
Can I use these standards with languages other than TypeScript and JavaScript?
While many principles like KISS, DRY, and YAGNI apply universally, the specific examples target TypeScript and JavaScript ecosystems. Adapt the concepts to your language of choice.
How do I enforce these standards in my team?
Combine these standards with linting tools (ESLint, Prettier), pre-commit hooks, and code review checklists. Use the skill during reviews to catch violations early.
What if the standards conflict with my existing codebase?
Apply standards incrementally. Prioritize new code and high-risk areas when refactoring. Gradual adoption is better than attempting a complete rewrite.
Do these standards replace the need for code reviews?
No, these standards complement code reviews. They provide objective criteria for evaluation, but reviews also capture context-specific decisions and architectural considerations.
How often should I update these standards?
Review and update standards quarterly or when adopting new frameworks. Balance stability with evolution - resist frequent changes but adapt to new best practices in the ecosystem.

Developer Details

Author

affaan-m

License

MIT

Repository

https://github.com/sickn33/antigravity-awesome-skills/tree/main/skills/cc-skill-coding-standards

Ref

main

File structure

📄 SKILL.md