This guide sets shared coding rules for every project. It helps developers write clean, consistent, and easy to read code. Clear naming and simple solutions are the main focus. The rules apply to any language or framework. New team members can learn these conventions quickly. Everyone follows the same baseline so code looks familiar across projects.
Use this skill when starting a new project or reviewing code. It covers immutability, error handling, and common quality principles like KISS, DRY, and YAGNI. For detailed framework patterns, use separate frontend or backend skills. This skill is the shared floor, not the deep dive.
By following these standards, teams reduce confusion and avoid bugs. Code becomes easier to maintain and refactor. The result is a consistent codebase that everyone can work on with confidence.
Global
mkdir -p ~/.claude/skills/coding-standardsProject
mkdir -p .claude/skills/coding-standardsSource Repository
Web Design Guidelinesvercel-labs/agent-skills
Review your UI code for compliance with web interface guidelines
Improve Codebase Architecturemattpocock/skills
Scan your codebase for architecture improvements with visual reports and pick one to refactor
Zoom Outmattpocock/skills
Get a big picture view of your code with a simple map of modules and callers
Caveman Reviewjuliusbrussee/caveman
Ultra-compressed one-line code review comments that cut noise
Requesting Code Reviewobra/superpowers
Catch code issues early with focused automated reviews before every merge
Receiving Code Reviewobra/superpowers
Think first, then code. Verify feedback before making changes. Stay objective
Auditpbakaus/impeccable
Audit your code for accessibility performance theming and anti-patterns
Request Refactor Planmattpocock/skills
Plan safe code refactors with tiny commits and clear GitHub issues