Claude prompt for cyberpunk: Android Repair (Common Fixes)
Claude · Cyberpunk · Common Fixes
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: diagnostic. Optimize for typical failures and how to repair the prompt.
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.A strong Claude cyberpunk android repair prompt names the job, audience, and finish line. This page does that for storyboarders. Teams report saving 15–30 minutes per task when prompts include constraints up front. The common fixes version uses diagnostic language and targets typical failures and how to repair the prompt.
When to use this prompt
Claude shines at cyberpunk work when you state the observable outcome: workshop scene. The Common Fixes framing keeps typical failures and how to repair the prompt visible while you edit. Pair it with a real sample from your portfolio for best results.
Why this prompt works
- The common fixes angle adds typical failures and how to repair the prompt without extra fluff.
- Separates draft from critique so you can steal the structure later.
- Keeps cyberpunk vocabulary specific instead of buzzwords.
- Locks the audience (storyboarders) before style so tone stays honest.
- Centers workshop scene so success is observable.
How to use it in Claude
Save the winning variant for android repair — teams with a short library ship faster. Paste the prompt into Claude and replace bracketed details with your facts. Name the success metric aloud: workshop scene. If the draft cannot pass it, do not polish prose yet. Ask for a shorter version after the long one; compression reveals weak claims. When storyboarders review output, they should see typical failures and how to repair the prompt without hunting for it.
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 Common Fixes 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-fixes when typical failures and how to repair the prompt 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.
- If output is vague, ask Claude 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
- 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 Common Fixes prompt but editing it into a vague one-liner.
Expert notes
Anthropic 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 Common Fixes variant, they usually care about typical failures and how to repair the prompt 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 Claude. |
Key takeaways
- State the job (workshop scene) in one line before any style talk.
- If text output drifts, re-anchor with tools that make sense.
- Claude improves when you paste a real snippet or reference still.
- Cyberpunk work needs neon cities, tech-noir mood, and future-grit details.
- Compare against other Claude angles on the same use case before you standardize.
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 common fixes version stresses typical failures and how to repair the prompt 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 common fixes angle for android repair?
- Different angles solve different failures. Common Fixes helps when storyboarders need typical failures and how to repair the prompt. 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.