メニュー
SkillsMP は XyraSinclair/ideonomy から 14 件の skill を収集しています。skill を開くとソースと詳細を確認できます。
収集済み skill 14 件中 14 件を表示しています。
The dangerous case is not "no oracle" — it is a WEAK oracle you falsely believe is exact. Before trusting any test suite, metric, benchmark, eval, or proof as if it settled the question, state explicitly what it CERTIFIES and what it does NOT — the gap…
原文の言語: 英語
Stop re-deriving from zero every session. At the close of any non-trivial work session, extract what RESISTED resolution — anomalies, reframes that failed, objections that survived, named-but-unfilled gaps, contested judgments, the unexplained core of a…
原文の言語: 英語
When the same awkward phrase keeps recurring — "the kind of bug where...", "this class of lines that...", "that pattern we keep tripping on but have no name for" — treat the repetition as residue signaling a missing concept. Coin a precise noun, give it a…
原文の言語: 英語
When the task is to set rules, incentives, or metrics — "how should we score this", "what policy makes agents tell the truth", "how do we reward the right behavior" — do not propose a rule and hope it induces the outcome. Start from the behavior you want as a…
原文の言語: 英語
When one narrative starts dominating early — a bug explanation, a market story, a user motive, "the obvious cause" — stop converging and force at least four live alternatives, each still consistent with what has been seen and each carrying a prediction that…
原文の言語: 英語
When a global attack stalls — the system is too coupled, the proof too wide, the rollout too distributed, the synthesis too brittle — stop pretending the whole thing must yield in one piece. Solve it on tractable patches, then compute exactly what fails on…
原文の言語: 英語
The universal pre-gate that wraps every other skill. Every cognitive move TRANSFORMS the problem — tests it, reframes it, localizes it, names it, formalizes it, dimensionalizes it, persists it — and the sharpest failure is not that the move is non-executable,…
原文の言語: 英語
Whenever you are tempted to say "done", "complete", "fully reviewed", "all sources covered", or "the migration is comprehensive", force the denominator into the open first. State the full space of cases, sources, branches, or entities under discussion, then…
原文の言語: 英語
When a problem is grinding — casework piling up, effort scaling without progress, "it depends on everything" — stop answering at the level it was posed and change the representation until it becomes mechanical or disappears. Raise the abstraction (the general…
原文の言語: 英語
When an answer arrives suspiciously clean — especially on a high-stakes claim, a safety judgment, or anything your own confidence is trying to launder into truth — strip authorship and confidence, pay an adversary to destroy it, and require the attacks to…
原文の言語: 英語
Stay rigorous on questions that have NO computable oracle — taste, register, ethics, strategy, "is this good / right / worth it". Use when you catch yourself about to score an irreducibly normative or aesthetic thing with a single made-up number (7/10, "high…
原文の言語: 英語
When a general claim arrives too easily — a formula, an invariant, "this mechanism works", "the query logic is correct" — force it down to the smallest concrete instance that still exercises the core mechanism and compute it by hand before you generalize. The…
原文の言語: 英語
Before answering substantively, diagnose the problem's shape and dispatch to the right premier skill instead of defaulting to fluent prose. Use when the next move is unclear, when several skills plausibly apply, or whenever the first draft of the response…
原文の言語: 英語
Defeat answer-then-rationalize: when a claim is checkable more cheaply than it is producible (a row count, a benchmark number, "this refactor preserves behavior", a combinatorial count, "this query returns X"), write the independent truth-check AND commit its…
原文の言語: 英語