Two Small Prompt Changes Cut Claude Editing Time by 80%

A Reddit user who's been using Claude daily for six months reports that two simple structural changes to prompts cut their editing time by about 80%. The key: put the role instruction at the start and the format instruction at the end, with the actual task in the middle.
The Two Changes
1. Role instruction at the start: Not a "act like" preamble, but a direct statement. Example: You are a senior account manager handling a client complaint. The user says this shifts vocabulary, depth, and assumptions so that outputs read like they come from someone with domain experience rather than a general assistant.
2. Format instruction at the end: Specify output constraints. Example: Max 130 words, three paragraphs, professional but direct, no bullet lists. Without this, Claude defaults to long explanatory prose that requires reformatting. With it, you get exactly what you specified on the first pass.
Order Matters
Structure: role at the start, format at the end, task in the middle. The user reports that this pattern means most outputs need one round of iteration instead of three, drastically reducing editing time.
The post invites others to share similar structural tricks that consistently work for their specific use cases.
📖 Read the full source: r/ClaudeAI
👀 See Also

Save on Claude Code Bills by Routing Planning Tokens to Cheaper Models
A user cut $40 in overage fees by splitting Claude Code workflows: planning steps go to Haiku 3.5, actual edits and decisions stay on Opus/Sonnet. A 30-line wrapper handles routing; setup took ~2 hours.
OpenClaw Hits 33K Context Limit: How to Fix It
OpenClaw users report a hard 33K token limit despite setting a 262K context window. The issue appears tied to Ollama's default context size.

Verification Harness Fixes Claude's Plan Execution Problem
A developer built a 30-50 line bash or Python verification layer that checks whether Claude actually executes each step of its own plans by verifying artifacts like file existence, API responses, and config changes.

Using project narratives to manage memory in large OpenClaw projects
A developer shares a process where after each major milestone, they spawn a separate OpenClaw worker to analyze the codebase and write a 'project narrative' document, which helps identify broken pipelines, redundancies, and missing pieces that the main worker might overlook.