global-standards

Standardize project-wide coding standards and conventions across languages and frameworks.

4|Updated Dec 23, 2025
One-click install
npx skills add https://github.com/89jobrien/steve --skill global-standards
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: global-standards
Source: https://github.com/89jobrien/steve/tree/main/steve/skills/global-standards
Command: npx skills add https://github.com/89jobrien/steve --skill global-standards

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Inconsistent coding styles and unclear conventions slow teams down. This Skill codifies project-wide standards, guiding coding style, commenting, error handling, validation, tech-stack usage, and overall conventions to maintain quality at scale.

Core Features & Use Cases

  • Coding Style: naming, formatting, and file organization guidelines
  • Commenting Standards: when and how to document code
  • Error Handling: structured errors and user-friendly messages
  • Input Validation: schemas, sanitization, and safe boundaries
  • Tech-Stack Consistency: align across frontend, backend, and tooling
  • Project Conventions: git workflows, CI/CD, and documentation norms

Quick Start

Review the project's coding standards before starting a new feature or performing a code review.

Frequently Asked Questions about global-standards

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I establish coding standards across my entire project?

Coding standards codify project-wide conventions for naming, formatting, commenting, error handling, and validation. This Skill standardizes these across all languages and frameworks, providing guidelines, templates, and lint rules that teams apply during development and code review to maintain consistency at scale.

What should be included in a project's coding standards?

Effective coding standards cover naming conventions, file organization, commenting requirements, error handling patterns, input validation schemas, tech-stack consistency, and project-specific workflows like git and CI/CD processes. This Skill guides implementation of each area with templates and governance processes.

How do coding standards help with code reviews?

Coding standards provide reviewers with explicit criteria for style, validation, error handling, and tech-stack alignment. They reduce subjective feedback, accelerate review cycles, and ensure consistent enforcement across architectural decisions and feature introductions.

Can I apply these standards across different languages and frameworks?

Yes. This Skill applies coding standards across all languages and frameworks by focusing on universal principles—naming, commenting, validation, error handling—rather than language-specific syntax, enabling teams to maintain consistency in polyglot or multi-framework projects.

When should developers review project standards?

Developers should review coding standards before starting new features, performing code reviews, refactoring existing code, or onboarding to the project. This ensures alignment with conventions and reduces rework during review cycles.

What's the difference between linting and coding standards?

Linting enforces automated formatting and syntax rules through tools. Coding standards encompass broader guidance—naming philosophy, validation patterns, error handling strategies, tech-stack decisions, and governance—that linting complements but cannot fully replace.