Raising Resolution

Original name

Original description

Raise the RESOLUTION (解像度) of your understanding of THIS code/data/API/source/problem BEFORE you assert or act, by INSPECTING primary information instead of guessing — an operational procedure distilled from 馬田隆明『解像度を上げる』. Load-bearing CITATION GATE: before a factual claim about local code/data/an API/a source, ask — can you cite a line you Read, a command you ran, or a source you fetched that grounds THIS exact claim? NO → stop and inspect; YES → assert and act. This skill is LOWEST precedence and yields to any domain owner: multi-paper / corpus synthesis → systematizing-knowledge / sok, OSS adoption → growing-oss-adoption, .claude / CLAUDE.md / hooks / SKILL.md authoring or auditing → operating-the-harness, Julia / Lean execution → writing-julia / proving-theorems, a future-bet (MVP / prototype / spike / 賭け / kill-condition / will-it-scale) → acting-on-hypotheses. If any owner applies, this skill does NOT fire (it is at most a silent sub-step). It FIRES only when ALL hold AND no owner applies: (a) you are about to SPECULATE INSTEAD OF inspect a fact about THIS local artifact, (b) nothing yet grounds it, (c) the un-grounded claim is BLOCKING a concrete next action AND inspecting is non-trivial. It does NOT fire as a reminder to read files during ordinary edit/debug where inspecting is already the obvious next step — not "read before asserting" (baseline) but "you are about to speculate INSTEAD of inspecting." Two routing cuts decide overlap. DECISIVE CUT vs acting-on-hypotheses (agrees in substance with acting-on-hypotheses STEP 0 — same smart-person test, same YES/NO routing): "Could a smart person, given enough primary info about what ALREADY EXISTS, know the answer? YES → raising-resolution; NO (needs a forward TEST reality has not decided) → acting-on-hypotheses." CARDINALITY CUT vs systematizing-knowledge: "single local artifact → here; a CORPUS of papers/sources synthesized into a position → systematizing-knowledge." Trigger on the speculation language the model actually emits: probably / likely / usually / typically / I think / should be / in my experience / this kind of library / たぶん / おそらく / 一般的に / はず, plus 推測するな / ちゃんと調べて / inspect / guessing / speculating / 一次情報 / primary information / 解像度 / resolution / 解像度を上げる. Concept-token tail (mnemonic): 深さ・広さ・構造・時間, 症状 vs 病因, なぜなぜ / Why so, 課題 vs 解決策. If a vagueness symptom is needed it must bind to a code object (不明なバグ挙動 / 仕様が未確認), never bare 曖昧 / vague. This skill is English; respond to the user in their language (Japanese by default).