aiskillstore/marketplace / skills/89jobrien/global-standards
global-standards
VerifiedProject-wide coding standards and conventions specialist. Use PROACTIVELY when writing code, making architectural decisions, or establishing project conventions. Covers coding style, commenting, error handling, validation, tech stack consistency, and project conventions across all languages and frameworks.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 8.0 KB |
| references/coding-style.md | markdown | 1.2 KB |
| references/commenting.md | markdown | 1.1 KB |
| references/conventions.md | markdown | 1.6 KB |
| references/error-handling.md | markdown | 1.4 KB |
| references/tech-stack.md | markdown | 1.2 KB |
| references/validation.md | markdown | 1.2 KB |
| skill-report.json | config | 19.8 KB |
references/coding-style.md
View on GitHub---
author: Joseph OBrien
status: unpublished
updated: '2025-12-23'
version: 1.0.1
tag: skill
type: reference
parent: global-standards
---
# Coding Style Standards
Detailed guidelines for coding style, naming conventions, and code organization.
## Naming Conventions
### Variables and Functions
- Use descriptive names that reveal intent
- Prefer full words over abbreviations
- Use camelCase for JavaScript/TypeScript
- Use snake_case for Python
- Use PascalCase for classes and types
### Files and Directories
- Use kebab-case for file names
- Match file names to their primary export
- Use descriptive directory names
## Code Organization
### Function Size
- Keep functions small and focused
- Single Responsibility Principle
- Extract complex logic into separate functions
### Structure
- Clear separation of concerns
- Logical grouping of related code
- Consistent indentation and formatting
## DRY Principle
- Extract reusable logic into functions
- Avoid code duplication
- Use shared utilities and helpers
## Formatting
- Consistent indentation (spaces or tabs per project)
- Proper spacing around operators
- Consistent line length limits
- Proper import organization
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| receiving-code-reviewobra/superpowersUse when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| requesting-code-reviewobra/superpowersUse when completing tasks, implementing major features, or before merging to verify work meets requirements | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| using-git-worktreesobra/superpowersUse when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallback | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| verification-before-completionobra/superpowersUse when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |