abstractonion

abstractonion/cadence

Skill Claude CodeCodex

Use when writing import statements — keep them at the top of the file; do not drop imports inside functions or class methods to work around typing or ordering issues.

abstractonion/cadence

Skill Claude CodeCodex

Use when a bug, failing test, or unexpected behavior appears — trace the root cause before patching the symptom; cap hypothesis attempts at three before surfacing.

abstractonion/cadence

Skill Claude CodeCodex

Use when multiple agents or long-running tasks need the same repo without disturbing the main checkout — create a sibling git worktree.

abstractonion/cadence

Skill Claude CodeCodex

Use when files grow past a few hundred lines or accumulate unrelated responsibilities — split by concern rather than adding to the large file.

abstractonion/cadence

Skill Claude CodeCodex

Use for any non-trivial change to move it through the seven-phase engineering loop — think, plan, build, review, test, ship, reflect.

abstractonion/cadence

Skill Claude CodeCodex

Use during long sessions to avoid context degradation — read narrowly, delegate heavy reads, checkpoint progress, and hand off rather than push through polluted context.

abstractonion/cadence

Skill Claude CodeCodex

Use when adding TypeScript modules — prefer named exports; avoid export default except where a framework explicitly requires it.

abstractonion/cadence

Skill Claude CodeCodex

Use when generated code (OpenAPI clients, GraphQL types, protobuf, migrations, etc.) looks wrong — change the source schema or template and regenerate, never hand-edit the output.

abstractonion/cadence

Skill Claude CodeCodex

Use when writing or reviewing TypeScript code that would otherwise reach for any or as to silence the type checker — find the real type instead.

abstractonion/cadence

Skill Claude CodeCodex

Use when a backend test or eval fails — fix it at the edges (test, fixture, feature code); do not modify central settings, base classes, middleware, or shared fixtures to make it pass.

abstractonion/cadence

Skill Claude CodeCodex

Use when modeling lifecycle or state — represent distinct conceptual states with explicit enums or unions instead of collapsing them onto "", 0, None, or null.

abstractonion/cadence

Skill Claude CodeCodex

Use when writing TypeScript nullability checks — prefer == null / != null to match both null and undefined; use strict equality everywhere else.