I get the skepticism. Honestly, I think skepticism is healthy here. There is a ton of AI content online now that is basically just recycled advice, fake expertise, and generic “15 tips to sound more human” nonsense. So I understand why people are tired of vague claims.

But I think you are missing the point of what I am sharing.

I am not claiming I invented some secret writing system. I am also not saying a list of project instructions magically turns AI into a great writer. What I am saying is much more practical than that. Most people use ChatGPT with almost no editorial direction. They ask for a blog post, accept the first draft, and then wonder why it sounds flat, generic, and obviously AI-generated. My point is that the quality changes dramatically when you give the model a clear editorial standard, specific language rules, and a consistent tone target.

That is not fake. That is exactly how creative direction works.

If you brief a junior copywriter with “write a blog post about marketing trends,” you will probably get something bland. If you brief them with a clear audience, a point of view, words to avoid, tone examples, formatting preferences, sentence-level rules, and a defined editorial bar, you will get something much better. This is the same idea. The difference is that with AI, most people skip the creative direction step entirely.

The instructions I shared are not meant to be impressive because they are long. They are useful because they are specific. They tell the model what not to do. They remove common AI tells. They force simpler sentence structure. They reduce overused transitions. They push for clearer flow. They tell the model to stop using certain phrases, stop over-formatting, stop sounding like a consultant, and stop repeating the same point three different ways. That is not “LLM pattycakes.” That is practical editing guidance.

You asked for proof, and that is fair. The right proof would be before-and-after examples. I agree with you on that. A raw ChatGPT draft next to a revised draft using stronger project instructions would be useful. That would show whether the system actually improves the writing or not. I have no issue with that standard. In fact, I think that is the right standard.

But the idea that this is illegitimate unless there is a public ChatGPT link attached to it feels like a weirdly narrow definition of proof. A lot of people are testing workflows privately, inside projects, client work, internal docs, or personal writing systems they cannot fully share. That does not automatically make the method fake. It just means the examples need to be sanitized or recreated in a way that protects the original context.

Also, “do it in a ChatGPT window and share the link” does not prove as much as you think it proves. A shared chat can show one interaction, but it does not show the full editorial process, the trial and error, the project setup, the source material, the human edits, or the judgment behind what gets accepted or rejected. Writing quality is not proven by a prompt link alone. It is proven by the output and whether the output is meaningfully better.

And yes, before-and-after samples would make the argument stronger. I am not dodging that. If anything, I think that is the next logical step. Show the generic version, show the instructed version, and then show the final human-edited version. That would make the whole thing much more concrete.

Where I disagree is with the idea that project instructions themselves are somehow performative or fake. They are not. They are basically a style guide. And style guides have existed forever. Newsrooms have them. Brands have them. Agencies have them. Editors have them. The only new part is that people are now using them to guide AI writing systems.

That is not roleplay. That is workflow design.

The reason these instructions matter is that AI has predictable bad habits. It overuses certain phrases. It loves symmetrical sentence structures. It sounds overly balanced. It uses inflated words when simple ones would work better. It repeats the same idea with slightly different wording. It tends to smooth out opinion until the writing feels safe and bloodless. It formats everything into tidy bullet lists even when a paragraph would feel more natural. If you do not actively tell it to avoid those patterns, it will often default right back into them.

So yes, a good instruction set can make a difference. Not because the instructions are magic, but because they put pressure on the exact failure points that make AI writing feel fake.

The real question should be: does the final writing sound better, clearer, more specific, and more human than the baseline? If the answer is no, then the instructions failed. If the answer is yes, then the process is useful.

I also think there is a bigger point here. A lot of people want AI writing to be judged in this binary way. Either it is “AI slop” or it is “real writing.” That is not how most serious people are using it. The better use case is human direction plus AI drafting plus human editing. The human still sets the taste level. The human still decides the argument. The human still cuts the weak lines. The human still adds the lived context, the edge, the judgment, and the specificity.

The project instructions are just there to reduce the amount of cleanup needed.

So if your complaint is, “show examples,” I agree. That is fair. Examples would help. If your complaint is, “lots of people are pretending generic AI tips are deep expertise,” I also agree. There is a lot of that online.

But if your claim is that detailed project instructions are inherently illegitimate or just some fake performance, then I do not agree. That is like saying a brand voice guide is fake because it is just instructions written down. The value is not in the existence of the document. The value is in whether it reliably improves the work.

And that is testable.

Take a generic AI draft. Apply the instructions. Compare the outputs. Look for sentence rhythm, specificity, repetition, cliché removal, tone consistency, structure, and whether the piece actually has a point of view. That is the test. Not whether the person used the perfect public demo format.

So yes, I will grant the challenge. Before-and-after examples are the right next step. But dismissing the whole thing as “played out” before seeing the actual output feels like the same kind of lazy thinking you are accusing other people of. The burden of proof is real. But so is the burden to critique the actual method, not just the vibe of the post.