MiniMax Prompt Generator

MiniMax leads on multi-turn tool use — define the tools precisely.

Goal: [THE END STATE]

Available functions:
- `[function_name](param: type)` — [what it does, when to call it]
- `[function_name](param: type)` — [what it does, when to call it]

Rules:
- Call a function rather than guessing any value you do not have.
- Chain calls where one result feeds the next; do not ask me between steps.
- If a call fails, retry once with corrected arguments, then report the failure.

Report: the call sequence you made, the result of each, and the final answer.

Full spec for end-to-end implementation work.

## Goal
[WHAT TO BUILD]

## Context
[STACK, VERSIONS, EXISTING ARCHITECTURE]
[PASTE RELEVANT CODE]

## Requirements
[NUMBERED LIST]

## Constraints
[DEPENDENCIES, PERFORMANCE, COMPATIBILITY]

## Output Format
Implementation plan, then complete code per file, then tests, then a verification checklist.

Plays to MiniMax's large-context document work.

[PASTE LONG DOCUMENT OR CORPUS]

---

Task: [WHAT TO DO WITH IT]

Requirements:
- Reference the section behind each finding.
- Keep terminology consistent with the source.
- Note any section you could not parse.

Format: [FORMAT].

Designing the decomposition rather than executing it.

Design an agent workflow that accomplishes: [GOAL]

Available capabilities: [TOOLS / APIs / DATA SOURCES]

For each step specify: the trigger, the tool called, the inputs, the success check, and what happens on failure.

Constraints: [LATENCY, COST, HUMAN-IN-THE-LOOP POINTS]

Format: a numbered step table, then the failure-handling policy, then the three most likely failure modes.

Explicit before/after with behaviour preservation.

Migrate the code below from [SOURCE] to [TARGET].

Preserve: [BEHAVIOUR THAT MUST NOT CHANGE]
Allowed to change: [WHAT MAY CHANGE]
Forbidden: [WHAT MUST NOT BE TOUCHED]

Return the migrated code, then a mapping table of old construct → new construct, then anything that has no clean equivalent and how you handled it.

Code:
[PASTE CODE]

General analytical work with clear decision criteria.

You are a [ROLE].

Analyse [SUBJECT] and recommend [DECISION].

Context: [BACKGROUND]. Constraints: [CONSTRAINTS]. Decision criteria in priority order: [1], [2], [3].

Requirements: quantify where possible, state assumptions explicitly, give one recommendation rather than a menu.

Format: recommendation, reasoning, risks, next steps. Under [WORD COUNT] words.