global-standards

Enforce universal coding standards for naming, DRY, KISS, YAGNI, error handling, and Git commits.

1|Updated Feb 21, 2026
One-click install
npx skills add https://github.com/BEE-CODED/bee-dev --skill global-standards-bee-coded
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: global-standards
Source: https://github.com/BEE-CODED/bee-dev/tree/main/plugins/bee/skills/standards/global
Command: npx skills add https://github.com/BEE-CODED/bee-dev --skill global-standards-bee-coded

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill ensures all code adheres to a consistent set of high-quality standards, improving maintainability, readability, and reducing bugs across the entire project.

Core Features & Use Cases

  • Standardized Naming: Enforces clear and consistent naming conventions for variables, functions, classes, and files.
  • Code Simplicity: Promotes DRY, KISS, and YAGNI principles to keep code clean and efficient.
  • Robust Error Handling: Guides developers on implementing effective error detection, messaging, and cleanup.
  • Self-Documenting Code: Encourages writing code that is inherently understandable, minimizing the need for excessive comments.
  • Git Best Practices: Defines conventions for commit messages, branching, and code reviews.
  • Use Case: When developing a new feature, this Skill's guidelines will be consulted to ensure variable names are descriptive, functions are concise, and commits follow the conventional commit format.

Quick Start

Follow the global standards for naming conventions, DRY, KISS, YAGNI, error handling, self-documenting code, and Git conventions.

Frequently Asked Questions about global-standards

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

FAQPage Schema
What are universal coding standards for naming conventions and error handling?

Universal coding standards enforce clear naming conventions for variables and functions, alongside robust error handling strategies, to improve code maintainability, readability, and consistency across all languages and frameworks.

How do I apply DRY, KISS, and YAGNI principles to improve code quality?

Apply DRY, KISS, and YAGNI principles by keeping functions concise, eliminating redundancy, and avoiding unnecessary features, which ensures your code remains clean, efficient, and inherently self-documenting.

What is the best way to structure Git commit messages for code reviews?

The best way to structure Git commit messages is by following conventional commit formats and branching conventions, ensuring commits are descriptive and consistent throughout the development lifecycle.

Do these coding best practices work with any programming language or framework?

Yes, these best practices work universally across all languages and frameworks by focusing on fundamental principles like self-documenting code and simplicity rather than language-specific syntax.

When should I enforce coding standards during the development lifecycle?

You should enforce coding standards continuously during development, consulting guidelines when writing new features to ensure descriptive variable names, concise functions, and proper error cleanup before code reviews.