magia187
- 10 skills
- 0 followers
- 15 hours ago last updated
- ▌ API Compat · magia187Use when changing a public or shared API (HTTP, SDK, CLI, events). Prefer additive changes; document breaks; provide versioning or migration paths before shipping incompatible updates.
- ▌ Repro First · magia187Use when fixing a bug or investigating unexpected behavior. Reproduce the failure with a minimal failing case before changing production code, so the fix is grounded in evidence and verifiable.
- ▌ Yagni Slice · magia187Use when implementing a feature or change request. Deliver the smallest slice that satisfies the ask; refuse speculative abstractions, unused extension points, and "while we're here" work.
- ▌ Skill Author · magia187Use when creating or revising an agent skill (SKILL.md) for Claude Code, Cursor, Codex, skillcheck, or skillstack. Write a narrow, testable skill to the same quality bar as this pack — no stubs or vague prompts.
- ▌ Incident Hotfix · magia187Use during a production incident or urgent outage. Ship the minimal fix, bound blast radius, and prepare rollback; defer refactors and non-essential cleanups until the system is stable.
- ▌ Secrets Hygiene · magia187Use when committing, opening a PR, editing configs, or pasting logs. Scan diffs and config for credentials and secrets; never commit API keys, tokens, private keys, or passwords — redact and rotate if exposure is suspected.
- ▌ Test Plan First · magia187Use when starting implementation of a feature or bugfix. Write a concrete test plan and at least one failing automated test (or explicit manual cases) before changing production behavior.
- ▌ Flaky Test Triage · magia187Use when a test fails intermittently or only on CI. Decide quarantine vs fix, then stabilize with determinism (fake clocks, isolation, retries at the right layer) — never by sprinkling sleeps.
- ▌ Adversarial Review · magia187Use when reviewing a PR, patch, or design. Attack the change as a skeptic: enumerate failure modes, missing tests, unsafe defaults, and privilege edges before approving or merging.
- ▌ Perf Measure First · magia187Use when optimizing latency, throughput, memory, or bundle size. Profile or benchmark before changing code; record before/after numbers so gains are real and regressions are caught.