Gemini prompt for cyberpunk: Android Repair (Workflow)
Gemini · Cyberpunk · Workflow
You are a pragmatic coach using Gemini for cyberpunk, specifically android repair.
Job: workshop scene.
Audience: storyboarders. Constraint: tools that make sense.
Working style: operational. Optimize for step order, checkpoints, and handoffs.
Process:
1. Restate the brief in one sentence and list missing facts as questions.
2. Draft the artifact.
3. Stress-test it against the constraint.
4. Return a final version plus 3 numbered improvements.
Output contract: use headings, short paragraphs, and concrete examples. No filler. No invented statistics.
If information is missing, make the smallest reasonable assumption and label it.Use this Gemini cyberpunk template when storyboarders need android repair with the rule: tools that make sense. Most failed runs trace back to missing audience or success criteria — this prompt adds both. The workflow version uses operational language and targets step order, checkpoints, and handoffs.
When to use this prompt
When storyboarders tackle android repair inside cyberpunk, the hard part is not the model — it is the brief. Neon cities, tech-noir mood, and future-grit details. This prompt encodes that context so Gemini does not guess. Pair it with a real sample from your portfolio for best results.
Why this prompt works
- Names a clear job so Gemini does not wander into generic advice.
- The workflow angle adds step order, checkpoints, and handoffs without extra fluff.
- Asks for a self-check pass, which cuts hallucinated details.
- Repeats the hard constraint: tools that make sense.
- Forces an output contract: headings, examples, and a final version.
How to use it in Gemini
Ask for a shorter version after the long one; compression reveals weak claims. For cyberpunk work, paste gemini is useful for research synthesis, workspace-style tasks, and multimodal briefs as a one-line reminder above the prompt. If the first answer is vague, reply with the constraint again: tools that make sense. Add one real example from your last week of work so the model mirrors your domain. Name the success metric aloud: workshop scene. If the draft cannot pass it, do not polish prose yet.
Run a constrained version and a wild version of android repair. Keep structure from one and energy from the other. For android repair in cyberpunk, the failure mode is usually too many jobs in one ask. This prompt blocks that by design — especially "tools that make sense". Expect two minutes customizing and two minutes editing for Workflow output. Google models still need your facts for android repair; they cannot invent metrics or brand rules. concept artists and worldbuilders teams bookmark slug android-repair-workflow when step order, checkpoints, and handoffs matters.
Step-by-step
- Open Gemini and paste the prompt block unchanged.
- Replace placeholders with your project facts (storyboarders, offer, timeline).
- Confirm the constraint is still visible: tools that make sense.
- If output is vague, ask Gemini to restate assumptions as questions first.
- Reply with one fix list, then regenerate the final version only.
Example output
Example output shape: H1 with Android Repair, 3 short sections, bullet list of recommendations, closing line that states tools that make sense. Facts you supply appear; nothing invented.
Common mistakes
- Skipping the audience (storyboarders) and hoping Gemini infers it.
- Ignoring the output contract headings.
- Deleting "tools that make sense" to save space — that is usually the whole point.
Expert notes
Practitioners choose Workflow when android repair needs step order, checkpoints, and handoffs. Gemini from Google still needs your facts — especially for tools that make sense.
For cyberpunk, compare this Workflow prompt against the Quick Start and Expert angles on the same use case. Keep the structure that scores higher on workshop scene.
Comparison / variations
| Approach | When | Tweak |
|---|---|---|
| Bare request | You only need a spark | Write a android repair piece. |
| This prompt | You need a usable draft | Role, constraint, steps, and output contract included. |
| Plus examples | Voice must match yours | Paste 120 words of your writing or a still you like, then rerun in Gemini. |
Key takeaways
- Cyberpunk work needs neon cities, tech-noir mood, and future-grit details.
- storyboarders should recognize themselves in the first paragraph.
- Gemini improves when you paste a real snippet or reference still.
- Keep tools that make sense visible in the prompt, not only in your head.
- Compare against other Gemini angles on the same use case before you standardize.
FAQ
- What is a Gemini prompt for android repair?
- It is a structured brief that tells Gemini how to produce cyberpunk output for storyboarders. This workflow version stresses step order, checkpoints, and handoffs and keeps "tools that make sense" in the instructions.
- How do I customize this Gemini cyberpunk prompt?
- Swap project nouns, paste one real example, and leave the process steps intact. The constraint "tools that make sense" should stay unless your brief truly changed.
- Why use the workflow angle for android repair?
- Different angles solve different failures. Workflow helps when storyboarders need step order, checkpoints, and handoffs. It is not longer for its own sake — each line has a job.
- Is this Gemini prompt updated for 2026?
- Yes. Pages follow our SEO Bible, refresh on a rolling schedule, and include current best practices for Google models. Always verify facts before client delivery.