You can create a coding standards guide for your project by looking at existing code. This tool reads your files or folders and learns the patterns you already use. It checks things like indentation, naming, and comments. Then it writes a clear document everyone can follow. Consistent code is easier to read and maintain. The guide helps new team members get up to speed fast.
You control the output. Choose a detailed or minimal template. Add the standards straight to your README file. The tool can find and fix inconsistencies in your codebase. It even suggests a filename for the new document that does not already exist in your project.
Global
mkdir -p ~/.claude/skills/write-coding-standards-from-fileProject
mkdir -p .claude/skills/write-coding-standards-from-fileSource Repository
Improve Codebase Architecturemattpocock/skills
Scan your codebase for architecture improvements with visual reports and pick one to refactor
Web Design Guidelinesvercel-labs/agent-skills
Review your UI code for compliance with web interface guidelines
Caveman Reviewjuliusbrussee/caveman
Ultra-compressed one-line code review comments that cut noise
Zoom Outmattpocock/skills
Get a big picture view of your code with a simple map of modules and callers
Codebase Designmattpocock/skills
Create deep modules with tiny interfaces and lots of hidden logic for testability
Requesting Code Reviewobra/superpowers
Catch code issues early with focused automated reviews before every merge
Request Refactor Planmattpocock/skills
Plan safe code refactors with tiny commits and clear GitHub issues
Receiving Code Reviewobra/superpowers
Think first, then code. Verify feedback before making changes. Stay objective