Explore Prompts

Build a dependency graph indexer and an impact analyzer that estimates blast radius of a change and picks appropriate test suites and reviewers.

Create a plan to reduce permissions across services: narrow IAM roles, remove unused keys, and add tests that detect overbroad permissions. Require staged rollout.

Design an agent that reduces third-party API spend via caching, batching, and smarter fallbacks, while preserving correctness. Include cost dashboards and guardrails.

Create an agent that scans logs/events for accidental PII collection and proposes fixes (redaction, schema changes). Include alerting and retention rules.

Design an agent that tunes retry/backoff/rate-limits based on telemetry. Require proofs that error rates drop without raising costs or latency.

Create a chaos testing approach limited to staging: inject failures, verify timeouts/circuit breakers, and ensure alerts fire. Require strict boundaries and approval.

Design automated rollback tests that verify deployments can be reverted cleanly. Include data migration constraints and safe fallback paths.

Build a semantic diff summarizer: describe functional change, impacted modules, migration needs, and risks. Require it to cite tests/benchmarks that support claims.

Design UI improvements for reviewing AI-made diffs: risk highlighting, test evidence, and “what changed semantically.” Include A/B testing plan for reviewer speed/accuracy.

Create a schedule for the research agent to pull release notes, CVEs, and docs updates, summarize changes, and propose actionable backlog items with citations.

Design a doc crawler + citation store so the agent can quote authoritative sources for API usage and edge cases. Include freshness checks and version pinning.

Create a security patching playbook: small diffs, added tests, immediate canary, and post-deploy monitoring. Include coordination with human security reviewers.