Can I leave placeholders or TODOs in my code?

No, this skill strictly forbids placeholders and TODOs, requiring all functionality to be fully implemented and production-ready immediately.

Does this skill support different programming languages?

Yes, it provides standardized patterns and examples for multiple languages including TypeScript, Swift, and Go to ensure cross-stack consistency.

How does this skill handle testing and mocking?

It mandates real backend connections and prohibits mocking to ensure tests validate actual behavior, while requiring a 100% pass rate before any commit.

Why does this skill forbid the use of 'else' blocks?

It enforces the use of guard clauses, which reduce code indentation and cognitive load, ensuring the main logic (the 'happy path') is always at the lowest indentation level.

Production Code Standards

Name: Production Code Standards
Author: sharpner

bysharpner

•

Herramientas para Desarrolladores

Enforces high-discipline development rules including guard clauses, real-world testing, and zero-placeholder policies for production-ready codebases.

Acerca de

The Production Code Standards skill (core-rules) is designed for developers who prioritize software integrity over speed. It implements a strict architectural philosophy that eliminates nested logic through guard clauses, forbids the use of mocks in favor of real integration testing, and removes technical debt by prohibiting TODOs and placeholders. By enforcing Test-Driven Development (TDD) for bugs and requiring 100% test pass rates before commits, this skill ensures that every line of code is robust, maintainable, and ready for a production environment.

Características Principales

1 GitHub stars
Zero-tolerance policy for TODOs and placeholder implementations
TDD workflow enforcement for all bug fixes and feature development
Strict enforcement of guard clauses to eliminate nested 'else' blocks
Mandatory real backend connections by prohibiting brittle mocking
Standardized package design rules to prevent 'utils' folder clutter

Casos de Uso

Onboarding teams to a high-quality development workflow with automated guardrails
Maintaining high architectural standards in complex, multi-language codebases
Refactoring legacy code into a cleaner, more testable, and production-ready state

Acerca de

Características Principales

1 GitHub stars
Zero-tolerance policy for TODOs and placeholder implementations
TDD workflow enforcement for all bug fixes and feature development
Strict enforcement of guard clauses to eliminate nested 'else' blocks
Mandatory real backend connections by prohibiting brittle mocking
Standardized package design rules to prevent 'utils' folder clutter

Casos de Uso

Onboarding teams to a high-quality development workflow with automated guardrails
Maintaining high architectural standards in complex, multi-language codebases
Refactoring legacy code into a cleaner, more testable, and production-ready state