skills.rest
nikblanchet
nikblanchetCOMMUNITY
Explore all skills by this author →
GitHub

development-standards

Enforce development standards across code, documentation, commits, and pull requests.

Updated Nov 19, 2025
Search Tags:#code quality#documentation#coding standards#professionalism#language features#developer communication#emoji policy
One-click install
npx skills add https://github.com/nikblanchet/claude-code-production-patterns --skill development-standards
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: development-standards
Source: https://github.com/nikblanchet/claude-code-production-patterns/tree/main/actual-code/skills/user/development-standards
Command: npx skills add https://github.com/nikblanchet/claude-code-production-patterns --skill development-standards

SYSTEM DOCUMENTATION & REQUIREMENTS

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.

Frequently Asked Questions about development-standards

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

FAQPage Schema
How do I enforce consistent coding standards across my team's pull requests and commits?▼

Enforce coding standards by establishing a no-emoji policy in developer-facing content, requiring thorough documentation for all code, and promoting modern language features. Review pull requests and commits against these standards before merging to maintain professionalism and clarity across your codebase.

Why should I avoid emoji in code, documentation, and commits?▼

Emoji in developer-facing content undermines professionalism, creates maintenance friction during code reviews, and can signal low-quality or AI-generated output. Text-based formatting ensures clarity and consistency across all development workflows.

What documentation standards should I require for code quality?▼

Require thorough, accurate, and timely documentation for all code—in comments, README files, and pull request descriptions. Clear documentation makes your codebase easier to understand, maintain, and review, improving team collaboration and reducing onboarding time.

How do I encourage modern language features without sacrificing code readability?▼

Adopt cutting-edge language features when they improve clarity and elegance rather than complexity. During code reviews, promote modern syntax and patterns that keep your codebase efficient while maintaining team understanding and maintainability.

What should I check before submitting a pull request to meet development standards?▼

Before submitting, verify that your code uses clear, text-based formatting without emoji, includes comprehensive documentation, adopts modern language features where beneficial, and adheres to your team's professionalism standards. Request a standards review to catch issues early.

Related Skills

Explore More Software Engineering Skills→
xotongxotong

lint-and-validate

Run linters, formatters, and type checkers on code changes before commits.

Community
Intermediate
koralliskorallis
90

standards-enforcement

Configure ESLint, Prettier, and Husky to enforce coding standards.

Community
Intermediate
paxlabs-incpaxlabs-inc
7

requesting-code-review

Automate pre-commit code verification with static security analysis and subagent review.

Community
Advanced
ProteoWizardProteoWizard
17

version-control

Enforce team-specific Git commit formats and gate commits, pushes, and pull requests.

Official
Intermediate