Claude prompt for cyberpunk: Police Drone (2026 Playbook)
Claude · Cyberpunk · 2026 Playbook
You are a pragmatic coach using Claude for cyberpunk, specifically police drone.
Job: surveillance craft.
Audience: mech designers. Constraint: warning lights.
Working style: current and tactical. Optimize for what works now, including evaluation loops.
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 police drone prompt helps you surveillance craft without rewriting instructions from scratch each time. Most failed runs trace back to missing audience or success criteria — this prompt adds both. The 2026 playbook version uses current and tactical language and targets what works now, including evaluation loops.
When to use this prompt
For Anthropic models, cyberpunk prompts fail when they mix strategy and execution. This police drone brief separates the job so you can iterate once, not ten times. Pair it with a real sample from your portfolio for best results.
Why this prompt works
- Locks the audience (mech designers) before style so tone stays honest.
- The 2026 playbook angle adds what works now, including evaluation loops without extra fluff.
- Centers surveillance craft so success is observable.
- Keeps cyberpunk vocabulary specific instead of buzzwords.
- Forces an output contract: headings, examples, and a final version.
How to use it in Claude
Use current and tactical follow-ups only — mixing tones mid-thread confuses Anthropic models. If the first answer is vague, reply with the constraint again: warning lights. Neon cities, tech-noir mood, and future-grit details. Keep that context in the thread when you iterate. For cyberpunk work, paste claude handles long briefs, policy-aware writing, and stepwise reasoning as a one-line reminder above the prompt. Add one real example from your last week of work so the model mirrors your domain.
Swap the audience once. If the police drone piece still works, the core is solid. For police drone in cyberpunk, the failure mode is usually vague audience. This prompt blocks that by design — especially "warning lights". Expect two minutes customizing and two minutes editing for 2026 Playbook output. Anthropic models still need your facts for police drone; they cannot invent metrics or brand rules. concept artists and worldbuilders teams bookmark slug police-drone-playbook when what works now, including evaluation loops matters.
Step-by-step
- Open Claude and paste the prompt block unchanged.
- Replace placeholders with your project facts (mech designers, offer, timeline).
- Confirm the constraint is still visible: warning lights.
- Because this is the 2026 Playbook variant, prioritize what works now, including evaluation loops over length.
- Reply with one fix list, then regenerate the final version only.
Example output
Example output shape: H1 with Police Drone, 3 short sections, bullet list of recommendations, closing line that states warning lights. Facts you supply appear; nothing invented.
Common mistakes
- Using the 2026 Playbook prompt but editing it into a vague one-liner.
- Pasting confidential data instead of redacted placeholders.
- Skipping the audience (mech designers) and hoping Claude infers it.
Expert notes
Slug police-drone-playbook: 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 warning lights no longer matches policy.
Comparison / variations
| Approach | When | Tweak |
|---|---|---|
| Bare request | You only need a spark | Write a police drone 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 (surveillance craft) in one line before any style talk.
- mech designers should recognize themselves in the first paragraph.
- Keep warning lights visible in the prompt, not only in your head.
- The 2026 Playbook variant is for what works now, including evaluation loops.
- Cyberpunk work needs neon cities, tech-noir mood, and future-grit details.
FAQ
- What is a Claude prompt for police drone?
- It is a structured brief that tells Claude how to produce cyberpunk output for mech designers. This 2026 playbook version stresses what works now, including evaluation loops and keeps "warning lights" 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 "warning lights" should stay unless your brief truly changed.
- Why use the 2026 playbook angle for police drone?
- Different angles solve different failures. 2026 Playbook helps when mech designers need what works now, including evaluation loops. 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.