Skip to main content
skill CX Codex

impl-standards — Claude Code skill: what it does, how to install

impl-standards — a set of coding rules: error propagation, constant extraction, progress logging for long operations, and dependency injection patterns.

MIT 126 installs ★ 3 updated 2026-10-25

Install into Claude Code · Skills CLI (Vercel) All methods and platforms ↓
npx skills add terrylica/cc-skills --skill impl-standards -a claude-code
Open on GitHub

What impl-standards does

Triggers on mentions of error handling, constants, magic numbers, progress logging, SSoT, or dependency injection. Provides a standards table: raise and propagate errors without fallback, extract magic numbers into semantic constants, log progress every 15–60 seconds for operations over one minute. Recommends config singleton with None default, resolver chain, and entry-point validation. Logs go to logs/{adr-id}-YYYYMMDD_HHMMSS.log.

Includes Python examples, links to three references (error handling, constants management, SSoT/DI), and a troubleshooting table covering silent failures, magic numbers, and type errors. For ML pipelines, prefers Polars over Pandas except where MLflow requires Pandas. Available commands: Read, Grep, Glob. Check allowed-tools before use — no external dependencies or API keys needed.

What it helps with

  • Extract magic numbers into named constants
  • Add progress logging to a long-running operation
  • Raise and propagate an error instead of silent catch
  • Switch from Pandas to Polars in a new pipeline
  • Audit code for hardcoded values before release

Example prompts for the agent

  • Show me how to handle a request error following impl-standards
  • Extract the timeout 30 into a constant per the skill rules
  • Add progress logging every 30 seconds to this processing loop

How to install impl-standards

1Skills CLI (Vercel)

npx skills add terrylica/cc-skills --skill impl-standards -a claude-code

2Manually: put the files in place

~/.claude/skills/impl-standards/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/impl-standards/

Step by step, with commands for each platform: How to install skills in Claude Code: five ways

Questions about impl-standards

How to install impl-standards in Claude Code?

Run npx skills add terrylica/cc-skills --skill impl-standards -a claude-code, and the skill will appear at ~/.claude/skills/impl-standards/SKILL.md.

What does impl-standards do?

Provides rules for error handling (raise + propagate), constants (extract magic numbers), progress logging (every 15–60 seconds in operations over a minute), config (singleton with None default), and library choice (Polars over Pandas).

When does the skill activate?

On mentions of error handling, constants, magic numbers, progress logging, SSoT, dependency injection, config singleton, or before release to verify code quality.

Source text

SKILL.md · MIT
---
name: impl-standards
description: Core engineering standards for implementation. TRIGGERS - error handling, constants management, progress logging, code quality.
allowed-tools: Read, Grep, Glob
---

# Implementation Standards

Apply these standards during implementation to ensure consistent, maintainable code.

> **Self-Evolving Skill**: This skill improves through use. If instructions are wrong, parameters drifted, or a workaround was needed — fix this file immediately, don't defer. Only update for real, reproducible issues.

## When to Use This Skill

- During `/itp:go` Phase 1
- When writing new production code
- User mentions "error handling", "constants", "magic numbers", "progress logging", "SSoT", "dependency injection", "config singleton"
- Before release to verify code quality

## Quick Reference

| Standard         | Rule                                                                     |
| ---------------- | ------------------------------------------------------------------------ |
| **Errors**       | Raise + propagate; no fallback/default/retry/silent                      |
| **Constants**    | Abstract magic numbers into semantic, version-agnostic dynamic constants |
| **SSoT/DI**      | Config singleton → None-default + resolver → entry-point validation      |
| **Dependencies** | Prefer OSS libs over custom code; no backward-compatibility needed       |
| **Progress**     | Operations >1min: log status every 15-60s                                |
| **Logs**         | `logs/{adr-id}-YYYYMMDD_HHMMSS.log` (nohup)                              |
| **Metadata**     | Optional: `catalog-info.yaml` for service discovery                      |

---

## Error Handling

**Core Rule**: Raise + propagate; no fallback/default/retry/silent

```python
# ✅ Correct - raise with context
def fetch_data(url: str) -> dict:
    response = requests.get(url)
    if response.status_code != 200:
        raise APIError(f"Failed to fetch {url}: {response.status_code}")
    return response.json()

# ❌ Wrong - silent catch
try:
    result = fetch_data()
except Exception:
    pass  # Error hidden
```

See [Error Handling Reference](./references/error-handling.md) for detailed patterns.

---

## Constants Management

**Core Rule**: Abstract magic numbers into semantic constants

```python
# ✅ Correct - named constant
DEFAULT_API_TIMEOUT_SECONDS = 30
response = requests.get(url, timeout=DEFAULT_API_TIMEOUT_SECONDS)

# ❌ Wrong - magic number
response = requests.get(url, timeout=30)
```

See [Constants Management Reference](./references/constants-management.md) for patterns.

---

## Progress Logging

For operations taking more than 1 minute, log status every 15-60 seconds:

