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/validation.md

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

# Validation Standards

Input validation patterns and security best practices.

## Validation Principles

### Client and Server

- Always validate on the server side
- Provide immediate feedback on the client
- Never trust client-side validation alone

### Validation Libraries

- Use established libraries (Zod, Yup, Pydantic, Joi)
- Define schemas for consistency
- Reuse validation schemas across layers

## Input Sanitization

### Security

- Prevent XSS attacks
- Prevent SQL injection
- Prevent command injection
- Use allowlists over blocklists

### Data Types

- Validate types, formats, and ranges
- Check required fields
- Validate nested objects and arrays

## Business Rules

- Validate domain-specific rules
- Check sufficient balance, valid dates, permissions
- Implement custom validators when needed

## Error Messages

- Clear, actionable validation errors
- Show errors near the relevant input
- Provide real-time feedback when possible

## File Uploads

- Validate file size limits
- Check allowed file types
- Validate file content when possible
- Scan for malware if applicable
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