Claude Skills by altafino

Angular guardrails pack — signals, change detection, @for track, RxJS teardown, standalone defaults, plus UI state/a11y discipline. Use when writing Angular components, templates, or services.

Audit guardrails-kit compliance of the current session — run the transcript marker scorecard. Use when asked to audit compliance, check which guardrail rules fired or were missed, or score the session.

Force the guardrails debugging discipline — reproduce first, CAUSE line, failed-attempts ledger, escalation ladder. Use when debugging is flailing, the same fix keeps failing, or asked to debug systematically.

Health-check the installed guardrails kit — markers, doc set, versions, STATE.md shape, drift. Use when asked to check the kit installation, diagnose guardrails problems, or after upgrading the kit.

Go guardrails pack — typed-nil interfaces, slice aliasing, maps, defer, goroutine/channel traps, JSON pitfalls. Use when writing or reviewing Go code.

Install or upgrade the guardrails kit into a project with an existing CLAUDE.md by executing MIGRATE.md exactly. Use when asked to migrate a CLAUDE.md, install the kit, or retrofit guardrails into a project.

NoSQL guardrails pack — MongoDB $set/replace and schema drift, Redis SCAN/TTL/atomicity, eventual consistency. Use when writing MongoDB, Redis, DynamoDB, or other non-relational store code.

Performance guardrails pack — N+1, complexity notes, measure-before/after, unbounded growth, pagination, hot-path I/O. Use when asked for a performance pass or when optimizing/reviewing query and loop cost.

Force the guardrails planning gate before non-trivial work — TASK block, premise check, prior-art search, baseline. Use when asked to plan a change properly or when edits are starting without a posted plan.

Post-compaction/resume recovery for the guardrails kit — re-run the SESSION.md S1 sequence manually. Use after a compaction, /resume, or when session context feels lost or stale.

Reasoning scaffolds pack — worked-example traces, counterexample hunts, invariants, options enumeration. Use when writing algorithms, recursion, parsers, state machines, index math, or choosing between design approaches.

Security guardrails pack — injection, secrets, path traversal, auth defaults, deserialization, untrusted-content discipline. Use when asked for a security pass or when code touches user input, secrets, or auth.

SQL guardrails pack — NULL logic and JOIN traps, destructive-operation discipline, injection, query cost. Use when writing SQL, query-builder calls, ORM queries, or database migrations.

Create or refresh docs/STATE.md before pausing, stopping, compaction, or handoff — guardrails session state. Use when asked to save state, checkpoint the session, or wrap up for the day.

Tailwind CSS guardrails pack — dynamic class purging, v4 CSS-first config, @apply/@reference, arbitrary values. Use when writing Tailwind utility classes or Tailwind configuration.

Testing guardrails pack — test authorship quality, regression-proof discipline, expectation-change audit. Use when writing tests, adding coverage, or reviewing test quality.

Force the guardrails VERIFY echo protocol — prove every done/fixed/works claim with quoted command output. Use when asked to verify claims, check completion evidence, prove it works, or when "done" was claimed without proof.

Vue 3 guardrails pack — reactivity loss, ref unwrapping, v-if/v-for precedence, compiler macros, plus UI state/a11y discipline. Use when writing Vue single-file components or composables.