Claude prompt for cyberpunk: Android Repair (Workflow)
Claude · Cyberpunk · Workflow
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: operational. Optimize for step order, checkpoints, and handoffs.
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.Looking for a Claude prompt for android repair? Start here — the workflow angle focuses on step order, checkpoints, and handoffs. Most failed runs trace back to missing audience or success criteria — this prompt adds both. The workflow version uses operational language and targets step order, checkpoints, and handoffs.
When to use this prompt
Claude shines at cyberpunk work when you state the observable outcome: workshop scene. The Workflow framing keeps step order, checkpoints, and handoffs visible while you edit. Pair it with a real sample from your portfolio for best results.
Why this prompt works
- Locks the audience (storyboarders) before style so tone stays honest.
- Keeps cyberpunk vocabulary specific instead of buzzwords.
- The workflow angle adds step order, checkpoints, and handoffs without extra fluff.
- Repeats the hard constraint: tools that make sense.
- Centers workshop scene so success is observable.
How to use it in Claude
Use operational follow-ups only — mixing tones mid-thread confuses Anthropic models. 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. Ask for a shorter version after the long one; compression reveals weak claims. If the first answer is vague, reply with the constraint again: tools that make sense.
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 Workflow 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-workflow when step order, checkpoints, and handoffs 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 Workflow prompt but editing it into a vague one-liner.
Expert notes
Slug android-repair-workflow: a concept artists and worldbuilders-oriented cyberpunk brief. Neon cities, tech-noir mood, and future-grit details. Pair it with one real asset from your portfolio before the second run.
Refresh quarterly: Claude models change. Keep constraints; update examples. Mark the page stale if tools that make sense no longer matches policy.
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
- storyboarders should recognize themselves in the first paragraph.
- If text output drifts, re-anchor with tools that make sense.
- State the job (workshop scene) in one line before any style talk.
- Ship a draft, then tighten. Do not chase a perfect first token.
- 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 workflow version stresses step order, checkpoints, and handoffs 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 workflow angle for android repair?
- Different angles solve different failures. Workflow helps when storyboarders need step order, checkpoints, and handoffs. 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.