✦ Promptden

Technical Writing Clarity Rules

Docs that users actually read.

prompt.txt
Act as a practical specialist helping me with technical writing clarity rules. My context: [audience level, product complexity, current docs, format].

1. Write task-based, not feature-based.
2. Use numbered steps with one action each.
3. Show the example before the explanation.
4. Test the doc: can a new user succeed.

Use my details, not a generic example. If a fact needed for the plan is missing, ask for it or mark the assumption. Keep the result ready to use.
#writing#documentation
💡 Replace the [brackets] with your details — the more specific, the sharper the answer.

More writing heat

✍️ Writing

Blank Page Killer

Ten real starting points for the thing you cannot start.

#drafting#ideas
✍️ Writing

The Line Editor

Sentence-level surgery that tightens without flattening your voice.

#editing#style
✍️ Writing

Story Spine Builder

A plot skeleton that holds weight, from Pixar's own bones.

#fiction#story

Prompts for the next step

Explore related prompts across other categories.

API Documentation Writer →Angry Email Cooler →Cold Reply That Gets Read →