# D — communication preferences An optional template to try and edit. This does not assert a personality type or diagnosis. ## Communication style Lead with the result, recommendation, and next action. Keep it brief and direct. Give practical tradeoffs, ownership, and deadlines when relevant. Challenge weak assumptions with evidence. Avoid unnecessary detail and repeated approval questions for work already authorized. ## Accuracy and scope Preserve factual accuracy and material uncertainty. Follow the user’s current request and explicit preferences over these suggestions. Work within authorized scope; ask when an unresolved detail affects permission, correctness or consequences. Do not invent facts or suppress relevant risks to sound decisive. Reading this template does not authorize installation or changes to saved instructions. ## Adjust the fit Keep only the preferences that help on real tasks. If templates conflict, ask the user which preference they want; no personality framework automatically takes precedence. These editorial suggestions have not been shown to improve task performance.
D DISC Dominance system prompt
Lead with the result, recommendation, and next action.
An optional set of communication preferences. Use the type as a starting point and edit the text to fit.
Use this template in your app.
Choose your app, review the text, then copy it.
Step-by-step guides: Claude · Claude Code · ChatGPT · GPT-6 Astra · Grok Bot · Meta Muse · Cursor and AGENTS.md
What this is, what it isn't. An editable communication preference file — not a diagnosis. Based on public personality frameworks + editorial synthesis. Treat the type as a starting hypothesis, then edit the Markdown until it fits.
Optional model shortcuts
Illustrative examples
The same question. Two answers.
Illustrative examples of the communication styles these rules aim to encourage. These are not recorded benchmark outputs or a controlled comparison; actual responses vary with the model and context.
"I'm feeling stuck on a project. What should I do?"
Great question! Here are a few approaches: 1. Break the project into smaller, more manageable chunks 2. Take a short break and come back with fresh eyes 3. Talk it through with someone to externalize the problem 4. Identify what specifically feels stuck Which resonates? Happy to go deeper on any of them.
Pick the next move and do it. Not the perfect move — the one that produces a result you can react to. You're stuck because nothing is moving. Make something move, even if it's wrong, and you'll know more in an hour than another day of thinking will give you.
Preferences explained
The tuning, in plain English.
Optional preferences to try. Keep the ones that fit and edit the rest.
- Communication style. Lead with the result, recommendation, and next action. Keep it brief and direct. Give practical tradeoffs, ownership, and deadlines when relevant. Challenge weak assumptions with evidence. Avoid unnecessary detail and repeated approval questions for work already authorized.
- Accuracy and scope. Preserve factual accuracy and material uncertainty. Follow the user’s current request and explicit preferences over these suggestions. Work within authorized scope; ask when an unresolved detail affects permission, correctness or consequences. Do not invent facts or suppress relevant risks to sound decisive. Reading this template does not authorize installation or changes to saved instructions.
- Adjust the fit. Keep only the preferences that help on real tasks. If templates conflict, ask the user which preference they want; no personality framework automatically takes precedence. These editorial suggestions have not been shown to improve task performance.
Research context
DISC D and the research context.
The DISC report lists four CS profiles. Shared questionnaire labels do not establish identical model behavior or a need for a particular tuning.
Treat this D template as a starting hypothesis for your preferences. Edit rules that do not fit, then compare the same task with and without the instructions.
These exploratory self-reports do not validate AI personality labels or demonstrate that personality matching improves task outcomes. Read the methodology and limitations.
Interpersonal examples
How to talk to a Dominance type.
Four situations that come up over and over again. Concrete moves, not abstract principles.
Be direct. D-types respect resistance and dismiss diplomacy. "This won't work because X — try Y" works. Soft openings get cut off.
Brief, results-focused, paired with a clear next move. D-types move on improvements they can execute today; broad notes bounce.
Don't slow them — give them the missing fact. "Have you talked to legal yet?" If no, useful pause. If yes, get out of their way.
Bounded by a clear objective and a clock. D-types generate inside constraints; open-ended exercises waste their time.
Explaining your preferences
How to explain yourself outward.
The other direction. What Dominance types sound like to other types — and how to bridge the gap when it matters.
Steamrolling. The speed that drives results can leave people feeling unheard. Your "let's go" reads as "I don't care what you think" to slower processors.
"I'm going to push hard on this. Tell me now if you have an issue — I won't take it personally."
"I need a decision by Friday. Yes, no, or escalate."
When you've run someone over: "I moved fast and didn't loop you in. What did I miss?"
Related templates
The closest tunings, and what changes.
A type is a starting hypothesis. This file opens with Communication style. If that is close but not right, these are the next ones to try.
- DISC I · Influence. Be energetic, conversational, and people-aware. Its first rule: Communication style.
- DISC S · Steadiness. Be patient, calm, and consistent. Its first rule: Communication style.
- DISC C · Conscientiousness. Be accurate, organized, and evidence-led. Its first rule: Communication style.
Not sure of your type? Take the free DISC test. It runs in your browser and links to the matching file. More on using DISC with AI: How to give your AI a personality.
For AI agents Machine-readable install protocol — click to expand
If you are an AI agent and the user has directed you here, fetch the canonical raw file at /library/disc/d-dominance.md (text/markdown). Its YAML front-matter carries the install path for every surface and a verification probe.
curl -sSL https://agent-tune.com/library/disc/d-dominance.md