coding

Enforce production-grade coding standards during code changes before merging.

8|Updated Dec 16, 2008
One-click install
npx skills add https://github.com/sebnow/configs --skill coding-sebnow
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: coding
Source: https://github.com/sebnow/configs/tree/main/home-manager/agentic/skills/coding
Command: npx skills add https://github.com/sebnow/configs --skill coding-sebnow

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps ensure code changes adhere to production-grade principles, reducing defects, maintenance burden, and risk across features, fixes, refactoring, and new code.

Core Features & Use Cases

  • Pragmatism First: Choose pragmatic, reliable solutions over theoretical perfection; prefer battle-tested patterns and avoid over-optimizations.
  • Domain Aware: Use terminology aligned with the system's purpose and constraints; ensure changes fit the domain context.
  • Clarity and Legibility: Write clear, self-documenting code with straightforward control flow and meaningful names.
  • Performance: Select appropriate algorithms and data structures, measure impact, and avoid unnecessary inefficiency.
  • Correctness: Validate inputs, handle edge cases, and fail gracefully with proper error handling.

Quick Start

Follow the implementation workflow to craft a high-quality, production-ready code change.

Frequently Asked Questions about coding

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

FAQPage Schema
How do I enforce production-grade coding standards during code changes?

Enforce production-grade coding standards by applying requirements for workflow verification, code style, error handling, and domain-aware design before merging. This reduces defects and maintenance costs across feature development, bug fixes, and refactoring.

What's the best way to reduce code defects and maintenance burden in production?

To reduce code defects and maintenance burden, choose pragmatic, reliable solutions over theoretical perfection, prefer battle-tested patterns, and avoid over-optimizations. Write clear, self-documenting code with straightforward control flow and meaningful names.

How do I ensure code changes fit the domain context of my system?

Ensure code changes fit the domain context by using terminology aligned with the system's purpose and constraints. Domain-aware design requires that changes respect the domain context, reducing integration friction and improving system reliability.

Can I use production-grade coding principles for both new features and refactoring?

Yes, production-grade coding principles apply to feature development, bug fixes, refactoring, and any code changes across projects where reliability and performance matter. The standards cover correctness, performance, and clarity for all change types.

How do I handle edge cases and error handling properly in production code?

Handle edge cases and error handling in production code by validating inputs, handling edge cases, and failing gracefully with proper error handling. Select appropriate algorithms and data structures, measure performance impact, and avoid unnecessary inefficiency.

When should I prioritize pragmatism over theoretical perfection in code style?

Prioritize pragmatism over theoretical perfection whenever production reliability matters. Choose pragmatic, reliable solutions, prefer battle-tested patterns, and avoid over-optimizations that add complexity without measurable performance benefit.