Before your next AI session, spend 30 seconds answering 5 short questions. You’ll spend the rest of the session actually working instead of correcting.
That’s the idea behind a session seed, spotted this week in r/PromptEngineering. Posted by u/PitBrvt, it’s a simple pre-chat ritual that sets tone, depth, and behavior before you type a single real message. Think of it like briefing a contractor before handing them a project. The more context you give upfront, the less time you spend on revisions later. Most people skip this step entirely, then wonder why the model feels off after the first five messages.
What the 5 Questions Actually Cover
Each one targets a different axis of how the model behaves:
- 🎯 PILLAR: tone, clarity, and how much drift you’ll tolerate. This is the personality layer. “Direct, no fluff, push back if I’m wrong” is a PILLAR answer. So is “warm, patient, explain things step by step.” You’re telling the model what kind of collaborator you want it to be.
- SHAPE: your domain or task type. This helps the model pick relevant analogies, frame its assumptions, and skip context you don’t need. “Software engineer working on API design” is a shape. “Freelance copywriter for health brands” is another. The more specific you are here, the less the model defaults to generic.
- PACE: response density (Tight, Neutral, or Breathe). Tight means dense, no padding, get to the point fast. Breathe means give the idea room to expand. Neutral is the default most people never override, and then wonder why responses feel bloated or oddly clipped.
- DEPTH: surface-level vs. deep threading. Surface is “give me the answer.” Thread is “walk me through the reasoning.” The difference matters a lot depending on whether you’re trying to learn something or just trying to ship something.
- POSTURE: does the AI agree, push back, or blend both. Harmonize means it follows your lead. Counterbalance means it challenges you. Hybrid lands somewhere in between. Most people run on Harmonize by default without realizing it, which is exactly why AI starts to feel like a yes-man over time.
You fill in the answers, paste the block at the top of your chat, and the model uses it as a behavioral frame for everything that follows. Five fields. About thirty seconds. Done.
Why Vague Answers Still Work
One commenter nailed it: the vagueness is the feature. You’re not giving the model rigid instructions. You’re giving it context that shapes interpretation. Even a messy answer to “PILLAR” tells the model something about how you think and what register you want.
The model calibrates. It doesn’t need precision. It needs direction.
Think about how this works in practice. If your PILLAR answer is “casual but smart, skip the fluff,” the model won’t treat that as a spec sheet. It reads it as a signal for the whole conversation: use shorter sentences, drop the “Certainly!” opener, stop hedging every answer with disclaimers. You didn’t have to say any of that explicitly. The context carries it forward.
That’s different from a system prompt, which is usually written by a developer trying to lock down behavior for a product. A session seed is conversational. You’re writing it for yourself as much as for the model. The act of filling it in forces you to think about what kind of session you actually want, which makes you a sharper collaborator before you even start typing.
Where This Is Actually Useful
This works best when:
- You have a long working session with a clear goal (writing, research, code review). The longer the session, the more value the seed delivers. In a 5-message exchange, drift doesn’t matter much. In a 40-message working session, it matters a lot.
- You want consistent behavior across many exchanges without repeating yourself. Instead of saying “be more concise” for the fourth time in a row, you set PACE to Tight once at the top and move on.
- You’re opening a fresh chat and want to reproduce the tone from a previous session. If a session last week felt exactly right, save the seed that started it. Paste it into a new chat and get back to that state in seconds instead of recalibrating for 10 minutes.
Without something like this, models drift. They get formal. They start hedging. They forget the energy you set 20 messages ago. You end up spending cycles correcting behavior instead of doing the actual work. A session seed is cheap insurance against that pattern. It costs 30 seconds. The payoff is a session that stays on track without you babysitting it.
Prompt of the Day 📋
Copy this and fill it in before your next session:
=== SESSION START === 1. PILLAR (tone + clarity + drift level): ___ 2. SHAPE (domain / task): ___ 3. PACE (Tight / Neutral / Breathe): ___ 4. DEPTH (Surface / Thread): ___ 5. POSTURE (Harmonize / Counterbalance / Hybrid): ___ === END ===
A few tips on filling it in well. For PILLAR, one sentence is enough. For SHAPE, be specific but not exhaustive. For PACE, if you’re unsure, start with Tight and adjust from there. For DEPTH, pick based on your goal for the session: doing vs. learning. For POSTURE, try Counterbalance at least once. It feels uncomfortable at first. It’s also where the most useful friction lives.
Run it once before a real work session. See if you end up correcting the AI less. That’s the test.
Want more prompts like this, plus the AI tools and tactics actually worth your time? Subscribe to Cyber Corsairs and get it every week.
Frequently Asked Questions
Q: Do I really need all 5 questions, or is there a simpler way?
Not necessarily. One commenter pointed out you can just introduce yourself naturally with your specific task, that works too. But if you want structure, PILLAR and SHAPE do about 70% of the work, so at minimum lock in your session stance (tone) and your domain/task. The other three are mostly insurance policies.
Q: How detailed should my answers be?
There’s a sweet spot. Answers that are too vague cause the model to default to “helpful assistant” mode and the scaffolding falls apart. Based on testing, roughly 8, 12 content words across all 5 answers is the threshold, enough to narrow down what kind of session this is, but not so rigid that you lose flexibility.
Q: Does the order of these questions actually matter?
Yes, more than expected. Tone-first (PILLAR before SHAPE) keeps the model in your voice but lets it wander on topic. Domain-first does the opposite, stays on-topic but can drift in register. Worth A/B testing both to see which suits your workflow.
Q: Why do vague answers still create useful scaffolding?
The answers act as a “prior” that narrows the space of likely next moves far more than zero answers would. Even fuzzy anchors give the model a sense of what kind of session this is, and that constraint alone is surprisingly powerful.
Q: Should I show the model examples of what good output looks like?
One commenter suggests adding a 6th question with a sample output. That shifts the seed from “this is the context” to “this is what the session must produce”, a calibration point that stance and shape questions can’t provide alone.
A lightweight 5‑question session seed to align tone, depth, and behavior
by u/PitBrvt in PromptEngineering