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/tech-stack.md

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

# Tech Stack Standards

Technology stack reference and consistency guidelines.

## Framework Patterns

### Frontend

- Follow framework-specific patterns (React hooks, Vue composition API, etc.)
- Use framework-recommended libraries
- Maintain consistency with existing code

### Backend

- Follow framework conventions (Express middleware, FastAPI decorators, etc.)
- Use established patterns for API design
- Maintain consistency across services

## Dependency Management

### Adding Dependencies

- Evaluate necessity before adding
- Prefer existing tools over new ones
- Check for security vulnerabilities
- Document why dependency is needed

### Version Management

- Pin versions for production
- Use semantic versioning
- Keep dependencies up to date
- Test updates before deploying

## Technology Choices

### Consistency

- Use established patterns
- Follow project conventions
- Document technology decisions
- Maintain architectural consistency

### Evaluation Criteria

- Performance requirements
- Team expertise
- Maintenance burden
- Security considerations
- Cost implications
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