What are the logging conventions used by this skill?

It mandates progress logging every 15-60 seconds for long operations and follows a specific naming convention: logs/{adr-id}-YYYYMMDD_HHMMSS.log.

When should I use the Core Implementation Standards skill?

It is best used during the implementation phase of a feature, before a release, or whenever you are addressing error handling and code quality.

What is the primary goal of the impl-standards skill?

The primary goal is to ensure that code follows professional engineering standards, specifically regarding error propagation, constants management, and observability.

How does this skill handle error management?

It enforces a 'Raise + Propagate' rule, meaning errors are explicitly raised with context rather than being silently caught or ignored with fallback values.

Does it help with magic numbers in code?

Yes, it identifies magic numbers and provides patterns to abstract them into semantic, named constants to improve code readability and maintainability.

Core Implementation Standards

Name: Core Implementation Standards
Author: terrylica

byterrylica

•

개발자 도구

Enforces high-quality engineering standards and production-grade patterns during feature implementation.

소개

The Core Implementation Standards skill ensures that code generated or refactored by Claude follows professional engineering best practices. It focuses on critical areas such as robust error propagation, the elimination of magic numbers through semantic constants, and standardized progress logging for long-running operations. By applying these rules, developers can maintain consistent code quality, improve observability with structured logging conventions, and ensure that all production code is maintainable and resilient.

주요 기능

Standardizes progress logging for operations exceeding one minute
Implements a consistent log file naming convention for traceability
Abstracts magic numbers into semantic, version-agnostic constants
Provides automated guidance for production-ready code quality
2 GitHub stars
Enforces 'Raise + Propagate' error handling to prevent silent failures

사용 사례

Refactoring legacy codebases to remove hardcoded values and improve error handling
Transitioning experimental or prototype code into production-grade software
Standardizing logging and observability across complex backend services

소개

주요 기능

Standardizes progress logging for operations exceeding one minute
Implements a consistent log file naming convention for traceability
Abstracts magic numbers into semantic, version-agnostic constants
Provides automated guidance for production-ready code quality
2 GitHub stars
Enforces 'Raise + Propagate' error handling to prevent silent failures

사용 사례

Refactoring legacy codebases to remove hardcoded values and improve error handling
Transitioning experimental or prototype code into production-grade software
Standardizing logging and observability across complex backend services