Claude prompt for cyberpunk: Android Repair (With Examples)
Claude · Cyberpunk · With Examples
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: practical. Optimize for few-shot samples and before/after pairs.
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. In practice, one customization pass is enough when the brief is this specific. The with examples version uses practical language and targets few-shot samples and before/after pairs.
When to use this prompt
Claude shines at cyberpunk work when you state the observable outcome: workshop scene. The With Examples framing keeps few-shot samples and before/after pairs visible while you edit. Pair it with a real sample from your portfolio for best results.
Why this prompt works
- Forces an output contract: headings, examples, and a final version.
- Uses practical language that matches how practitioners actually brief work.
- Locks the audience (storyboarders) before style so tone stays honest.
- Separates draft from critique so you can steal the structure later.
- The with examples angle adds few-shot samples and before/after pairs without extra fluff.
How to use it in Claude
Save the winning variant for android repair — teams with a short library ship faster. Use practical follow-ups only — mixing tones mid-thread confuses Anthropic models. Ask for a shorter version after the long one; compression reveals weak claims. Name the success metric aloud: workshop scene. If the draft cannot pass it, do not polish prose yet. This With Examples path is for storyboarders who care about workshop scene.
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 With Examples 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-examples when few-shot samples and before/after pairs 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.
- Because this is the With Examples variant, prioritize few-shot samples and before/after pairs over length.
- 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 With Examples 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 With Examples variant, they usually care about few-shot samples and before/after pairs 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.
- Ship a draft, then tighten. Do not chase a perfect first token.
- Document what changed when you customized slug android-repair-examples.
- Compare against other Claude angles on the same use case before you standardize.
- Keep tools that make sense visible in the prompt, not only in your head.
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 with examples version stresses few-shot samples and before/after pairs 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 with examples angle for android repair?
- Different angles solve different failures. With Examples helps when storyboarders need few-shot samples and before/after pairs. 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.