Explore Prompts

Create a pipeline where analytics identifies friction points and the agent proposes small UX or performance fixes. Require user impact estimation and safe rollout.

Design a plan to evolve telemetry schemas: version fields, dual-write, backfill, and validation. Include privacy checks and cost controls.

Create an agent that rewrites error messages for clarity, adds error codes, and links to docs. Verify improvements via support ticket taxonomy and A/B testing.

Design a self-improving CLI agent that adds features while preserving backward compatibility, adds help text/tests, and uses semantic versioning rules.

Create a plan to safely modify locale/date/number formatting: add tests for edge locales, verify backward compatibility, and avoid breaking user settings.

Design traceability: map docs claims to tests that verify them. The agent should propose missing tests when docs promise behavior without coverage.

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.