Claude prompt for cyberpunk: Android Repair (Advanced)
Claude · Cyberpunk · Advanced
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: 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.Claude users in cyberpunk use this android repair prompt to ship faster drafts that respect "tools that make sense". 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
Claude shines at cyberpunk work when you state the observable outcome: workshop scene. The Advanced framing keeps constraints, evaluation, and edge cases visible while you edit. Pair it with a real sample from your portfolio for best results.
Why this prompt works
- Repeats the hard constraint: tools that make sense.
- Uses precise and demanding language that matches how practitioners actually brief work.
- Names a clear job so Claude does not wander into generic advice.
- Locks the audience (storyboarders) before style so tone stays honest.
- Asks for a self-check pass, which cuts hallucinated details.
How to use it in Claude
Neon cities, tech-noir mood, and future-grit details. Keep that context in the thread when you iterate. Redact client names; keep structure. Slug android-repair-advanced is your canonical URL for this brief. 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. Save the winning variant for android repair — teams with a short library ship faster.
Have Claude list assumptions about cyberpunk before drafting. Delete any you cannot defend. 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. 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-advanced when constraints, evaluation, and edge cases 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.
- 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
- 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 Advanced 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 precise and demanding tone keeps constraints, evaluation, and edge cases 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
- Claude improves when you paste a real snippet or reference still.
- The Advanced variant is for constraints, evaluation, and edge cases.
- Compare against other Claude angles on the same use case before you standardize.
- Document what changed when you customized slug android-repair-advanced.
- If text output drifts, re-anchor with tools that make sense.
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 advanced version stresses constraints, evaluation, and edge cases 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 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 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.