Create language-specific code style guides for teams
Create a code style guide for:
**Language:** {{LANGUAGE}}
**Framework:** {{FRAMEWORK}} (if applicable)
**Team Size:** {{TEAM_SIZE}}
**Existing Tools:** {{TOOLS}} (ESLint, Prettier, etc.)
**Specific Preferences:**
{{PREFERENCES}}
Generate a comprehensive style guide:
# {{LANGUAGE}} Style Guide
## Introduction
- Purpose of this guide
- How to use it
- Enforcement tools
## 1. Naming Conventions
### Variables
- camelCase/snake_case rules
- Meaningful names
- Abbreviations
### Functions/Methods
- Verb prefixes
- Naming patterns
### Classes/Types
- PascalCase rules
- Interface prefixes
### Constants
- UPPER_SNAKE_CASE
- Magic numbers
### Files
- File naming convention
- Directory structure
## 2. Formatting
### Indentation
- Spaces vs tabs
- Indent size
### Line Length
- Maximum characters
- Breaking long lines
### Braces
- Same line vs new line
- Single-statement blocks
### Spacing
- Around operators
- After commas
- In function calls
## 3. Code Organization
### File Structure
- Import ordering
- Section organization
### Function Length
- Maximum lines
- When to split
### Class Structure
- Member ordering
- Visibility grouping
## 4. Comments
### When to Comment
### Comment Style
### Documentation Comments
## 5. Best Practices
### Error Handling
### Null/Undefined
### Async Code
## 6. Anti-Patterns
What to avoid
## 7. Tool Configuration
ESLint/Prettier config examplesOr press ⌘C to copy
Replace these placeholders with your own content before using the prompt.
[{LANGUAGE][{FRAMEWORK][{TEAM_SIZE][{TOOLS][{PREFERENCES]