code-quality-standards

Included with Lifetime

$97 forever

Use when writing or reviewing code and documentation

Writing & Docs

What this skill does


# Code Quality Standards

## Core Principles

- **Readability**: Clear, self-documenting code. Clarity over cleverness.
- **Naming**: Descriptive, concise names for variables, functions, classes.
- **DRY**: Encapsulate reusable logic. Define once, reference everywhere.
- **Comments**: Explain *why*, not *what*.
- **Security**: No hardcoded secrets. Least privilege. Validate all input.
- **TDD**: Write failing tests before implementation. Red-green-refactor.
- **Idempotency**: Operations must be safely repeatable with consistent results.

## Language Rules

### Python

- Follow PEP 8. Use type hints for all function signatures.
- Write docstrings for all functions/classes/modules.
- Use `logging` module, never `print()`.
- Pin dependencies for apps (lock file); use ranges for libraries.
- Run `black`, `flake8`, `mypy` before committing.

### Bash / Shell

- **NEVER use Bash for file operations** — use Read/Edit/Write/Grep/Glob tools.
- **NEVER use `for` loops** — breaks permission matching, requires interactive
  prompts. Use parallel tool calls or tool-native batch operations instead.
- **NEVER generate scripts** — execute commands directly via tool calls.
- Prefer parallel tool calls for independent commands.

### JavaScript / TypeScript

- Use TypeScript for all new JS code. Prefer `const` over `let`, avoid `var`.
- Implement proper error boundaries in React components.

## Logging Standards

Format: `YYYY-MM-DD HH:mm:ss [LEVEL] {message}`

| Level | Use |
| --- | --- |
| ERROR | System failures, exceptions requiring attention |
| WARN | Unexpected but recoverable conditions |
| INFO | Normal operational messages |
| DEBUG | Detailed diagnostic information |

Include context (operation, user, resource). Never log secrets.

## Testing Philosophy

Prefer **continuous real-time monitoring** over one-time tests.

| Use Continuous Monitoring | Use One-Time Tests |
| --- | --- |
| Services with health endpoints | IaC validation (`terraform validate`) |
| Long-running infrastructure | Linting/formatting (pre-commit) |
| Anything that can fail post-deploy | Unit tests (TDD cycle) |

Monitoring MUST proactively alert. Alerting channels (priority order):
Slack, Splunk alerts, email. Silent dashboards are not monitoring.

## Documentation Format

- Use standard Markdown with proper syntax highlighting.
- Hierarchical numbering (1., 1.1., 1.1.1.) for structured content.
- Link to other docs instead of duplicating (DRY).
- Keep docs concise — AI-first, humans second.
- All Markdown validated by `markdownlint-cli2` via pre-commit hooks.

## Related Skills

- **review-standards** (code-standards) — Use when performing formal code review on PRs
- **pr-standards** (git-standards) — PR & issue standards, PR guards, issue linking

Files: 1

Size: 2.8 KB

Complexity: 5/100

Category: Writing & Docs

Source: https://github.com/jacobpevans/claude-code-plugins/tree/main/code-standards/skills/code-quality-standards

Related in Writing & Docs

jax-development

Included

Use this skill when the user is writing, debugging, profiling, refactoring, reviewing, benchmarking, parallelising, exporting, or explaining JAX code, or when they mention JAX, jax.numpy, jit, grad, value_and_grad, vmap, scan, lax, random keys, pytrees, jax.Array, sharding, Mesh, PartitionSpec, NamedSharding, pmap, shard_map, Pallas, XLA, StableHLO, checkify, profiler, or the JAX repo. It helps turn NumPy or PyTorch-style code into pure functional JAX, fix tracer/control-flow/shape/PRNG bugs, remove recompiles and host-device syncs, choose transforms and sharding strategies, inspect jaxpr/lowering/IR, and benchmark compiled code correctly.

Writing & Docsscripts

nature-article-writer

Included

Drafts, rewrites, diagnostically critiques, and style-calibrates primary research manuscripts for Nature and Nature Portfolio journals. Use when the user wants a Nature-style title, summary paragraph or abstract, introduction, results, discussion, methods, figure legends, presubmission enquiry, cover letter, reviewer response, or when a scientific draft sounds generic, jargon-heavy, structurally weak, or AI-ish and needs precise, broad-reader-friendly prose without inventing data, analyses, or references. Best for primary research articles and letters rather than reviews or press releases unless explicitly adapting one.

Writing & Docsscripts

deckrd

Included

Document-driven framework that derives requirements, specifications, implementation plans, and executable tasks from goals through structured AI dialogue. Use when user says "write requirements", "create spec", "plan implementation", "derive tasks", "structure this feature", "break down into tasks", or "document this module". Also use for reverse engineering existing code into docs (/deckrd rev). Do NOT use for direct code writing — use /deckrd-coder after tasks are generated. Do NOT use when the user only wants to run or fix existing code without planning.

Writing & Docsscripts

clinical-decision-support

Included

Generate professional clinical decision support (CDS) documents for pharmaceutical and clinical research settings, including patient cohort analyses (biomarker-stratified with outcomes) and treatment recommendation reports (evidence-based guidelines with decision algorithms). Supports GRADE evidence grading, statistical analysis (hazard ratios, survival curves, waterfall plots), biomarker integration, and regulatory compliance. Outputs publication-ready LaTeX/PDF format optimized for drug development, clinical research, and evidence synthesis.

Writing & Docsscripts

handling-sf-data

Included

Salesforce data operations with 130-point scoring. Use this skill to create, update, delete, bulk import/export, generate test data, and clean up org records using sf CLI and anonymous Apex. TRIGGER when: user creates test data, performs bulk import/export, uses sf data CLI commands, needs data factory patterns for Apex tests, or needs to seed/clean records in a Salesforce org. DO NOT TRIGGER when: SOQL query writing only (use querying-soql), Apex test execution (use running-apex-tests), or metadata deployment (use deploying-metadata).

Writing & Docsscripts

accelint-ac-to-playwright

Included

Convert and validate acceptance criteria for Playwright test automation. Use when user asks to (1) review/evaluate/check if AC are ready for automation, (2) assess if AC can be converted as-is, (3) validate AC quality for Playwright, (4) turn AC into tests, (5) generate tests from acceptance criteria, (6) convert .md bullets or .feature Gherkin files to Playwright specs, (7) create test automation from requirements. Handles both bullet-style markdown and Gherkin syntax with JSON test plan generation and validation.

Writing & Docsscripts