Skip to content

aiskillstore/marketplace / skills/89jobrien/global-standards

global-standards

Verified

Project-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.

FileKindSize
SKILL.mdskill md8.0 KB
references/coding-style.mdmarkdown1.2 KB
references/commenting.mdmarkdown1.1 KB
references/conventions.mdmarkdown1.6 KB
references/error-handling.mdmarkdown1.4 KB
references/tech-stack.mdmarkdown1.2 KB
references/validation.mdmarkdown1.2 KB
skill-report.jsonconfig19.8 KB

references/conventions.md

View on GitHub
---
author: Joseph OBrien
status: unpublished
updated: '2025-12-23'
version: 1.0.1
tag: skill
type: reference
parent: global-standards
---

# Project Conventions

File structure, git workflows, and project organization standards.

## File Structure

### Organization

- Logical grouping of related files
- Consistent directory naming
- Clear separation of concerns
- Standard project layout

### Naming

- Use kebab-case for files and directories
- Match file names to their purpose
- Use descriptive names

## Git Workflows

### Commit Messages

- Use conventional commit format
- Write clear, descriptive messages
- Reference issues when applicable
- Keep commits focused and atomic

### Branching

- Use feature branches
- Follow branch naming conventions
- Keep branches up to date
- Clean up merged branches

## Configuration Files

### Environment Variables

- Use .env files for local development
- Document required variables
- Never commit secrets
- Provide .env.example template

### Dependencies

- Keep dependency files organized
- Document dependency purposes
- Use lock files for reproducibility
- Regularly update dependencies

## CI/CD

### Workflows

- Automate testing and linting
- Run checks before merging
- Deploy automatically on merge
- Monitor deployment status

### Quality Gates

- Require passing tests
- Enforce code style
- Check security vulnerabilities
- Validate configuration

## Documentation

### README

- Clear project description
- Setup instructions
- Usage examples
- Contributing guidelines

### Changelog

- Document all changes
- Use semantic versioning
- Group changes by type
- Include migration notes
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 implementationStars: 322kUpdated Claude CodeCodexVerifiedInstall
requesting-code-reviewobra/superpowersUse when completing tasks, implementing major features, or before merging to verify work meets requirementsStars: 322kUpdated Claude CodeCodexVerifiedInstall
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 fallbackStars: 322kUpdated Claude CodeCodexVerifiedInstall
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 alwaysStars: 322kUpdated Claude CodeCodexVerifiedInstall