Task and output contract
Turn a request into a job with a clear deliverable and a clear way to check it.
81 methods · Three levels in every card
A starting point based on the work you want to do.
Search for a method name or for the work you want to do. When you open a card, you can read the explanation, the Simple, Medium and Hard examples, the limits and the original sources together.
Start with the Simple example; read its situation and limits before adapting the prompt. The examples are fictional teaching examples, not model experiments that were actually run.
Read the guide to choosing a method →
Card texts: Mustafa Saraç · CC BY 4.0. Review / contribute on GitHub. Source version: 6257da10f016. Images and third-party works are not covered by this license.

Original illustration made with Google Gemini · 1024 × 572
Generate an image: Create an original museum-grade computational sculpture photographed as a physically present installation, horizontal 16:9. Deep anthracite void, mineral porcelain whites, restrained ice-blue and amber accents, fine particles only where structurally meaningful, tactile surfaces, subtle volumetric illumination, believable depth, exceptional edge detail and intentional negative space. A monumental asymmetric mineral atlas suspended in darkness: four unmistakably different physical pathways share one quiet white origin. One pathway extracts fragments from deep layered strata, one folds a broad sheet into an expressive surface, one passes through exact geometric joints, and one forms a responsive open loop reaching into the environment. The pathways remain spatially distinct and meet at a small controlled amber nexus. View from a low three-quarter angle with architectural scale and dramatic but soft side lighting. Preserve a large dark breathing area in the upper left. The result should feel like a single intentional sculpture, not four panels or a collage. Keep the image sophisticated and legible at mobile size: one dominant mechanism, a clear silhouette, no decorative overload. No text, letters, numbers, typography, captions, symbols, watermark, logo, fake chart, screenshot, interface, identifiable people or artist signature. Do not imitate any specific existing artwork.
Explanations, examples and sources are searched too. If you type several words, all of them must match.
Showing 81 of 81 cards. All use cases.
Turn a request into a job with a clear deliverable and a clear way to check it.
Show the behavior you want with a few correct input–output pairs.
State which details the model should look at, and for which reader.
Make the context, objective and reader visible in the same short brief.
Carry the short, checkable intermediate results from a solved example over to a new problem.
Ask for short intermediate results without giving a solved example; extract the final answer separately.
Solve the easy subproblem first; make its result the input of the next problem.
Before returning to the detailed question, find which general principle applies.
Take separate samples for the same question; count the final answers in a common format.
Open more than one solution path; evaluate the intermediate states and go back when needed.
Let the model write the program; let a real interpreter compute the numeric answer.
When you answer a question, find the relevant document first; then build the answer from the information in that document.
Match every claim with the passage that actually supports it.
Generate a draft that resembles the document you are looking for; use it to find the real documents.
Use the intermediate information you found to change the direction of the next search.
Give the output schema to an API that supports it; check the meaning of the returned data separately.
Separate the instruction, the source text and the example in a readable way.
Pass the first text through a separate critique call and correct it with concrete feedback.
Break the draft into small check questions; get the answers again without being influenced by the draft.
Turn the feedback from one attempt into a short lesson note and carry it into the next attempt.
Get the model's evaluation with explicit criteria and sources; check the judge's decision too.
Ask the model not to do the job, but to write the instruction that will be used for that job.
Let a conductor model define the subtasks; let the application pass them to separate expert calls.
Instead of solved content examples, give a schema that shows the structure of the task.
Generate candidate instructions; choose which one works based on the target model's real outputs.
Generate new candidates by showing earlier candidates together with their real scores.
Derive prompt changes from error traces; keep candidates that are strong on different examples together.
Define model calls as input–output modules; tie optimization to a metric.
Rank candidates by measuring, as a probability, how well the generated text predicts the starting prompt.
Choose the next step based on the tool result that actually came back.
Split a job into small calls whose output is checked.
Define what comes back from a tool as carefully as what goes into it.
Make the permissions, the budget and the stop condition visible at the start of the job.
Keep a project's reusable working rules in one document.
When you shorten a long history, do not lose the decisions and the open tasks.
Keep the state that needs to be remembered outside the chat, in a note with sources.
Before preparing the answer, let the model ask for the missing information.
Before answering a question, propose a more useful version of it.
Make clear where the answer ends and which information is missing.
Do not confuse commands inside the text being read with the user's authority.
Turn a scattered request into a layered instruction structure with a known version.
Instead of narrating intermediate steps at length, limit them to short, checkable notes.
Work with solution pieces that can merge, instead of a single path.
Before answering, generate candidate pieces of relevant knowledge; do not mistake them for sources.
First set up the solution plan, then carry out the steps of that same plan.
Answer the missing subquestion before returning to the main question.
Emotional emphasis is an instruction variable; it does not give the model emotions.
First produce a skeleton, then fill in the independent parts in separate calls.
First rewrite the context relevant to the question; generate the answer from that context.
Bring in the important information left in the source without making the summary longer.
Let a small policy model generate task-specific hints for a large model.
Select similar examples, shuffle the options, and combine separate answers by mapping them back.
Tie the critique to an external tool result, then correct the answer.
Examine a scattered context in small parts, then extract only the answer.
Hand the numerical calculation over from the language model to an executor.
Reconstruct backwards which question the solution assumes, and compare it with the actual question.
Have a human label the examples the model is most uncertain about.
Route subtasks to named handlers; carry their results like a program.
Look for the missing point by explaining what you want to do and which steps you follow.
You build the explanation; the model makes the connection you skipped visible.
Explain back what you understood in your own words; check where the explanation fell short.
Let the model keep the student role with a limited knowledge state; you are the one explaining.
Without giving the answer right away, help the learner find the next step.
Question each other's assumptions in turn; keep the final decision open.
Split a subquestion again when needed; combine the answers upwards.
Recall without seeing the answer, then compare with the source.
Spread review over time; record what you forgot.
Before choosing a solution, clarify which problem you are solving.
Do not ask for a preference as a single label; bring it out through trade-offs.
Have the generated code explained, check how it runs, fix the faulty step.
Make understanding the task, the first solution and the final check separate, visible steps.
Before building the main answer, clarify the necessary subquestions with the user.
Put other paths next to the first solution; compare them with the same criteria.
Generate similar solutions, then show which structure carries over to the target question.
Run ideation together with the human's own ideas and explicit constraints.
Assume the work has failed; look for concrete causes that could lead to it.
See the claim, its support and its objection as separate nodes.
Record your own judgment first, then compare it with the model's suggestion.
Make the group's different pieces of knowledge visible; do not manufacture an artificial consensus.
Compare the answers of separate model calls, then run a bounded debate.
The tutor produces the answer; a separate supervisor checks the permitted level of help.
Adapt the prompts to your own situation. In an example that needs a tool or a separate call, copying the text alone does not set up that way of working.