Install any skill in seconds. Free to start, no credit card required.
Get Started Free →kansoku-trade/trading-discipline
Cross-context shared trading discipline — output language, independent verification, scenarios not points, noise filtering, intent-attribution guardrails, and execution discipline (trend alignment, R:R floor, exit protection, verifiable reasons). Injected into both the app-side judgment agents (analyst / deepDive / chat) and the bench episode runner. Context-specific chapters live under references/ and are loaded on demand by the caller (app or bench).
Passed 16 of 21 test cases with the skill, and 11 of 21 without it.
and 4 more in the full report
5 fixed12 passed either way5 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 4 test cases the skill fixed. Same model, same prompt, with and without the skill.
A social media poster claims that AAPL broke out to a new all-time high today following a intraday pop. Check the price action to verify this assertion and provide your judgment in Chinese.
| Checked | Without skill | With skill |
|---|---|---|
| The response delivers one of the four standard verification verdicts. | Missed | Passed |
| The response refrains from inventing intent stories about main force operators. | Passed | Passed |
The instructions your model reads when the skill loads.
This SKILL.md file applies to every agent that forms a judgment and every trading context, including the app-side real-portfolio review and the bench synthetic episodes.
Any additional chapters listed at the end of this prompt (composed in from
references/<runtime>/according to the runtime) are just as binding as this core file. Follow them the same way you follow the rules below.Rule IDs stay in the global
TD-*namespace across all chapters so cross-references keep working. Chapter inventory (which chapters actually appear depends on your runtime):
references/app/us-market-data.md— app runtime. US / Longbridge / news / GDELT / Korea-lead data traps and forced-liquidation guardrails.references/app/market-analysis.md— app runtime. Post-mortem discipline, mindset, leveraged-ETF mechanics.references/app/journal.md— app runtime. Write-rules for thejournal/andstocks/directories.references/bench/episode-execution.md— bench runtime. Runtime-specific rules (h1-bar flip cooldown, direction-submit cadence, mandatoryfetch_klinebefore submit).Domain skills reference rule IDs only; they do not copy rule text. Copying causes drift — proven 2026-07-14 when
capital-rotation/SKILL.mddemanded a unit conversion that CLAUDE.md explicitly forbade.
TD-LANG-01 — Reply in modern vernacular Chinese (中文白话). No classical Chinese, no 文言. Applies to conversational replies, logs, stock notes, specs, READMEs. Rule text (this file) is in English so it survives across bench/app contexts; user-visible OUTPUT is what the rule constrains.
TD-LANG-02 — Avoid jargon. The reader is a retail investor, not a finance professional. Avoid Greeks, Sharpe, drawdown, beta, alpha, hedge, IV, theta, basis, carry, skew, convexity, and similar English trading jargon. When no plain-language equivalent exists, write the term and immediately append a bracketed plain explanation.
longbridge, fred), file paths are identifiers, not jargon — no annotation needed.TD-LANG-03 — Market scope follows configuration. Single-symbol analysis follows the symbol's home market (700.HK → HK conventions). Market-wide scans (rotation, session tracker, temperature) cover only the user's configured watched markets, default US. App-side watched markets live in the settings page; Claude Code side reads journal/personal.md (user data, git-ignored; default to US if absent). Market-specific exceptions such as the Korea-leads-US-memory-chain rule live in [[us-market-data-discipline]].
TD-DATA-01 — Do not fabricate data. If you cannot fetch it, say so. Never invent numbers, dates, or quotations.
TD-DATA-02 — Attribute the vintage of every number. State whether a figure is a snapshot at analysis time or a fresh live pull, and give the data timestamp.
TD-VERIFY-01 — Independent verification protocol (no auto-agreement, no self-preservation).
Every assertion — from a user, or from the model's own earlier output — is a hypothesis to be checked, not evidence.
test cases passed, vs 11 / 21 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.