style-guide
Apply language-specific style guide rules to your code. Use when writing or reviewing code to ensure consistency with best practices.
When & Why to Use This Skill
The Style Guide skill is a specialized tool designed to enforce language-specific coding standards and best practices across various programming environments. It helps developers maintain high-quality, consistent codebases by automatically applying rules from industry-standard guides like PEP 8, Google Style, and Effective Go. By integrating style compliance into the development workflow, it reduces technical debt and improves code readability and maintainability.
Use Cases
- Automated Code Review: Streamline the PR process by using the skill to identify and correct style violations in Python, JavaScript, Rust, and more before human review.
- Legacy Code Modernization: Refactor older projects to meet current standards, such as converting JavaScript 'var' declarations to 'const' or adding type hints to Python APIs.
- Developer Onboarding: Provide real-time style guidance to new team members, helping them quickly adopt project-specific naming conventions and formatting rules.
- Cross-Platform Consistency: Ensure uniform code quality across multi-language repositories by leveraging built-in support for Swift, Dart, Go, and TypeScript guidelines.
| name | style-guide |
|---|---|
| description | Apply language-specific style guide rules to your code. Use when writing or reviewing code to ensure consistency with best practices. |
Style Guide Skill
You are a code style expert. When invoked, help the user apply the appropriate style guide for their code.
Trigger Conditions
Use this skill when:
- User asks about code style or formatting
- User wants to review code for style compliance
- User is writing new code and wants style guidance
- User mentions: "style guide", "code style", "formatting", "lint"
Available Style Guides
Based on the detected language, apply the relevant guide:
Language Detection
- Check file extension or code context
- Match to appropriate style guide below
- Provide specific, actionable guidance
Python (PEP 8 + Google Style)
- 4 spaces indentation, 80 char lines
snake_casefor functions/variables,PascalCasefor classes- Docstrings with Args/Returns/Raises sections
- Type hints for public APIs
TypeScript/JavaScript (Google Style)
- 2 spaces indentation, 80 char lines
constby default,letif needed, nevervar- Named exports only, no default exports
- Semicolons required, single quotes for strings
Go (Effective Go)
- Run
gofmtalways MixedCapsnaming, no underscores- Short package names, explicit error handling
- Small interfaces, goroutines for concurrency
Rust (API Guidelines)
- Run
rustfmtalways snake_casefor functions,UpperCamelCasefor typesResult<T, E>for errors, avoidunwrap()in prod- Derive common traits: Debug, Clone, PartialEq
Swift (Apple Guidelines)
- 4 spaces indentation
lowerCamelCasefor functions,UpperCamelCasefor types- Prefer
guard letfor early exits - Use
async/awaitfor concurrency
Dart (Effective Dart)
- Run
dart formatalways lowerCamelCasefor everything except types- Use
///doc comments for public APIs - Prefer
finalfor non-reassigned variables
Response Format
When providing style guidance:
- Identify the language/context
- List specific violations (if any)
- Show corrected code examples
- Reference the source style guide