SEELE TV / Prompt archive

MiniMax design critique prompts: make the critique prompt set inspectable.

Use MiniMax design critique prompts to frame a precise reader question. Public discussion identifies a topic, while the method separates observed material from unverified product or output claims and leaves current context for direct confirmation.

Collection categories

Generation method

Choose how the production brief begins. Select an active method again to return to the complete collection.

Prompt minimax-design-critique-prompts-establishMedia reserved
Text generationScene16:915 sec

MiniMax Design Critique Prompts — Establish the world

Create a 15 sec 16:9 video direction for “MiniMax design critique prompts” in the context of trend previous minimax design skills.
Subject and action: Show the subject entering the setting, performing one clear action, and reaching a visible end state across three connected beats.
Camera and edit: Begin with a restrained wide establishing frame, move to a medium action shot, and finish on one legible detail.
Continuity: Preserve subject identity, wardrobe, hero-object details, geography, lighting direction, and direction of travel across every shot.
Sound: Use original location ambience, tactile action sounds, and no copyrighted music.
Production focus: Make MiniMax design critique prompts workflow and critique prompt set checklist visible through the scene rather than explaining it with text overlays.
Delivery: 16:9, 15 sec, text-led; realistic motion and material behavior; no logos, fake interface, duplicated subjects, impossible physics, or unsupported result claims.
Start Creating Source reserved
Prompt minimax-design-critique-prompts-socialMedia reserved
Text generationSocial9:1612 sec

MiniMax Design Critique Prompts — Build a vertical social cut

Create a 12 sec 9:16 video direction for “MiniMax design critique prompts” in the context of trend previous minimax design skills.
Subject and action: Communicate the premise in the first beat, demonstrate one change in the middle, and hold the result long enough to read.
Camera and edit: Use an immediate close opening, two readable handheld reframes, and a stable final composition designed for a vertical crop.
Continuity: Preserve subject identity, wardrobe, hero-object details, geography, lighting direction, and direction of travel across every shot.
Sound: Keep speech original and concise; connect cuts with room tone and motivated practical sounds.
Production focus: Make MiniMax design critique prompts workflow and critique prompt set checklist visible through the scene rather than explaining it with text overlays.
Delivery: 9:16, 12 sec, text-led; realistic motion and material behavior; no logos, fake interface, duplicated subjects, impossible physics, or unsupported result claims.
Start Creating Source reserved
Prompt minimax-design-critique-prompts-referenceMedia reserved
Reference generationReference16:918 sec

MiniMax Design Critique Prompts — Preserve a supplied reference

Create a 18 sec 16:9 video direction for “MiniMax design critique prompts” in the context of trend previous minimax design skills.
Subject and action: Introduce the referenced subject, show one physically plausible interaction, and return to a composition that can be checked against the source.
Camera and edit: Use the supplied reference as the identity, material, palette, and proportion constraint; cover it with wide, medium, and detail views.
Continuity: Preserve subject identity, wardrobe, hero-object details, geography, lighting direction, and direction of travel across every shot.
Sound: Use grounded ambience and synchronized object sounds; do not imply audio that is not established by the scene.
Production focus: Make MiniMax design critique prompts workflow and critique prompt set checklist visible through the scene rather than explaining it with text overlays.
Delivery: 16:9, 18 sec, reference-led; realistic motion and material behavior; no logos, fake interface, duplicated subjects, impossible physics, or unsupported result claims.
Start Creating Source reserved
Prompt minimax-design-critique-prompts-continuityMedia reserved
Reference generationContinuity4:320 sec

MiniMax Design Critique Prompts — Stress-test continuity

Create a 20 sec 4:3 video direction for “MiniMax design critique prompts” in the context of trend previous minimax design skills.
Subject and action: Repeat one subject, one hero object, and one spatial relationship through setup, action, reaction, and resolved end frame.
Camera and edit: Stage four connected shots with consistent screen direction, eyelines, lens logic, and motivated camera movement.
Continuity: Preserve subject identity, wardrobe, hero-object details, geography, lighting direction, and direction of travel across every shot.
Sound: Carry one continuous ambient bed across edits and add only original, scene-motivated effects.
Production focus: Make MiniMax design critique prompts workflow and critique prompt set checklist visible through the scene rather than explaining it with text overlays.
Delivery: 4:3, 20 sec, reference-led; realistic motion and material behavior; no logos, fake interface, duplicated subjects, impossible physics, or unsupported result claims.
Start Creating Source reserved

How to use the Model flexible archive

Treat the prompt as a production brief.

01

Define the reader task and evidence boundary

