'hypothesis' 검색 결과

Systematic debugging methodology - scientific method, hypothesis testing, and root cause analysis that works across all technologiesUse when "bug, debugging, not working, broken, investigate, root cause, why is this happening, figure out, troubleshoot, doesn't work, unexpected behavior, debugging, root-cause, hypothesis, scientific-method, troubleshooting, bug-hunting, investigation, problem-solving" mentioned.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

The science of learning through controlled experimentation. A/B testing isn't about picking winners—it's about building a culture of validated learning and reducing the cost of being wrong. This skill covers experiment design, statistical rigor, feature flagging, analysis, and building experimentation into product development. The best experimenters know that every test, positive or negative, teaches something valuable. Use when "a/b test, experiment, hypothesis, statistical significance, sample size, feature flag, variant, control, treatment, p-value, conversion rate, test winner, split test, experimentation, testing, statistics, feature-flags, hypothesis, growth, optimization, learning, validation" mentioned.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Designing A/B tests: hypothesis docs, sample size, feature flags, significance analysis, CUPED, SRM detection, switchback experiments. Use when hypothesis validation is needed.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Expert guide for property-based testing (fast-check, Hypothesis) and mutation testing (Stryker, mutmut) — AI-generated test properties, invariant discovery, mutation score optimization, and test suite quality verification / Panduan ahli property-based testing (fast-check, Hypothesis) dan mutation testing (Stryker, mutmut) — properti tes yang dihasilkan AI, penemuan invarian, optimasi skor mutasi, dan verifikasi kualitas suite tes.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Formal oracle for abductive inference that selects the minimal hypothesis best explaining a set of observations. Provides three sub-oracles: MCMC via monad-bayes, Gemini for natural language, and propagator networks for constraint domains. Use when performing hypothesis selection, explaining observations, or solving inference-to-best-explanation problems.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Turns a theory into falsifiable, pre-registerable hypotheses: DGP and DAG, identification, estimands, SESOIs, test choice among NHST, equivalence, and minimum-effect tests, scope conditions, and hypothesis tiers. Use when converting a research question into testable predictions or predicting a null.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use when facing unknowns, debugging without a clear cause, or making architecture decisions — enforces hypothesis-driven scientific reasoning through observation, hypothesis formulation, prediction, experiment design, and evidence-based conclusion. Use when previous attempts have failed or the problem space involves uncertainty.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Construct well-structured arguments using the hypothesis-argument-example triad. Covers formulating falsifiable hypotheses, building logical arguments (deductive, inductive, analogical, evidential), providing concrete examples, and steelmanning counterarguments. Use when writing or reviewing PR descriptions that propose technical changes, justifying design decisions in ADRs, constructing substantive code review feedback, or building a research argument or technical proposal.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Scaffold and run Karpathy-style autoresearch loops in any git repo. This skill should be used when setting up autonomous code improvement, generating adversarial eval harnesses, running hypothesis-implement-eval-keep/discard loops, or checking autoresearch progress. Triggers on "autoresearch", "autonomous improvement", "eval loop", "hypothesis loop", "self-improvement loop".

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Hard-gated ideation for an Arbor research run. Load at the START of every IDEATE round, before drafting any hypothesis. Enforces the PI mindset (mechanism over knob), the four-question first-principles probe, the kill-filter, and the four-line hypothesis format. Ported from Arbor's idea_drafting + first_principles_probe.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Design a research study. Use when the user says "study design", "design my research", "what research method should I use", "how do I test this hypothesis", "research plan", "methodology section", "experimental design", "survey design", "qualitative study design", "how to structure my study", "sample size", "data collection plan", or needs to plan how to test a research question or hypothesis - even if they don't explicitly say "study design".

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Autonomously improve a real artifact (code, training recipe, agent harness, data pipeline, prompt) against an objective and an evaluator, using Hypothesis Tree Refinement (HTR) from the Arbor paper. Use this whenever someone wants to iteratively optimize something over many experiments without overfitting — e.g. "get my model's eval score up", "improve this agent/harness", "tune this pipeline", "beat the baseline on this benchmark", "run a search over approaches and keep the best", "do an MLE-bench / Kaggle-style optimization", or any long-horizon "make this artifact better and don't just memorize the dev set" task. Trigger it even when the user doesn't say "Arbor" or "hypothesis tree" but describes repeated experiment-and-evaluate loops, branching exploration of competing ideas, or worries about a dev/test gap. Runs Claude itself as the coordinator with subagent executors in isolated git worktrees; for the standalone `arbor` CLI tool see references/arbor-upstream.md.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Expert-level statistics knowledge. Use when working with probability distributions, hypothesis testing, regression, Bayesian statistics, statistical inference, experimental design, ANOVA, or statistical modeling. Also use when the user mentions 'p-value', 'confidence interval', 'hypothesis test', 'regression', 'ANOVA', 'chi-square', 't-test', 'Bayesian', 'maximum likelihood', 'statistical significance', 'correlation', 'normal distribution', or 'sampling distribution'.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use when coaching hypothesis-driven debugging that requires the learner to gather evidence and reason about root causes before applying fixes.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Turn any hypothesis, however fringe, into an argument map rather than a verdict: five independent lenses (consensus, skeptic, frontier, historian, experimental design), then a synthesis of for and against, evidence quality, a confidence tier and the cheapest decisive experiment. Triggers: "/research-swarm <hypothesis>", "map the arguments on X".

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Repository または subsystem を対象に、source-only で明示的なセキュリティ監査を行う entry skill。 通常の PR セキュリティレビューとは分離し、reconnaissance、scope 固定、既存 security skill への委譲、 evidence と unresolved hypothesis、observe-only SecurityAuditCoverage、coverage critic、 structured audit artifact と repeat-run coverage を扱う。target-controlled code は実行しない。

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Autonomously improve a real artifact (code, training recipe, agent harness, data pipeline, prompt) against an objective and an evaluator, using Hypothesis Tree Refinement (HTR) from the Arbor paper. Use this whenever someone wants to iteratively optimize something over many experiments without overfitting — e.g. "get my model's eval score up", "improve this agent/harness", "tune this pipeline", "beat the baseline on this benchmark", "run a search over approaches and keep the best", "do an MLE-bench / Kaggle-style optimization", or any long-horizon "make this artifact better and don't just memorize the dev set" task. Trigger it even when the user doesn't say "Arbor" or "hypothesis tree" but describes repeated experiment-and-evaluate loops, branching exploration of competing ideas, or worries about a dev/test gap. Runs Claude itself as the coordinator with subagent executors in isolated git worktrees; for the standalone `arbor` CLI tool see references/arbor-upstream.md.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

