Claude prompt for cyberpunk: Android Repair (High Converting)
Claude · Cyberpunk · High Converting
You are a hands-on practitioner using Claude for cyberpunk, specifically android repair.
Job: workshop scene.
Audience: storyboarders. Constraint: tools that make sense.
Working style: outcome-led. Optimize for clarity, specificity, and measurable results.
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.Claude users in cyberpunk use this android repair prompt to ship faster drafts that respect "tools that make sense". In practice, one customization pass is enough when the brief is this specific. The high converting version uses outcome-led language and targets clarity, specificity, and measurable results.
When to use this prompt
Claude shines at cyberpunk work when you state the observable outcome: workshop scene. The High Converting framing keeps clarity, specificity, and measurable results visible while you edit. Pair it with a real sample from your portfolio for best results.
Why this prompt works
- Uses outcome-led language that matches how practitioners actually brief work.
- Asks for a self-check pass, which cuts hallucinated details.
- Names a clear job so Claude does not wander into generic advice.
- The high converting angle adds clarity, specificity, and measurable results without extra fluff.
- Locks the audience (storyboarders) before style so tone stays honest.
How to use it in Claude
Neon cities, tech-noir mood, and future-grit details. Keep that context in the thread when you iterate. Add one real example from your last week of work so the model mirrors your domain. Paste the prompt into Claude and replace bracketed details with your facts. Save the winning variant for android repair — teams with a short library ship faster. This High Converting path is for storyboarders who care about workshop scene.
Ask for a checklist storyboarders would use. Then grade the draft against workshop scene. 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 High Converting output. Anthropic models still need your facts for android repair; they cannot invent metrics or brand rules. concept artists and worldbuilders teams bookmark slug android-repair-high-converting when clarity, specificity, and measurable results matters.
Step-by-step
- Open Claude 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.
- Add a 100-word example before the second run if voice matters.
- 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
- Deleting "tools that make sense" to save space — that is usually the whole point.
- Skipping the audience (storyboarders) and hoping Claude infers it.
- Using the High Converting prompt but editing it into a vague one-liner.
Expert notes
This Claude page targets "workshop scene" for storyboarders. Claude handles long briefs, policy-aware writing, and stepwise reasoning. The outcome-led tone keeps clarity, specificity, and measurable results visible while you edit.
Workflow tip: save three winning outputs for android repair and diff them. The shared skeleton becomes your team standard inside Claude.
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 Claude. |
Key takeaways
- If text output drifts, re-anchor with tools that make sense.
- Keep tools that make sense visible in the prompt, not only in your head.
- storyboarders should recognize themselves in the first paragraph.
- State the job (workshop scene) in one line before any style talk.
- Claude improves when you paste a real snippet or reference still.
FAQ
- What is a Claude prompt for android repair?
- It is a structured brief that tells Claude how to produce cyberpunk output for storyboarders. This high converting version stresses clarity, specificity, and measurable results and keeps "tools that make sense" in the instructions.
- How do I customize this Claude 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 high converting angle for android repair?
- Different angles solve different failures. High Converting helps when storyboarders need clarity, specificity, and measurable results. It is not longer for its own sake — each line has a job.
- Is this Claude prompt updated for 2026?
- Yes. Pages follow our SEO Bible, refresh on a rolling schedule, and include current best practices for Anthropic models. Always verify facts before client delivery.