Updated: 2026-02-20
Prompts only work when they produce a decision. These are operational trading psychology prompts you can answer in seconds, track over time, and turn into guardrails when your worst state shows up.
Most trading psychology advice fails because it is not measurable. It tells you to be calmer, more patient, or more confident. Those are feelings, not levers.
Prompts become useful when they do three things: they force you to name state, they force you to name risk, and they force you to choose an action. If a prompt does not change what you do next, it is entertainment.
The goal is not self-expression. The goal is process control. You are building a system that protects you during your worst sessions, not writing a memoir of your best sessions.
To keep it honest, treat prompt answers like data. Use short answers. Score them. Review the scores weekly. Then convert the failure mode into a constraint that runs even when you do not feel like it.
A session starts before the first click. If you begin trading without a stop condition, the market becomes your stop condition.
Use these prompts as a 60-second pre-flight. If your answer is bad, you do not need courage. You need a smaller plan or a no-trade decision.
Write answers in a single line. The point is to reduce cognitive load, not increase it.
Most emotional damage comes from decision points inside the trade: adding size, moving stops, taking random partials, or revenge re-entering after a stop.
The trick is not to be emotionless. The trick is to create friction at the exact moment emotion tries to rewrite your plan.
If you do not want to write mid-trade, pick one prompt and use it as a gate. One gate can save a month.
Post-trade prompts are not for analysis. They are for labeling. If you can label a trade consistently, you can review it later without lying to yourself.
Use a three-part prompt: plan, execution, state. Keep it binary where possible. Your future self will thank you.
Weekly review is where psychology becomes an engineering problem. You are not asking 'why am I like this'. You are asking 'what condition causes damage, and what constraint reduces it'.
Use prompts that connect directly to measurable outcomes: average R, max loss, rule breaks, and time-of-day patterns.
The output should be one constraint for next week. If you output more, you will enforce none.
Different traders fail differently. Choose the two failure modes that cost you the most and focus prompts there. Focus beats coverage.
Use the prompts that you can still answer when you are triggered. If you only answer them when you are calm, they will not protect you when it matters.
If you do not score prompts, you cannot see progress. You will rely on memory, and memory is not a risk system.
Use a simple 0/1/2 score for key prompts. Then track weekly averages. You are not trying to be perfect. You are trying to reduce the frequency of your worst state.
Example: state score 2 means reduced size mode. Rule-break score 2 means mandatory cooldown. You want the score to trigger behavior automatically.
Prompts do not work in isolation. They work when the answer changes what you are allowed to do next.
Pick one guardrail that is easy to enforce: a trade cap, a max daily loss, a cooldown timer, or a checklist gate for entries. Then wire prompt scores to that guardrail.
This is how you turn psychology into an operating system. Emotion still happens, but the damage does not compound.
Start with 3-5 total prompts across the whole workflow. If you use more, you will stop answering them when you are stressed. Add only after the habit is stable.
No. Short prompts win because they are sustainable. You can do reflection later in weekly review, but in-session prompts should create friction and clarity fast.
Score it and track outcomes by score. If a high score correlates with rule breaks and drawdown, the prompt is correctly identifying risk state and should trigger constraints.
That is the signal. Simplify the prompts and attach a constraint that is harder to bypass (trade cap, lockout, or mandatory cooldown).
Yes. Tiltless is designed around behavior tags and weekly review loops so prompt answers become measurable cohorts and lead to enforceable corrections.
See plans and run one weekly review loop with Tiltless: edges, leaks, and enforceable next actions.
