Style guide

Skill tenxengineer/conductor_cc/skills/style-guide

Apply language-specific style guide rules to your code. Use when writing or reviewing code to ensure consistency with best practices.From its SKILL.md

Install

npx -y skills add tenxengineer/conductor_cc --skill style-guide

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

SKILL.md

2.1 KB, as published. Nobody here has run it

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_case for functions/variables, PascalCase for classes
Docstrings with Args/Returns/Raises sections
Type hints for public APIs

TypeScript/JavaScript (Google Style)

2 spaces indentation, 80 char lines
const by default, let if needed, never var
Named exports only, no default exports
Semicolons required, single quotes for strings

Go (Effective Go)

Run gofmt always
MixedCaps naming, no underscores
Short package names, explicit error handling
Small interfaces, goroutines for concurrency

Rust (API Guidelines)

Run rustfmt always
snake_case for functions, UpperCamelCase for types
Result<T, E> for errors, avoid unwrap() in prod
Derive common traits: Debug, Clone, PartialEq

Swift (Apple Guidelines)

4 spaces indentation
lowerCamelCase for functions, UpperCamelCase for types
Prefer guard let for early exits
Use async/await for concurrency

Dart (Effective Dart)

Run dart format always
lowerCamelCase for everything except types
Use /// doc comments for public APIs
Prefer final for 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