Agent skill · software engineering · aiskillstore
global-standards
Project-wide coding standards and conventions specialist. Use PROACTIVELY
Why this skill is useful
Codifies project-wide coding standards and conventions that the AI could infer but now doesn't have to guess.
What it needs
About 4k tokens when loaded. Last updated 2026-08-07. 405 stars on the source repository.
What this skill does
Project Standards This skill provides comprehensive guidance on project-wide coding standards, conventions, and best practices that apply across the entire codebase regardless of language or framework. When to Use This Skill Use this skill when: Writing code - Ensuring consistency with project standards Making architectural decisions - Following established patterns Onboarding - Understanding project conventions Code review - Checking adherence to standards Refactoring - Maintaining consistency during changes Setting up new features - Following project conventions Core Standards Areas 1. Coding Style When to apply: Naming variables, functions, classes, modules, or files Structuring code for readability and maintainability Deciding on function size and single responsibility Removing unused code, commented-out blocks, or dead imports Extracting reusable logic to avoid duplication Applying consistent formatting and indentation Refactoring code for clarity and simplicity Principles: Clear, descriptive names that reveal intent DRY (Don't Repeat Yourself) principle Single Responsibility Principle Self-documenting code through structure Consistent formatting across the codebase Applies to: All code files (.py,.js, .ts,.jsx, .tsx,.vue, .rb,.go, .java,.rs, .cpp,.c, .swift,.kt) 2. Commenting Standards When to apply: Deciding whether code needs a comment Documenting complex algorithms or non-obvious business logic Writing docstrings or function documentation Reviewing existing comments for relevance Removing outdated or misleading comments Explaining non-obvious code decisions or workarounds Principles: Minimal, helpful comments Explain why, not what Keep code self-documenting through clear naming Comments should explain complex logic or business rules Avoid comments that restate what code does Keep comments evergreen and relevant Applies to: All code files across the entire codebase 3. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills aiskillstore/global-standards