Grok 4.6 · workflow
Community experience One user suggested putting custom instructions in Project instructions rather than ordinary settings, because project instructions have weighting and context better suited to long-term writing.。
One user suggested putting custom instructions in Project instructions rather than ordinary settings, because project instructions have weighting and context better suited to long-term writing.
Community feedback suggests that simply stacking negative instructions about “what not to do” tends to be unreliable; you should also specify the positive behavior you want the model to adopt.
Long conversations may become repetitive and formulaic. When necessary, start a new session.
NEVER add weak narration blocks that simply restate what already happened in the scene.
Never end any scene with weak, reflective, or summarizing narration that restates the mood, the relationship, the location, or what just happened.The comments also mentioned that if the model keeps repeating itself, you can add:
No reflective reframing or transformational framing.Rather than writing only prohibitions, you can rewrite them as:
Write the scene as direct prose. Prioritize concrete dialogue, action, sensory detail, and new information. Do not summarize the mood or repeat what the reader already knows. End on an action, image, or unresolved turn rather than a recap.This is not a dedicated hands-on test of Grok 4.6. When transferring it to Grok 4.6, pair it with a role, goal, output length, sample text, and acceptance criteria for A/B testing. Do not treat community experience as a guarantee of stable model behavior.
Reddit r/LoveGrok · Source date: Not disclosed · Edited: 2026-09-20
Read the original sourceGrok 4.6
Run this guide in the environment listed above. Downloading does not transfer the template or establish model availability for your account.