development-standards

What problem does it solve?

Inconsistent coding styles, unclear documentation, and unprofessional communication can hinder collaboration and signal low quality. This Skill establishes critical development standards, including a strict "no emoji" policy for developer-facing content, promoting clarity, professionalism, and maintainability, which streamlines code reviews and improves team efficiency.

Core Features & Use Cases

• No Emoji Policy: Enforces the absence of colorful emoji in code, commits, PRs, and CLI output to maintain professionalism and avoid signaling AI-generated content.
• Modern Language Adoption: Encourages the use of cutting-edge language features when they improve clarity and elegance, keeping your codebase modern and efficient.
• Comprehensive Documentation: Mandates thorough, accurate, and timely documentation for all code, making it easier for others (and your future self) to understand and maintain.
• Use Case: A developer is drafting a pull request description. This skill reminds them to use clear, text-based formatting, avoid emoji, and ensure their code and documentation adhere to the project's high standards, streamlining review and improving team communication.

Quick Start

Before submitting a pull request, ask me to "Review my code and documentation against development standards." I will check for emoji usage, modern language features, and documentation thoroughness.