From ai4ss-skills
Builds executable study designs for quantitative political science. Guides translation of research problems into descriptive, associational, predictive, or causal designs with population, measures, and identification strategy.
How this skill is triggered — by the user, by Claude, or both
Slash command
/ai4ss-skills:study-design-builderThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Turn a political-science question and theoretical argument into an executable empirical design. The
Turn a political-science question and theoretical argument into an executable empirical design. The design should specify what will be learned, from which population and comparison, with which measures, and under which assumptions. Contemporary causal inference is appropriate when the question and evidence support it; many important studies remain descriptive, associational, predictive, or measurement-oriented.
Set out the proposed study in a Research Design Memo or Pre-Analysis Memo that specifies:
Read the concept memo, literature, institutional material, data descriptions, and prior analysis. Clarify what the study wants to learn before discussing estimators. If the proposed outcome or treatment does not match the theoretical construct, repair the question or measurement first.
Decide whether the study's actual contribution is descriptive, associational, predictive, measurement-oriented, or causal. Do not force every worthwhile political-science study into a causal design. When the question is causal, define the relevant potential-outcome estimand and comparison; a DAG is not required.
Describe how cases enter the sample, how exposure occurs, how outcomes are observed, and which political processes could confound, mediate, anticipate, or spill over. Use institutional knowledge to judge the comparison rather than choosing a design from its label.
Connect each construct to observable indicators. Examine content, construct, convergent, discriminant, and predictive validity as appropriate. Discuss coding decisions, aggregation, measurement error, differential reporting, and whether the measure behaves differently across groups or time.
Choose analyses that answer the stated target. Begin with sample and measurement descriptions, raw patterns, and design diagnostics. Then specify estimation, uncertainty, heterogeneity, mechanisms, and falsification or sensitivity checks. Separate prespecified tests from exploratory learning.
When a design family has substantial specialist knowledge, such as DID, state which design-specific assumptions, comparisons, diagnostics, and sensitivity questions require deeper treatment instead of compressing those questions into a general design memo.
For most observational research, judge feasibility from data coverage, relevant variation, measurement quality, comparison support, timing, dependence, attrition, plausible precision, and the number of informative cases or clusters. Formal power calculations or simulations are optional and should be used only when their assumptions and design make them defensible.
Identify the assumptions and threats most likely to change the answer. Redesign the sample, measurement, comparison, outcome, time window, or claim when the evidence cannot sustain the initial plan. State the chosen design and rejected alternatives with reasons.
Sources on research practice:
A defensible design:
npx claudepluginhub siyaozheng/ai4ss-skills --plugin ai4ss-skillsDefends research design for APSR manuscripts: causal identification, case selection, process tracing, experimental design, and formal-empirical linkage.
Matches research questions to appropriate designs, sampling strategies, and validity controls, and reframes stuck problems with cross-domain analogies and first-principles deconstruction.
Defends the research design of a World Politics manuscript across comparative-historical, quantitative, qualitative, experimental, and formal-empirical methods. Strengthens argumentation without writing code.