A/B testing specialist v3 — hypothesis, sample size, statistical significance, Bayesian

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Write a rigorous, decision-grade experiment spec — falsifiable hypothesis, primary metric, guardrails, randomisation unit, exposure definition, method (A/B, holdout, switchback, quasi-experiment, MAB), MDE/duration plan, peek policy, validity threats, and pre-committed decision rule. Platform-agnostic. Load when the user has a candidate experiment and needs to spec it before launch, or says "spec this experiment", "write the test plan", "design this A/B test", "what's the hypothesis", "how big a sample do we need", "how long should we run this", "define the metrics for this test", or when the experimentation orchestrator routes here.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

This skill should be used when the user wants to "test a claim against data", "validate an empirical hypothesis", "refine a model/theory with evidence", "characterize a pattern and verify it", "演繹と帰納で検証", "仮説をデータで検証して更新", "実例と反例で確かめる", "弁証法ループ", "主張を現物で裏取り", "傾向分析を検証して精緻化", or mentions iteratively updating a hypothesis by deriving predictions and testing them against a real corpus. NOTE: Use this for VALIDATING/REFINING an empirical claim or model against real data through a derive→test→update loop. Use strong-inference for debugging an UNKNOWN cause, and devils-advocate for adversarially stress-testing a DESIGN proposal.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

The science of learning through controlled experimentation. A/B testing isn't about picking winners—it's about building a culture of validated learning and reducing the cost of being wrong. This skill covers experiment design, statistical rigor, feature flagging, analysis, and building experimentation into product development. The best experimenters know that every test, positive or negative, teaches something valuable. Use when "a/b test, experiment, hypothesis, statistical significance, sample size, feature flag, variant, control, treatment, p-value, conversion rate, test winner, split test, experimentation, testing, statistics, feature-flags, hypothesis, growth, optimization, learning, validation" mentioned.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

현재 성능 측정, 가설별 변경안 비교, 정확성 검증으로 최적화를 진행합니다. 시간과 비용 한도 안에서 가장 빠르고 안전한 안을 고르고 재실행 절차를 남깁니다.

• 느린 작업을 측정하며 속도 개선
• 같은 입력 조건에서 구현안 비교
• 응답 시간, 처리량, 실행 비용 평가

증상을 재현하는 테스트나 명령을 준비하고 원인 조사, 정상 사례 비교, 가설 검증, 수정의 네 단계를 진행합니다. 근본 원인을 찾고 회귀 테스트로 결과를 확인합니다.

• 테스트나 빌드 실패 조사
• 여러 시스템에 걸친 이상 추적
• 간헐적인 버그 재현

오류와 예상 밖의 동작을 조사, 분석, 가설, 구현 순서로 추적합니다. 근본 원인을 확인한 뒤 수정하며, 보고서에서 증거의 종류와 미확인 사항을 구분합니다.

• 서버 오류의 원인을 조사할 때
• 스택 추적으로 원인을 찾을 때
• 정상 작동하던 기능이 멈춘 이유를 조사할 때