プロンプト

Turn application requirements into architecture, APIs and an implementation plan.

Map systems, integration dependencies and a migration path.

Prioritize defects with evidence and concrete fixes.

A reproduction summary, diagnostic table, proposed patch and verification checklist.

A scenario matrix, test code, run instructions and coverage gaps.

An endpoint inventory, request and response examples, and contract acceptance criteria.

Bottleneck findings, candidate rewrites, index suggestions and a comparison plan.

A staged migration plan, SQL drafts, checkpoints and recovery steps.

Pipeline stages, configuration examples, release gates and failure handling.

An on-call checklist, diagnostic branches, recovery verification and review outline.

Component interfaces, state descriptions, implementation drafts and interaction checks.

Refactoring steps, before and after structure, compatibility risks and verification matrix.

Three candidate commit subjects, a body and necessary compatibility notes.

A script draft, argument reference, dry-run examples and failure checklist.

An impact table, upgrade sequence, compatibility edits and acceptance checks.

Evidence-backed risks, defensive fixes, retest steps and residual risks.

A performance evidence table, prioritized changes and repeatable measurement budgets.

An event inventory, sequence flow, failure handling and consistency tests.

Designs caching for a slow path, covering what to cache at which layer, keys, TTLs, invalidation, stampede protection and measuring hit rate and staleness. Use when fixing latency or database load.

Plans a breaking API version change with a deprecation timeline, compatibility shims, a client migration guide and adoption telemetry. Use before changing anything clients rely on.

Designs the sending side of webhooks with event selection, signing, retries with backoff, ordering, endpoint disabling, replay and a delivery log customers can see.

Re-examines a past architecture decision or ADR against what has changed since, separates broken assumptions from mere discomfort, and recommends keep, amend or supersede with the cost of each.

Diagnoses intermittent concurrency bugs by mapping shared state and the interleavings that break it, adds targeted instrumentation and proposes a fix. Use for bugs seen only under load.

Finds a memory leak from heap snapshots, memory metrics and code, naming the retaining path and the minimal fix with a regression check. Use when memory grows until a process is killed or restarted.