No public results yet
Plan an incremental library migration with rollback checkpoints
Break a dependency replacement into reviewable stages with compatibility checks, exit criteria and realistic rollback limits.
Trace inputs, branches, outputs and side effects in supplied code, with a worked example and clear limits on what can be inferred.
No public result for version 1 yet
Version 1 · 3 variables · 3 required
Fill in the values below — the customized prompt updates as you type. marks a required value.
The reader's relevant background. Default: A developer comfortable with Python syntax but new to generators.
Code and relevant inline documentation. Default: def unique(items): seen = set() for item in items: if item not in seen: seen.add(item) yield item
The behavior the reader most wants to understand. Default: Does this preserve input order, and what kinds of inputs can fail?
Explain this code for A developer comfortable with Python syntax but new to generators.:
def unique(items):
seen = set()
for item in items:
if item not in seen:
seen.add(item)
yield item
Focus question: Does this preserve input order, and what kinds of inputs can fail?
Start with a plain-language statement of what the code does. Map inputs, key transformations, branches, returned values, and visible side effects. Refer to actual symbols or line numbers from the supplied snippet; do not invent surrounding modules.
Walk through one small example by showing the value changes that can be derived from the code. Label this a manual trace, not an executed result. Explain one relevant boundary or failure case, and identify behavior that depends on a caller, dependency, or configuration not provided.
Finish by answering the focus question and naming the smallest additional excerpt needed to resolve any uncertainty. Do not rewrite the implementation unless asked.No public examples yet for version 1
Curated prompt only. No example output or model test is attached; model compatibility has not been verified. Default inputs are illustrative practice material; replace them with your own facts and context.
Reports go to moderators and are never shown publicly.
No public results yet
Break a dependency replacement into reviewable stages with compatibility checks, exit criteria and realistic rollback limits.
No public results yet
Define realistic traffic, workload data, measurements and stopping rules for an authorized performance test.
No public results yet
Find source-visible labeling, semantics and keyboard risks, while separating code findings from checks that require a browser.
No public results yet
Map feature assets, trust boundaries and data flows to concrete threats, existing controls and targeted verification tasks.
No public results yet
Turn an API contract into a small client design that handles retryable failures, deadlines and idempotency deliberately.
No public results yet
Interpret supplied plan evidence and prioritize query or index experiments without inventing costs or speedups.
Oldest first · one level of replies
Sign in to join the discussion. Share what you learned or made with this prompt.
No comments yet
Be the first to share how this prompt worked for you.