320건 · 관련도순
This skill should be used when the user wants to "investigate a bug", "debug an issue", "figure out why something is happening", "find the root cause", "troubleshoot", "強い推論で調査", "仮説を立てて検証", "原因を特定", "バグの原因調査", "なぜ動かないか調べて", "問題を切り分け", "原因不明", "デバッグ", or mentions systematic hypothesis-driven debugging. NOTE: Use this for investigating UNKNOWN causes, not for validating design proposals (use devils-advocate for that).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Runs the test-first build loop (spec, plan, thin slices, failing test first, verify, commit) for a Godot 4 game in GDScript or C# first; in a TypeScript, Python or other repo when test-first, slices or a reproduce-first fix is asked for. Trigger to build or add a game feature, mechanic, stat, system or milestone, even when told to test later; to turn a spec or grill record into slices; to fix a game bug from a reproduction, one hypothesis at a time; on "write the test first", "what's the next slice", "is this slice done" or "is this milestone ready to exit"; or say slicesmith (spec, plan, slice, fix, exit). Run proof and gate rulings are godotsmith's; diff review a review tool's; repo maps researchscribe's; art pixelsmith's; audio soundsmith's; interviews grillwright's; fan-out dispatchwright's.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Hypothesis-Test Loops via REPL for Exploratory Abductive Inference with Gay.jl colors
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Structured guide for setting up A/B tests with mandatory gates for hypothesis, metrics, and execution readiness.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Structured guide for setting up A/B tests with mandatory gates for hypothesis, metrics, and execution readiness.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Statistical analysis toolkit. Hypothesis tests (t-test, ANOVA, chi-square), regression, correlation, Bayesian stats, power analysis, assumption checks, APA reporting, for academic research.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Atom of Thoughts (AoT) reasoning - decompose complex problems into atomic units with confidence tracking and backtracking. For genuinely complex reasoning, not everyday questions. Triggers on: atomise, complex reasoning, decompose problem, structured thinking, verify hypothesis.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
When the user wants to plan, design, or implement an A/B test or experiment. Also use when the user mentions "A/B test," "split test," "experiment," "test this change," "variant copy," "multivariate test," or "hypothesis." For tracking implementation, see analytics-tracking.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.