Claude Skills by lawzava

Use when an approved goal must continue unattended across many steps, milestones, context resets, or sessions.

Use when a code structure, API, error, concurrency, or idiom decision is not settled by the repository or its configured tools.

Use when behavior or an interface needs a specification, requirements need tradeoffs, or approved work needs a multi-step plan.

Use when a decision needs evidence beyond the repository, including current product research, historical rationale, cross-system incident history, or contested reports.

Use when the user asks to be grilled, or wants a plan, decision, idea, or draft stress-tested through a structured interview before any action.

Use when the task itself is to draft, rewrite, edit, or preserve human-facing prose for clarity, attribution, or proportion; do not select merely because other work ends with a response.

Use when security, auth, billing, concurrency, data integrity, or another high-stakes artifact needs adversarial review by a provider other than its author.

Use when installing, configuring, debugging, or verifying an MCP server for a harness, or when a configured server's tools are missing or failing.

Use when auditing, pruning, correcting, refreshing, or automatically applying approved evidence-based cleanup to native harness memory.

Use when two or more independent lanes can run in parallel, an output-only lane protects lead context from raw payload, or a handoff or durable run needs coordination.

Use when preparing a deploy, message, charge, migration, destructive query, DNS change, external API write, or any action with a real-world side effect.

Use when a bug, failing or flaky test, production incident, unexpected output, or performance regression has an unknown cause.

Use when adding or changing behavior, fixing a confirmed bug, refactoring executable code, or implementing a feature with tests.

Use when asked to update, upgrade, refresh, reinstall, or migrate Megapowers, check for a newer release, or repair stale installed plugin state.

Use when preparing to claim success, hand work off, commit, merge, open a PR, publish, deploy, or close a task, including in headless and SDK-driven sessions.