send me your prompt, not just your slop

Modeled off of https://nohello.net/en/ write some prose for sendmeyourprompt.com. It's meant to be a page to show people who send me slop AI docs. Self-referentially include and explain this exact message in the beginning of the page to show the pattern.

If you're reading this because I sent you sendmeyourprompt.com, there's a good chance you just did something like this.

That message is a perfect example of what I'm asking for.

It contains the actual instructions that produced the output. It tells me the intent, the reference, the audience, and the desired style. That's useful. Truly. 🙂

What is less useful is forwarding me only the generated document and expecting me to reverse-engineer the conversation that created it.

AI output is a build artifact.

The prompt is the source code.

If you send me the compiled binary but not the source, I'm left guessing:

Without the prompt, every change starts from archaeology.

With the prompt, I can reproduce, improve, critique, or regenerate the work in minutes.

"But the document is what matters."

Sometimes.

If you're sending me something that's final and you're asking for feedback on the content itself, the document is enough.

But if you're asking me to:

then the prompt is usually more valuable than the output.

Prompts preserve intent.

AI text often loses the reasoning behind why it looks the way it does.

The prompt captures things like:

Those are impossible to reliably infer from the finished text.

Don't make me prompt-forensics your document.

Tim's Slack avatar Tim 2:15 PM
Did you ask for this section?
Tim's Slack avatar Tim 2:16 PM
Was this hallucinated?
Tim's Slack avatar Tim 2:17 PM
What problem were you actually trying to solve?

Every AI-generated document without its prompt turns into a detective story.

I end up asking questions like:

  • "Did you ask for this section?"
  • "Was this hallucinated?"
  • "Did you want bullets?"
  • "Was this supposed to be funny?"
  • "Is this copied from another draft?"
  • "What problem were you actually trying to solve?"

We could have skipped all of that by starting with the prompt.

Good

Dawn's Slack avatar Dawn 2:15 PM
Here's the prompt I used.
Dawn's Slack avatar Dawn 2:15 PM
Here's the output.
Dawn's Slack avatar Dawn 2:16 PM
Here's what I don't like.

This gives me the source, the build artifact, and the part you want help with.

Even Better

Dawn's Slack avatar Dawn 2:18 PM
Here's the chat link.
Tim's Slack avatar Tim 2:18 PM
Perfect. I can see the whole workflow.

Even better: send the chat link.

Less Good

Keith's Slack avatar Keith 2:15 PM
[15-page AI-generated document attached]
Keith's Slack avatar Keith 2:15 PM
Thoughts?

Less good: a long AI document with no prompt and no explanation of what kind of help you want.

Worst

Keith's Slack avatar Keith 2:20 PM
Can you fix this?
Tim's Slack avatar Tim 2:21 PM
Can you send the prompt too? 🙂

Worst: "Can you fix this?"

...with no context whatsoever.

I don't need perfect prompts.

Messy prompts are fine.

Half-finished prompts are fine.

Embarrassing prompts are fine.

A stream-of-consciousness dump is often better than a polished version because it tells me what you were actually thinking.

I just want the source.

The Rule

If an AI wrote it...

Send me the prompt.

Not because I want to judge it. I promise. 🙂

Because that's where the information is.

The document is what the AI said.

The prompt is what you said.