Gemini prompt for cyberpunk: Android Repair (Advanced)
Gemini · Cyberpunk · Advanced
You are a pragmatic coach using Gemini for cyberpunk, specifically android repair.
Job: workshop scene.
Audience: storyboarders. Constraint: tools that make sense.
Working style: precise and demanding. Optimize for constraints, evaluation, and edge cases.
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.This Gemini cyberpunk android repair prompt helps you workshop scene without rewriting instructions from scratch each time. Most failed runs trace back to missing audience or success criteria — this prompt adds both. The advanced version uses precise and demanding language and targets constraints, evaluation, and edge cases.
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
- Separates draft from critique so you can steal the structure later.
- Forces an output contract: headings, examples, and a final version.
- Locks the audience (storyboarders) before style so tone stays honest.
- Repeats the hard constraint: tools that make sense.
- Asks for a self-check pass, which cuts hallucinated details.
How to use it in Gemini
Name the success metric aloud: workshop scene. If the draft cannot pass it, do not polish prose yet. Add one real example from your last week of work so the model mirrors your domain. Use precise and demanding follow-ups only — mixing tones mid-thread confuses Google models. For cyberpunk work, paste gemini is useful for research synthesis, workspace-style tasks, and multimodal briefs as a one-line reminder above the prompt. Ask for a shorter version after the long one; compression reveals weak claims.
Swap the audience once. If the android repair piece still works, the core is solid. 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 Advanced 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-advanced when constraints, evaluation, and edge cases 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.
- For cyberpunk work, paste a rubric and ask for a self-score.
- 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
Google users working on android repair in cyberpunk should treat "tools that make sense" as non-negotiable. Neon cities, tech-noir mood, and future-grit details. When storyboarders run the Advanced variant, they usually care about constraints, evaluation, and edge cases more than length.
If text output feels generic, re-paste tools that make sense as the first follow-up message — do not rewrite the whole prompt.
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
- storyboarders should recognize themselves in the first paragraph.
- Gemini improves when you paste a real snippet or reference still.
- Document what changed when you customized slug android-repair-advanced.
- Keep tools that make sense visible in the prompt, not only in your head.
- State the job (workshop scene) in one line before any style talk.
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 advanced version stresses constraints, evaluation, and edge cases 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 advanced angle for android repair?
- Different angles solve different failures. Advanced helps when storyboarders need constraints, evaluation, and edge cases. 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.