The critique prompt set begins by separating the exact phrase “MiniMax Design Skills” from any claim about a product, model, integration, control, access state, or output. For the minimax design critique prompts route, the prompts artifact is deliberately different from adjacent pages: it has its own input list, reviewer question, decision field, and handoff owner. This route uses the plan intent and the task “prepare structured design critique prompts”; retain only reader-visible inputs, review conditions, declared unknowns, and decisions as context. Its distinct review lens is layout hierarchy, type scale, contrast, spacing, component states, asset provenance, and critique notes. Freeze the design tokens, inspect typography hierarchy and contrast, enumerate component states, and record every exception that departs from the declared visual system. Keep that route-specific shape visible in the brief so a reader can tell this is a separate job, not a keyword-swapped copy block. Build a small, explicit record rather than a highlight-only narrative. Name the reader's question, the artifact that answers it, the owner of that artifact, and the acceptance conditions a second reviewer can inspect. Preserve source files and versions when permitted, redact unnecessary personal or billing information, and mark unavailable fields as unavailable. Do not borrow controls from another surface, infer regional availability from a social post, or turn a proposed workflow into a guaranteed capability. Compare one declared variable at a time, keep rejected attempts with their reasons when policy permits, and distinguish editorial usefulness from technical performance. The page supports a local planning or evaluation decision and makes no claim about customer adoption, commercial performance, repeatability, quality, or future availability. critique prompt set should remain revisable when the product surface, source rights, model label, delivery target, or review rubric changes.

02

Run a controlled brief or review packet

For this prepare structured design critique prompts, keep the source brief, authorization, visible workspace context, input and output identifiers, settings, timestamps, reviewer, and disposition together. For the minimax design critique prompts route, the prompts artifact is deliberately different from adjacent pages: it has its own input list, reviewer question, decision field, and handoff owner. This route uses the plan intent and the task “prepare structured design critique prompts”; retain only reader-visible inputs, review conditions, declared unknowns, and decisions as context. Its distinct review lens is layout hierarchy, type scale, contrast, spacing, component states, asset provenance, and critique notes. Freeze the design tokens, inspect typography hierarchy and contrast, enumerate component states, and record every exception that departs from the declared visual system. Keep that route-specific shape visible in the brief so a reader can tell this is a separate job, not a keyword-swapped copy block. Build a small, explicit record rather than a highlight-only narrative. Name the reader's question, the artifact that answers it, the owner of that artifact, and the acceptance conditions a second reviewer can inspect. Preserve source files and versions when permitted, redact unnecessary personal or billing information, and mark unavailable fields as unavailable. Do not borrow controls from another surface, infer regional availability from a social post, or turn a proposed workflow into a guaranteed capability. Compare one declared variable at a time, keep rejected attempts with their reasons when policy permits, and distinguish editorial usefulness from technical performance. The page supports a local planning or evaluation decision and makes no claim about customer adoption, commercial performance, repeatability, quality, or future availability. critique prompt set should remain revisable when the product surface, source rights, model label, delivery target, or review rubric changes.

03

Close with a narrow disposition

A useful critique prompt set ends at the scale of the evidence: it records what was observed, what remains unknown, which decision was made, and what event requires a retest. For the minimax design critique prompts route, the prompts artifact is deliberately different from adjacent pages: it has its own input list, reviewer question, decision field, and handoff owner. This route uses the plan intent and the task “prepare structured design critique prompts”; retain only reader-visible inputs, review conditions, declared unknowns, and decisions as context. Its distinct review lens is layout hierarchy, type scale, contrast, spacing, component states, asset provenance, and critique notes. Freeze the design tokens, inspect typography hierarchy and contrast, enumerate component states, and record every exception that departs from the declared visual system. Keep that route-specific shape visible in the brief so a reader can tell this is a separate job, not a keyword-swapped copy block. Build a small, explicit record rather than a highlight-only narrative. Name the reader's question, the artifact that answers it, the owner of that artifact, and the acceptance conditions a second reviewer can inspect. Preserve source files and versions when permitted, redact unnecessary personal or billing information, and mark unavailable fields as unavailable. Do not borrow controls from another surface, infer regional availability from a social post, or turn a proposed workflow into a guaranteed capability. Compare one declared variable at a time, keep rejected attempts with their reasons when policy permits, and distinguish editorial usefulness from technical performance. The page supports a local planning or evaluation decision and makes no claim about customer adoption, commercial performance, repeatability, quality, or future availability. critique prompt set should remain revisable when the product surface, source rights, model label, delivery target, or review rubric changes.

Reader notes

Before you generate.

Does MiniMax Design Skills prove a current product capability?

No. The preserved public discussion is topic context only. Verify the authorized workspace, current first-party material, inputs, controls, entitlement, and outputs before making a capability statement.

What does this route produce?

It produces an evidence-safe critique prompt set packet or method for the stated reader task. It does not run a model, certify an output, or report a customer or commercial result.