| description | Router for engineering knowledge — the language-agnostic code baseline (naming, style, boring-code, design) plus deep runbooks for tests, Docker images, CI Makefiles, deploys, observability, Python tool distribution. NOT for language-specific idioms (use go/rs/py/ts/sh/sql) or terse Docker/systemd rules (ops keeps those hot). |
| when_to_use | writing or reviewing code in any language, naming a function or variable, boring code, abstraction discipline, explicit over clever, over-engineering, complected code, line width, file layout; writing tests, debugging test failures, reading test output, testcontainers, smoke tests, e2e tests, test hangs; Python uv Dockerfile, m4 monorepo image, .dockerignore, Ansible docker-service role, deploy a service, Makefile for uv, CI make targets, logging format, Prometheus metrics, SLO burn-rate alerts, error-handling hierarchy, distribute a Python tool, PEP 723 script, uvx; strict typing config, ban Any, basedpyright pyright ruff tsconfig eslint strict flags, no-explicit-any, ban type ignore, un-circumventable types, which linters to run/build, golangci-lint, go lint set, nolintlint, errcheck, staticcheck, govet; race detector, data race, sanitizer, ASan TSan MSan LSan, Miri, fuzzing, go test -race, cargo nextest, cargo careful, loom, cargo-fuzz cargo-mutants, memory checker, leak detector, goleak, hypothesis property testing, pytest-memray, python -X dev, ThreadSanitizer, valgrind alternative, dynamic analysis test targets |