Explore Prompts

Create a performance tuning agent that profiles hotspots, proposes targeted optimizations, validates with benchmarks, and documents tradeoffs.

Design a migration workflow: generate migrations, run on staging snapshots, verify invariants, measure runtime, and define rollback strategy. Require human approval for prod.

Create an agent that checks API changes for backward compatibility: OpenAPI/JSON schema diffs, deprecation policy, versioning, and migration notes.

Design characterization tests for legacy code before refactoring: capture I/O behavior, edge cases, and performance baselines. Use them as a gate for changes.

Create an agent that infers code style from the repo (naming, patterns, architecture) and generates a style guide. Use it to validate future edits.

Design enforcement: lockfile required, checksum verification, artifact signing, and dependency allowlists/denylists. Include alerting on suspicious updates.

Create a threat-modeling step: identify assets, attackers, and abuse cases for each PR. Include automated checks and a human escalation threshold.

Design a process where the agent checks a proposed change against official documentation versions, release notes, and migration guides. Require citations for claims.

Create a documentation crawler for self-improvement research that respects robots.txt, rate limits, and TOS. Include caching, dedupe, and citation storage.

Design an improvement loop keyed to SLOs: latency, error rates, and quality metrics. Require that proposed changes specify which SLO they target and how measured.

Create a backlog system: bugs, tech debt, performance, and security items. Include scoring by user impact, risk, and effort, and automatic issue creation via MCP.

Design a patch strategy that prefers minimal diffs: isolate behavior changes, avoid formatting churn, and include clear intent comments. Add a “diff size budget.”