Claude Skills by machenjie

`analysis-agent`/`task-agent`/`review-agent`: use when a framework, platform, infrastructure, or managed service creates a commitment; skip package, runtime, or fixed-stack work.

Use when tenant isolation spans data, caches, queues, runtime, search, telemetry, deletion, or export. Skip policy-only authorization, billing, customization, and SaaS lifecycle.

`analysis-agent`/`task-agent`/`review-agent`: use when fixtures, factories, seeds, isolation, cleanup, or sensitive test-data rules change; skip when test data is unaffected.

`analysis-agent`/`task-agent`/`review-agent`: use to recommend a risk-to-test evidence portfolio and omissions; skip test implementation, fixed-command, and release-verdict work.

`analysis-agent`/`task-agent`/`review-agent`: use when behavior needs deterministic seams for time, randomness, UUIDs, collaborators, or external I/O; skip when seams are adequate.

`analysis-agent`/`task-agent`/`review-agent`: use for changed assets, trust boundaries, reachable abuse paths, impact, or control placement; skip without a security delta.

Use with analysis-agent or task-agent for task-local transaction, isolation, and conflict decisions. Do not use without a transaction decision or as task owner.

`analysis-agent`/`task-agent`/`review-agent`: use when TypeScript runtime validation, structural typing, async, numeric, or module semantics change; skip generic work.

`analysis-agent`/`task-agent`/`review-agent`: use when logic, rules, invariants, branches, edges, or failure paths need isolated tests; skip without a unit-test decision.

`analysis-agent`: use when actors, goals, preconditions, triggers, paths, guarantees, postconditions, or acceptance traces need modeling; skip when no use-case decision exists.

`analysis-agent`/`task-agent`: use when actor journeys change entries, branches, interruption, recovery, authority, or side effects; skip route/state-only work.

`analysis-agent`/`task-agent`/`review-agent`: use when actors, personas, admins, customers, service accounts, or role risks need identification; skip when roles are unchanged.

`analysis-agent`/`task-agent`/`review-agent`: use when API, schema, event, or behavior changes need compatibility, deprecation, rollout, or migration; skip without version impact.

`analysis-agent`/`task-agent`/`review-agent`: use for browser/PWA runtime; skip generic components with no web-platform semantic decision, TS-only, backend, or native-client work.

`analysis-agent`/`task-agent`/`review-agent`: use for render sinks, browser state, server fetch, upload, redirect, cross-origin, or embedding changes; skip without web exposure.

Define source-backed, measurable acceptance with `analysis-agent` when acceptance is vague or failure behavior is unspecified. Do not select it when acceptance is already measurable or the request is question-only.

Use `review-agent` on implementation or repair diffs for hallucinated APIs, unsupported assumptions, unsafe abstractions, and dependency or regression risks. Skip work without a diff or after reviewer edits.

Use `analysis-agent` for module-boundary or dependency-direction analysis, or `review-agent` for independent assessment of a bounded architecture artifact. Skip isolated owner-internal edits with no structural impact.

Use `task-agent` for bounded backend service, API, worker, or repair changes, loading authorization, consistency, retry, contract, and rollout guidance only when triggered. Skip frontend-only and read-only work.

Use `task-agent` to update source-backed documentation or `review-agent` to assess documentation impact and accuracy when public behavior or operator workflows change. Skip work with no audience-facing behavior change.

Use `analysis-agent` when engineering intent lacks desired behavior, boundaries, constraints, or completion signals. Skip requests with an accepted Engineering Brief and no-repo direct-answer work.

Analyze an API, schema, migration, or compatibility decision with `analysis-agent`, or implement its bounded contract change with `task-agent`. Do not select it when no data or public-contract surface is affected.

Use `analysis-agent` for database, cache, queue, search, or consistency risk, or `task-agent` for bounded middleware changes. Skip work without middleware or source-of-truth impact and unrelated inspection.

Use `analysis-agent` for release decisions, `task-agent` for delivery artifacts, or `review-agent` for readiness on deployment, migration, rollback, or production risk. Skip local work with no release decision.

Use `analysis-agent` to identify domain ownership, invariants, state transitions, and cross-context effects when rules change or ownership is unclear. Skip presentation-only or question-only work with no domain behavior.

Use `review-agent` for an ordinary Engineering Brief, Task Plan, acceptance, or contract artifact. Route high-risk design and release, deployment, or migration readiness to their specialist reviewers.

Use `analysis-agent`: `implementation-preparation` for changes, `diagnosis-only` for verified cause, or `source-backed-answer` for repository questions. Skip source-free, Direct Task, and accepted-Brief narrow artifacts.

Use `analysis-agent` to map user-flow, interaction-state, accessibility, content, and recovery impact when experience behavior changes. Skip backend-only work with no experience effect and question-only requests.

Use `task-agent` for bounded frontend component or browser changes involving interaction, accessibility, API failures, security, or regression proof. Skip backend-only work and design exploration without implementation.

Use `review-agent` for a high-risk Engineering Brief when a critical path, architecture boundary, material risk, or multiple downstream tasks need deeper design evidence. Skip ordinary work without those signals.

Use `analysis-agent` for active multi-responder incident command, cadence, mitigation, communications, or handoff. Skip ordinary diagnosis, reliability design, release approval, post-incident docs, and execution.

Use `task-agent` for accepted Android, iOS/iPadOS, desktop, or cross-platform installed-client source changes. Skip browser/PWA-only, backend, infrastructure, release approval, and independent review work.

Use `analysis-agent` for integration decisions or `task-agent` for cross-system/external changes involving contracts, retries, idempotency, authentication, or reconciliation. Skip isolated work with no integration edge.

Use `task-agent` for bounded logging changes or `review-agent` to independently assess placement, schema, severity, redaction, correlation, and signal tradeoffs. Skip work with no logging impact and self-review requests.

Use `task-agent` for accepted infrastructure-as-code, cluster, cloud, delivery-platform, or environment-definition source changes. Skip production apply/deploy, release approval, and independent review.

Use `analysis-agent` to map acceptance to validation, `task-agent` to add or run bounded tests, and `review-agent` to assess proof coverage. Skip work with no material change or already-fresh complete validation.

Use `analysis-agent` to analyze recovery, SLO, capacity, degradation, and observability; `task-agent` to change resilience or telemetry; and `review-agent` to assess evidence. Skip self-review and no-runtime-impact work.

Use `task-agent` for a bounded repository generator, plugin, harness, CLI, monorepo automation, or maintenance utility source change. Skip product behavior, config-only work, docs, release, review, and planning.

Use an independently assigned `review-agent` for post-authoring review of changed rd-skills routing registries, fixtures, mappings, or owner conflicts without repair. Skip product work and in-task global rerouting.

Use `analysis-agent` to analyze permissions, secrets, sensitive data, trust boundaries, and injection; `task-agent` to implement controls; and `review-agent` to assess evidence. Skip self-review and no-trust-impact work.

Use `analysis-agent` to create a Task DAG from an accepted source-backed Brief when 2+ tasks have dependencies, parallel value, integration, or release order. Skip single edits, accepted DAGs, and unanalysed requests.