```python
import logging
from datetime import datetime

logger = logging.getLogger(__name__)

def long_operation(items: list) -> None:
    total = len(items)
    last_log = datetime.now()

    for i, item in enumerate(items):
        process(item)

        # Log every 30 seconds
        if (datetime.now() - last_log).seconds >= 30:
            logger.info(f"Progress: {i+1}/{total} ({100*(i+1)//total}%)")
            last_log = datetime.now()

    logger.info(f"Completed: {total} items processed")
```

---

## Log File Convention

Save logs to: `logs/{adr-id}-YYYYMMDD_HHMMSS.log`

```bash
# Running with nohup
nohup python script.py > logs/2025-12-01-my-feature-20251201_143022.log 2>&1 &
```

---

---

## Data Processing

**Core Rule**: Prefer Polars over Pandas for dataframe operations.

| Scenario           | Recommendation                     |
| ------------------ | ---------------------------------- |
| New data pipelines | Use Polars (30x faster, lazy eval) |
| ML feature eng     | Polars → Arrow → NumPy (zero-copy) |
| MLflow logging     | Pandas OK (add exception comment)  |
| Legacy code fixes  | Keep existing library              |

**Exception mechanism**: Add at file top:

```python
# polars-exception: MLflow requires Pandas DataFrames
import pandas as pd
```

See [ml-data-pipeline-architecture](/plugins/devops-tools/skills/ml-data-pipeline-architecture/SKILL.md) for decision tree and benchmarks.

---

## Related Skills

| Skill                                                                                                  | Purpose                                |
| ------------------------------------------------------------------------------------------------------ | -------------------------------------- |
| [`adr-code-traceability`](../adr-code-traceability/SKILL.md)                                           | Add ADR references to code             |
| [`code-hardcode-audit`](../code-hardcode-audit/SKILL.md)                                               | Detect hardcoded values before release |
| [`ml-data-pipeline-architecture`](/plugins/devops-tools/skills/ml-data-pipeline-architecture/SKILL.md) | Polars/Arrow efficiency patterns       |

---

## Reference Documentation

- [Error Handling](./references/error-handling.md) - Raise + propagate patterns
- [Constants Management](./references/constants-management.md) - Magic number abstraction
- [SSoT / Dependency Injection](./references/ssot-dependency-injection.md) - Config singleton → None-default → resolver chain

---

## Troubleshooting

| Issue                  | Cause                | Solution                                   |
| ---------------------- | -------------------- | ------------------------------------------ |
| Silent failures        | Bare except blocks   | Catch specific exceptions, log or re-raise |
| Magic numbers in code  | Missing constants    | Extract to named constants with context    |
| Error swallowed        | except: pass pattern | Log error before continuing or re-raise    |
| Type errors at runtime | Missing validation   | Add input validation at boundaries         |
| Config not loading     | Hardcoded paths      | Use environment variables with defaults    |

## Post-Execution Reflection

After this skill completes, check before closing:

1. **Did the command succeed?** — If not, fix the instruction or error table that caused the failure.
2. **Did parameters or output change?** — If the underlying tool's interface drifted, update Usage examples and Parameters table to match.
3. **Was a workaround needed?** — If you had to improvise (different flags, extra steps), update this SKILL.md so the next invocation doesn't need the same workaround.

Only update if the issue is real and reproducible — not speculative.

© terrylica · MIT · terrylica/cc-skills

Similar skills

All skills for Code review and refactoring →

From the same set79

The whole set →
asciinema-analyzer The asciinema-analyzer skill searches asciinema text recordings for keywords, commands, errors, and patterns. Use it when reviewing terminal session history. CX Codex +1 127installs research-archival research-archival scrapes AI research conversations and web pages, saves them as markdown with YAML frontmatter, and opens cross-referenced GitHub issues once the writing account is confirmed. CX Codex +1 127installs iterm2-layout iterm2-layout configures iTerm2 workspace layouts, panes, and tabs using a TOML file. Helps an AI agent register project directories and auto-discover git worktrees. CX Codex +1 126installs asciinema-player asciinema-player — a skill for Claude Code and five other platforms that plays .cast terminal recordings inside a dedicated iTerm2 window. Files over 100 MB crash browser players; this skill streams them from disk. CX Codex +1 126installs bootstrap-monorepo bootstrap-monorepo scaffolds a polyglot monorepo using moon, proto, and Bun with a TypeScript control plane and strict boundary rules. CX Codex +1 126installs asciinema-converter asciinema-converter turns asciinema .cast recordings into clean .txt files for reading and search. It handles one file or a directory batch. CX Codex +1 126installs multi-agent-performance-profiling multi-agent-performance-profiling spawns five parallel profiling agents to investigate system layers: instrumentation, database config, client library, batch sizing, and synthesis. CX Codex +1 126installs clickhouse-cloud-management clickhouse-cloud-management manages ClickHouse Cloud database users and access permissions using SQL statements over HTTPS. CX Codex +1 126installs

Project sponsors

Companies that keep this analytics open