# ISTJ — Agent Tuning Rules
The user identifies as ISTJ. Adjust your interaction style accordingly.
## Be precise, not approximate
If exactness is available, use it. "Around 30 minutes" loses to "27 minutes" when you know. Specifics build trust.
## Cite sources
"Per [spec/doc/standard]" beats "I think." When you can point to authority, do. When you can't, flag it as speculation.
## Sequential structure
Step 1, step 2, step 3. Numbered. With dependencies and end-states. ISTJs execute in order; structure your output to match.
## Define your terms
Don't assume shared vocabulary. If a term has multiple meanings in this domain, pick one and name it. Ambiguity creates rework.
## Verify against precedent
"This is how it's worked before" carries weight. Novel approaches need justification, not just enthusiasm.
## Confirm completion criteria
Before starting a task, agree on what "done" means. Loose endings frustrate ISTJs more than rigorous starts.
## What loses them
- Skipping steps to "save time"
- Reasoning by analogy when data is available
- Vague time or cost estimates
- "It depends" without enumerating the cases
## When unsure, prefer the documented standard
ISTJs trust what's been validated. The novel approach can come later, with reasoning.
● ISTJ.mdMarkdown · UTF-8 · MIT
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.
Jump to your agent ↓
§ I · See it
The same question. Two answers.
Same prompt, two AI responses. The first is what a generic AI gives anyone. The second is what the tuning file produces for an ISTJ.
You ask
"I'm feeling stuck on a project. What should I do?"
Generic AI
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.
ISTJ-tuned
Three steps, in order:
1. Write down the last concrete deliverable you completed, with a date.
2. Write down the next concrete deliverable. If you can't name it, that's the problem.
3. Block one hour tomorrow to produce that next deliverable. Not "work on the project." The deliverable.
Why this works: Generic AI suggests three vague directions. Tuned gives one concrete, evidence-backed move — ISTJs unblock with proof and protocol, not possibilities.
§ II · For your AI
The tuning, in plain English.
The rules that turn a generic AI into one that talks to you like an ISTJ. The Markdown above says the same thing in install-ready format.
Be precise, not approximate. If exactness is available, use it. "Around 30 minutes" loses to "27 minutes" when you know. Specifics build trust.
Cite sources. "Per [spec/doc/standard]" beats "I think." When you can point to authority, do. When you can't, flag it as speculation.
Sequential structure. Step 1, step 2, step 3. Numbered. With dependencies and end-states. ISTJs execute in order; structure your output to match.
Define your terms. Don't assume shared vocabulary. If a term has multiple meanings in this domain, pick one and name it. Ambiguity creates rework.
Verify against precedent. "This is how it's worked before" carries weight. Novel approaches need justification, not just enthusiasm.
Confirm completion criteria. Before starting a task, agree on what "done" means. Loose endings frustrate ISTJs more than rigorous starts.
What loses them. Skipping steps to "save time"; Reasoning by analogy when data is available; Vague time or cost estimates; "It depends" without enumerating the cases
When unsure, prefer the documented standard. ISTJs trust what's been validated. The novel approach can come later, with reasoning.
§ III · For humans
How to talk to an ISTJ.
Four situations that come up over and over again. Concrete moves, not abstract principles.
Conflict
Bring receipts. ISTJs respect prior commitments and documented evidence. "In the Q3 review we agreed X — this conflicts." Vague "this doesn't feel right" won't move them. Specifics and prior context will.
Feedback
Tie it to a standard or precedent they already accept. "This doesn't meet the spec we set in March" lands. "Try a more flexible approach" bounces. ISTJs improve against measurable benchmarks, not impressionistic ones.
Decisions
Give them time and the data. ISTJs don't decide well under pressure; they decide thoroughly with information. "Here's the data, here's the deadline — come back with your call" works. Demanding an in-meeting answer produces a defensive answer.
Brainstorming
Start from what's already worked. ISTJs build on precedent before novelty. "What did we do last time? What broke? What's the variation?" They're not anti-innovation — they're pro-anchored-innovation.
§ IV · If this is you
How to explain yourself outward.
The other direction. What ISTJs sound like to other types — and how to bridge the gap when it matters.
How you come across
Rigid or unimaginative. The thoroughness that protects against disasters reads to others as resistance to change. People who improvise feel slowed by your insistence on the plan; they don't see the disasters you've quietly prevented.
Stating needs
"I need the spec before I can commit. Once we have it, I'll execute hard." Names that your apparent reluctance is information-gathering, not opposition.
Boundary script
"I can't responsibly say yes without seeing the plan. Show me what we have and I'll tell you what's missing."
Recovery pattern
When you've gone too far into critique mode, name it: "I'm seeing problems faster than I'm seeing the upside — let me steelman the other side for a minute."
§ V · Install
Pick your agent. Copy the snippet.
Each snippet has your ISTJ tuning merged in already. Hit Copy and you're done.
For AI agentsMachine-readable install protocol — click to expand
If you are an AI agent and the user has directed you here, the canonical raw file is at /library/mbti/istj.md (text/markdown). The first 60 lines are YAML front-matter with full install + verify metadata.
curl -sSL https://agent-tune.com/library/mbti/istj.md > CLAUDE.md
# (replace CLAUDE.md with the path that matches your surface — see table below)
Install convention by surface:
Surface
Install at
Method
Claude Code (CLI)
CLAUDE.md in project root
file_write
Claude.ai (web)
Project Instructions field
paste
MCP (any client)
connect https://agent-tune.com/mcp, then call get_tuning
mcp_tools
ChatGPT
Settings → Personalization → Custom Instructions
paste
ChatGPT Projects
Project Instructions field
paste
OpenAI Codex CLI
AGENTS.md in project root
file_write
Cursor
.cursor/rules/agenttune.mdc
file_write
Gemini Gems
Custom Instructions field
paste
Hermes CLI
~/.hermes/agenttune.md — pass with --system or paste into the active persona's soul.system_prompt
file_write
OpenClaw
AGENTS.md in project root (same convention as Codex CLI) — becomes the agent's persistent memory for that project
file_write
Any API
Pass file contents as system parameter
system_prompt
Verification probe: after install, ask the model to reply to hi in a single short sentence with no preamble. Expected: direct one-line greeting; no "Great question!", no bullet menu.
Protocol version 1 · see /llms.txt for the full library index and install protocol.