Claude prompt for cyberpunk: Android Repair (Starter)
Claude · Cyberpunk · Starter
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: plain and encouraging. Optimize for first successful run with safe defaults.
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 Claude cyberpunk android repair prompt helps you workshop scene without rewriting instructions from scratch each time. Teams report saving 15–30 minutes per task when prompts include constraints up front. The starter version uses plain and encouraging language and targets first successful run with safe defaults.
When to use this prompt
Claude shines at cyberpunk work when you state the observable outcome: workshop scene. The Starter framing keeps first successful run with safe defaults visible while you edit. 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.
- Repeats the hard constraint: tools that make sense.
- Locks the audience (storyboarders) before style so tone stays honest.
- The starter angle adds first successful run with safe defaults without extra fluff.
- Keeps cyberpunk vocabulary specific instead of buzzwords.
How to use it in Claude
Save the winning variant for android repair — teams with a short library ship faster. For cyberpunk work, paste claude handles long briefs, policy-aware writing, and stepwise reasoning as a one-line reminder above the prompt. When storyboarders review output, they should see first successful run with safe defaults without hunting for it. Neon cities, tech-noir mood, and future-grit details. Keep that context in the thread when you iterate. Ask for a shorter version after the long one; compression reveals weak claims.
Start with the ugly first pass for android repair. Name what is wrong in five bullets, then rerun in Claude. 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 Starter 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-starter when first successful run with safe defaults 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 Starter 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 Starter variant, they usually care about first successful run with safe defaults 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.
- storyboarders should recognize themselves in the first paragraph.
- Document what changed when you customized slug android-repair-starter.
- Claude improves when you paste a real snippet or reference still.
- Ship a draft, then tighten. Do not chase a perfect first token.
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 starter version stresses first successful run with safe defaults 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 starter angle for android repair?
- Different angles solve different failures. Starter helps when storyboarders need first successful run with safe defaults. 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.