impl-standards

Enforce production code standards for error handling, constants, and logging.

62|10|Updated Dec 4, 2025
One-click install
npx skills add https://github.com/terrylica/cc-skills --skill impl-standards
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: impl-standards
Source: https://github.com/terrylica/cc-skills/tree/main/plugins/itp/skills/impl-standards
Command: npx skills add https://github.com/terrylica/cc-skills --skill impl-standards

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Inconsistent coding practices, poor error handling, and unmanaged constants lead to brittle, hard-to-maintain codebases. This skill provides a set of core engineering standards to ensure high-quality, consistent, and maintainable production code.

Core Features & Use Cases

  • Robust Error Handling: Enforces a "raise and propagate" policy, preventing silent failures and ensuring clear error visibility.
  • Semantic Constants Management: Guides on abstracting magic numbers into meaningful, version-agnostic constants for improved readability and maintainability.
  • Dependency Management: Promotes the use of battle-tested open-source libraries over custom implementations.
  • Progress Logging & Metadata: Standardizes logging for long-running operations and suggests optional metadata for service discovery.
  • Use Case: When developing a new feature, apply these standards to ensure your code is resilient to errors, easy to understand, and integrates seamlessly into the existing system, reducing future debugging and refactoring efforts.

Quick Start

Implement the new feature following the core engineering standards. Pay special attention to error handling and constants management.

Frequently Asked Questions about impl-standards

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

FAQPage Schema
How do I enforce consistent error handling in production code?

Error handling standards enforce a raise-and-propagate policy that prevents silent failures. Add context when raising errors and propagate them up the call stack so failures are visible and actionable rather than hidden.

What's the best way to manage magic numbers and constants in code?

Replace magic numbers with semantic named constants that clearly express intent and meaning. Use configuration-driven values for version-agnostic settings, improving readability and making future changes easier without touching business logic.

When should I apply coding standards during feature development?

Apply implementation standards when writing new production features, especially during error handling, constants management, and progress logging. Standards also apply before release and quality checks to ensure maintainability and robustness.

How do I log long-running operations correctly?

Progress logging standards require logging every 15–60 seconds for long operations to track execution flow. Use the log convention logs/{adr-id}-YYYYMMDD_HHMMSS.log to create consistent, timestamped records for debugging and monitoring.

Should I build custom solutions or use open-source libraries?

Dependency standards favor battle-tested open-source libraries over custom implementations. OSS libraries reduce maintenance burden, improve code quality, and leverage community-validated solutions for common problems.

What metadata should I include for service discovery?

Optional catalog-info.yaml metadata improves service discovery and integration. Include this alongside core standards for error handling, constants, and logging to support team tooling and system integration.