Claude prompt for cyberpunk: Street Vendor (Workflow)
Claude · Cyberpunk · Workflow
You are a systems thinker using Claude for cyberpunk, specifically street vendor.
Job: night market stall.
Audience: worldbuilders. Constraint: props with function.
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.Claude users in cyberpunk use this street vendor prompt to ship faster drafts that respect "props with function". 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
When worldbuilders tackle street vendor inside cyberpunk, the hard part is not the model — it is the brief. Neon cities, tech-noir mood, and future-grit details. This prompt encodes that context so Claude does not guess. Pair it with a real sample from your portfolio for best results.
Why this prompt works
- Keeps cyberpunk vocabulary specific instead of buzzwords.
- The workflow angle adds step order, checkpoints, and handoffs without extra fluff.
- Uses operational language that matches how practitioners actually brief work.
- Repeats the hard constraint: props with function.
- Forces an output contract: headings, examples, and a final version.
How to use it in Claude
Neon cities, tech-noir mood, and future-grit details. Keep that context in the thread when you iterate. Use operational follow-ups only — mixing tones mid-thread confuses Anthropic models. If the first answer is vague, reply with the constraint again: props with function. Redact client names; keep structure. Slug street-vendor-workflow is your canonical URL for this brief. For cyberpunk work, paste claude handles long briefs, policy-aware writing, and stepwise reasoning as a one-line reminder above the prompt.
Ask for a checklist worldbuilders would use. Then grade the draft against night market stall. For street vendor in cyberpunk, the failure mode is usually no example. This prompt blocks that by design — especially "props with function". Expect two minutes customizing and two minutes editing for Workflow output. Anthropic models still need your facts for street vendor; they cannot invent metrics or brand rules. concept artists and worldbuilders teams bookmark slug street-vendor-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 (worldbuilders, offer, timeline).
- Confirm the constraint is still visible: props with function.
- 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 Street Vendor, 3 short sections, bullet list of recommendations, closing line that states props with function. Facts you supply appear; nothing invented.
Common mistakes
- Deleting "props with function" to save space — that is usually the whole point.
- Ignoring the output contract headings.
- Using the Workflow prompt but editing it into a vague one-liner.
Expert notes
Practitioners choose Workflow when street vendor needs step order, checkpoints, and handoffs. Claude from Anthropic still needs your facts — especially for props with function.
For cyberpunk, compare this Workflow prompt against the Quick Start and Expert angles on the same use case. Keep the structure that scores higher on night market stall.
Comparison / variations
| Approach | When | Tweak |
|---|---|---|
| Bare request | You only need a spark | Write a street vendor 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
- Cyberpunk work needs neon cities, tech-noir mood, and future-grit details.
- worldbuilders should recognize themselves in the first paragraph.
- Keep props with function visible in the prompt, not only in your head.
- Claude improves when you paste a real snippet or reference still.
- Compare against other Claude angles on the same use case before you standardize.
FAQ
- What is a Claude prompt for street vendor?
- It is a structured brief that tells Claude how to produce cyberpunk output for worldbuilders. This workflow version stresses step order, checkpoints, and handoffs and keeps "props with function" 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 "props with function" should stay unless your brief truly changed.
- Why use the workflow angle for street vendor?
- Different angles solve different failures. Workflow helps when worldbuilders 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.