global-standards
Apply consistent coding standards
Also available from: Joseph OBrien
Developers and teams struggle to maintain consistent code style across projects. This skill provides comprehensive standards for naming conventions, error handling, validation patterns, and project conventions to ensure uniform, maintainable code.
Download the skill ZIP
Upload in Claude
Go to Settings → Capabilities → Skills → Upload skill
Toggle on and start using
Test it
Using "global-standards". What are the naming conventions for JavaScript variables and functions?
Expected outcome:
- Use camelCase for variables and functions (e.g., `userName`, `calculateTotal`)
- Use PascalCase for classes and types (e.g., `UserModel`, `ApiResponse`)
- Use UPPER_SNAKE_CASE for constants (e.g., `MAX_RETRIES`, `API_URL`)
- Use descriptive names that reveal intent (avoid `x`, `temp`, `data`)
- Use full words over abbreviations unless widely accepted (e.g., `user` not `usr`)
Using "global-standards". How should I handle errors in my API endpoint?
Expected outcome:
- Wrap external service calls in try-catch blocks
- Log errors with appropriate severity levels and context
- Implement retry logic with exponential backoff for transient failures
- Create custom exception types for domain-specific errors
- Return user-friendly error messages without sensitive details
Using "global-standards". What validation patterns should I use for user input?
Expected outcome:
- Validate on both client and server sides - never trust client validation alone
- Use established validation libraries like Zod, Yup, Pydantic, or Joi
- Sanitize input to prevent XSS, SQL injection, and command injection
- Use allowlists over blocklists for input validation
- Provide clear, actionable error messages near the relevant input
Security Audit
SafePure documentation skill containing only markdown reference files. Static findings are all false positives: the skill has no executable code, no network access, no file system operations, no command execution, and no environment variable access. All 52 detected patterns are benign documentation content, including code examples in markdown and references to external services in best-practices context.
Risk Factors
⚙️ External commands (17)
🌐 Network access (1)
Quality Score
What You Can Build
Maintain code consistency
Ensure all team members follow the same coding style and conventions across the codebase
Establish project standards
Define and communicate coding standards for new projects or onboarding materials
Validate code submissions
Check pull requests against established standards for style, error handling, and validation
Try These Prompts
What are the naming conventions for [JavaScript/Python/TypeScript] when naming [variables/functions/classes]?
How should I handle errors in my API endpoint that calls an external service? Include retry logic and user messages.
What validation patterns should I use for a registration form with email, password, and name fields?
What file structure, naming conventions, and git workflows should I establish for a new [React/Python/Node] project?
Best Practices
- Apply standards proactively when writing new code, not just during review
- Match the style of surrounding code when adding to existing files
- Use the reference files for detailed guidance on specific topics
Avoid
- Mixing different naming styles within the same file or module
- Leaving outdated or misleading comments in code
- Skipping input validation for internal APIs assuming trusted sources