Claude Skills by balanced7

Use whenever you work in the Akashic Aurora repo (E:\AI-Setup) — at session start, after ANY fix that first failed, whenever the user corrects you, and at session end. This is the shared-memory door; capture is the product, so use it even when the task feels too small to record. Also use when deciding whether knowledge belongs in a lesson, a note, a doc, or a hook.

Use when designing an implementation plan, scoping a slice, starting any multi-step task, or before writing significant code — and use it BEFORE the first Edit, not after. Planning is the highest-leverage review point: a bad plan line becomes hundreds of bad code lines.

Use when encountering any bug, test failure, hook misbehavior, or unexpected output — BEFORE proposing or applying any fix, even a one-liner that looks obvious. Also use when a fix you tried didn't work, and especially after a third failed attempt.

Use when about to claim any work is complete, fixed, passing, or shipped — before saying "done", "should work now", "that fixes it", or committing. Also use at the end of every slice, before wrap/handoff, and whenever you notice you are asserting an outcome you have not freshly observed.

Use whenever you work in the Akashic Aurora repo (E:\AI-Setup) — at session start, after ANY fix that first failed, whenever the user corrects you, and at session end. This is the shared-memory door; capture is the product, so use it even when the task feels too small to record. Also use when deciding whether knowledge belongs in a lesson, a note, a doc, or a hook.

Use when designing an implementation plan, scoping a slice, starting any multi-step task, or before writing significant code — and use it BEFORE the first Edit, not after. Planning is the highest-leverage review point: a bad plan line becomes hundreds of bad code lines.

Use when encountering any bug, test failure, hook misbehavior, or unexpected output — BEFORE proposing or applying any fix, even a one-liner that looks obvious. Also use when a fix you tried didn't work, and especially after a third failed attempt.

Use when about to claim any work is complete, fixed, passing, or shipped — before saying "done", "should work now", "that fixes it", or committing. Also use at the end of every slice, before wrap/handoff, and whenever you notice you are asserting an outcome you have not freshly observed.