Plugin Claude Code
Engineering discipline skills: grounding before coding, failure handling, one source of truth, verification, operational safety, and scoping.
1 2d ago A
tokens not measured
Plugin Claude Code
Engineering discipline as skills: evidence over theory, no silent error swallows, one source of truth, verification as the definition of done, operational safety, and fixes sized to their trigger.
1 2d ago A
tokens not measured
Agent
Independent verifier for completion claims. Use before any done, fixed, or passing claim ships, when a change's verification must not rest on the author's own account, or when a green suite needs distrusting. Verifies and reports; never fixes what it finds.
1 2d ago A 56 tokens
preflight
28Command
Run the pre-change checkpoint before starting a change.
1 2d ago A 9 tokens
verify
29Command
Independently verify a completion claim before it ships.
1 2d ago A 10 tokens
Skill Claude CodeCodex
Use when about to add, update, vet, or remove a dependency - a package, library, SDK, GitHub action, base image, or vendored code - or when a project's dependency posture needs declaring. Encodes the exhaust-what-you-have ladder, the vetting questions, and pin-and-prove updating. Use even for a tiny utility package…
1 2d ago A 85 tokens
Skill Claude CodeCodex
Use when starting any non-trivial change, investigating a bug, or working in unfamiliar code - before the first line is written. Also use for pure investigation with no change planned yet - "dig into this", "figure out why", "sometimes the export is empty", intermittent errors after a deploy. Encodes the ground-first…
1 2d ago A 112 tokens
Skill Claude CodeCodex
Use when a change crosses module boundaries, adds a dependency direction between modules, touches a critical path, or conflicts with a stated principle - and when writing or updating architecture principles themselves. Encodes structural invariants as named, enforced contracts: statement, rationale, guard. Use…
1 2d ago A 79 tokens
Skill Claude CodeCodex
Use when writing or touching any error path, catch block, fallback, default value, retry, or degraded mode - in any language, any repo. Encodes the no-silent-swallows contract and the fail-loud discipline. Use whenever an exception is about to be caught, a null is about to get a default, or a failure could pass…
1 2d ago A 90 tokens
Skill Claude CodeCodex
Use when adding data, config, state, constants, an enum-like string, a cache, or anything that could exist in two places - or when two sources already disagree. Encodes the one-fact-one-source doctrine for code and data: derive rather than store, extend the owner, absorb duplicates. Use at the moment copying a value…
1 2d ago A 81 tokens
Skill Claude CodeCodex
Use when an action touches live systems, shared state, or things that do not come back - deleting, overwriting, restarting, killing processes, editing shared config, handling secrets, or working beside concurrent sessions. Encodes the destructive-op guards, secrets hygiene, and concurrent-session safety. Use before…
1 2d ago A 79 tokens
Skill Claude CodeCodex
Use when doing any non-trivial engineering work - implementing, debugging, refactoring, configuring, operating, or investigating why a system misbehaves - or any change where being wrong has a cost. Encodes the evidence-over-theory discipline, the hard safety rules, and the pre-change checkpoint. Use whenever code…
1 2d ago A 104 tokens
Skill Claude CodeCodex
Use when deciding how big a fix should be, when scope is drifting mid-task, when a plan is being quietly trimmed to fit, or when "while you're at it" appears in any form. Encodes size-to-trigger, decompose-not-descope, and drive-to-completion. Use whenever the work is about to grow past its cause or shrink below its…
1 2d ago A 80 tokens
Skill Claude CodeCodex
Use when deciding what tests a change needs - a feature, a bug fix, a refactor, any behavior change - or when reviewing whether a diff's tests are sufficient. Encodes tests-change-with-behavior, the bug-regression pattern, and assertion discrimination. Use whenever behavior changes and the test diff is empty…
1 2d ago A 80 tokens
Skill Claude CodeCodex
Use when about to say "done", "fixed", "passing", or "shipped" - or when reporting the outcome of any change. Encodes verification as the definition of done: drive the change at its surface, run the verify command, report faithfully, distrust green suites, own failing gates. Use before every completion claim, even…
1 2d ago A 90 tokens
Skill Claude CodeCodex
Use when writing or refactoring unit tests - a new test file, added cases, a flaky test, an unreadable one. Encodes behavior-first testing: one behavior per test, names that state the claim, deterministic setup, mocks only at boundaries you do not own. Use whenever a test is being written, even a quick one, and…
1 2d ago A 96 tokens