Skip to content

lootlog/monorepo / .agents/skills/engineering-rigor

engineering-rigor

Verified

Shape and verify non-trivial engineering changes that cross boundaries, alter contracts, migrate callers, or affect several workspaces. Use for architectural work, migrations, shared state, retries, public APIs, and changes where a locally correct edit may fail elsewhere.

Engineering rigor

Make the smallest complete change that reaches the intended architecture.

Shape

  • Model the domain in data structures instead of scattered conditions.
  • Concentrate parsing, validation, and framework adaptation at system boundaries.
  • Prefer deep modules with small interfaces and low reader load.
  • Remove dead code and redundant layers before adding abstractions.
  • Redesign from the requirement as a first-class constraint instead of bolting on exceptions.

Change

  • Migrate every caller and delete the legacy internal API in the same change.
  • For internal APIs, migrate callers instead of adding compatibility layers unless the user requests them. Preserve deployed and persisted contracts required by AGENTS.md, including coordinated rollout where needed.
  • Delete re-export-only wrappers and import from the owning module.
  • Separate concurrent writers before adding locks. When shared state is necessary, make operations idempotent across retries and partial failures.
  • Break wide work into verifiable units. Keep every intermediate commit or phase coherent.

Prove

  • Reproduce defects before fixing them when practical.
  • Verify the real artifact, not only a proxy such as compilation.
  • Inspect the diff and generated output.
  • Run targeted tests, typecheck, lint, and broader checks in proportion to risk.

Use blast-radius when the main risk lies outside the edited symbols.

receiving-code-reviewobra/superpowersUse when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementationStars: 319kUpdated Claude CodeCodexVerifiedInstall
requesting-code-reviewobra/superpowersUse when completing tasks, implementing major features, or before merging to verify work meets requirementsStars: 319kUpdated Claude CodeCodexVerifiedInstall
using-git-worktreesobra/superpowersUse when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallbackStars: 319kUpdated Claude CodeCodexVerifiedInstall
verification-before-completionobra/superpowersUse when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions alwaysStars: 319kUpdated Claude CodeCodexVerifiedInstall