with one click
conjoint-design
Design conjoint experiments: attributes, power, AMCE/AMIE estimation.
Menu
Design conjoint experiments: attributes, power, AMCE/AMIE estimation.
End-to-end data analysis workflow in R or Python — from exploration through regression to publication-ready tables and figures. Make sure to use this skill whenever the user wants to run any empirical analysis, write analysis code, or produce output from data. Triggers include: "analyze this data", "run a regression", "write R code for this", "write Python code for this", "I have a dataset", "help me with this regression", "run a DiD", "run an RDD", "event study", "IV regression", "fit a model", "produce a table", "make a figure", "explore my data", or any request involving a dataset path or empirical estimation.
Find and assess datasets for a research question. Dispatches Explorer agents to search across data source categories, then Explorer-Critic to stress-test each candidate. Produces a ranked list with feasibility grades. Make sure to use this skill whenever the user wants to identify or evaluate data sources — not to search for papers or run analysis. Triggers include: "find data", "what data should I use", "find a dataset for this", "where can I get data on X", "assess datasets", "what datasets exist for", "help me find data", "is there data on this", "what are my data options", "I need data for this project", or any request to locate empirical data sources for a research question.
Deep consistency audit of the entire repository — launches 4 parallel specialist agents to find factual errors, code bugs, broken references, count mismatches, and cross-document inconsistencies, then fixes all issues and loops until clean. Make sure to use this skill whenever the user wants a comprehensive repository-wide check — not a targeted review of a single file. Triggers include: "audit", "deep audit", "find inconsistencies", "check everything", "run a full audit", "are there any broken references", "check the whole repo", "something feels off", "run the audit loop", or after making broad changes across multiple files.
Structured literature review using a parallel fleet of Librarian agents. Searches top journals, working paper repositories (NBER, SSRN, IZA), and traces citation chains from key papers. Make sure to use this skill whenever the user wants to survey existing research on a topic — not to find datasets or write a paper. Triggers include: "review the literature", "find related papers", "what's been done on X", "search for papers on", "do a lit review", "find papers about", "what papers should I cite", "who has written about this", "survey the literature", "find prior work on", or any request to locate and summarize academic publications on a topic.
Start a new research project by conducting a structured interview to formalize a research idea, then generates research questions with identification strategies and a project spec. Make sure to use this skill whenever the user wants to develop or document a new research idea — not to search for literature or data. Triggers include: "new project", "start research", "I have an idea", "help me develop this", "I want to study X", "help me formalize this idea", "what's my research question", "what identification strategy should I use", "write up my project idea", or when the user describes a topic they want to turn into a paper.
Run the proofreading protocol on academic writing — papers or manuscripts. Checks grammar, typos, layout issues, consistency, and academic writing quality. Produces a report without editing files. Make sure to use this skill whenever the user wants surface-level writing errors found — not substantive academic critique. Triggers include: "proofread", "check for typos", "grammar check", "look for errors in my draft", "proofread all", "polish this", "check my writing", "are there any mistakes", "proofread before I send this", or when the user wants a clean-up pass rather than feedback on arguments or methods.
| name | conjoint-design |
| description | Design conjoint experiments: attributes, power, AMCE/AMIE estimation. |
| argument-hint | [describe your design question or paste attribute table] |
Worked example (attribute table → power calculation → PAP tier assignment): see
reference/example.md.
cjpowR R package (Freitag 2021) or the associated Shiny app for simulation-based power analysis. These allow specification of the number of attributes, levels, tasks, and profiles, and return power curves for main effects and interactions. For a general declare-diagnose-redesign workflow that couples the closed-form formula with design-based simulation across estimands, diagnosands, and assignment schemes, use the DeclareDesign framework (Blair, Cooper, Coppock, and Humphreys 2019). For interaction analysis, use FindIt (Egami and Imai 2019). For heterogeneity detection, use cjbart (Robinson and Duch 2024) or the Bayesian mixture-of-regularized-regressions approach in Goplerud, Imai, and Pashley (2025). For lexicographic preference ranking, use cjRank (Dill, Howlett, and Müller-Crepon 2024). For assumption-free tests of whether a factor matters at all, use CRTConjoint (Ham, Imai, and Janson 2024). For deploying an adaptive focal/context design, use the Docker container at github.com/dmolitor/adaptive-infra, with replication scaffolding at github.com/jennahgosciak/adaptive_conjoint (Gosciak, Molitor, and Lundberg 2026); standard survey platforms (Qualtrics) do not support continuous Thompson-sampling updates.hypothesis-building skill.projoint R package. This is a design decision — it cannot be retrofitted after data collection.CRTConjoint (Ham, Imai, and Janson 2024), which provides an assumption-free test of whether a factor of interest matters in any way given the other factors, and tests for profile-order, carryover, and fatigue effects. This is especially valuable when AMCE-based confidence intervals are narrow and contain zero — a narrow AMCE CI implies a weak marginal effect, not necessarily a weak total causal effect.factorEx) rather than the default uniform AMCE. Define the estimand explicitly — unit-specific quantity, target population, and aggregation — before selecting an estimator, per the estimand-first framework of Lundberg, Johnson, and Stewart (2021).FindIt R package (CausalANOVA()), which simultaneously handles the high-dimensionality problem (even a modest conjoint with 5 attributes and 4 levels each generates 100+ interaction parameters) through regularization that shrinks weak interactions toward zero and collapses adjacent levels with similar effects (Egami and Imai 2019). Note: the AMIE framework applies to interactions between randomized conjoint attributes, not to interactions between attributes and non-randomized respondent characteristics (subgroup moderators).cjbart): Robinson and Duch (2024) fit a probit BART model to estimate Individual-level Marginal Component Effects (IMCEs) -- each respondent's predicted effect for each attribute level. The method introduces a three-level estimand hierarchy: OMCE (observation-level) → IMCE (individual-level, averaged across tasks) → AMCE (population-level, averaged across respondents). The IMCE distribution is the primary heterogeneity diagnostic: a tight, normal distribution centered on the AMCE suggests homogeneous effects; multimodal, skewed, or widely dispersed distributions (especially spanning both sides of zero) indicate substantive heterogeneity. Use het_vimp() to identify which respondent covariates most strongly partition the IMCE distribution via random forest variable importance scores.cjRank R package.pre-registration-writing skill for registry selection, locked/conditional/exploratory tier templates, and contingency-tree conventions that complement the conjoint-specific guidance here.methods-reporting skill to audit the 45-item checklist (attribute list, randomization scheme, restrictions, sample flow, estimator, SEs, weights, and replication materials) before submission; the conjoint-specific items in this skill slot into that broader reporting scaffold rather than substituting for it.FindIt::CausalANOVA() with nway=2 (or nway=3) to estimate AMIEs via penalized ANOVA with weighted zero-sum constraints. Use cv.CausalANOVA() to select the regularization cost parameter (1-SE rule). Decompose specific combination effects with AMIE(). Present as AMIE matrices across factor-level combinations (Egami and Imai 2019). Do not use conventional dummy-coded product terms.cjbart::cjbart() to fit a probit BART model, then IMCE() to extract individual-level effects with credible intervals. Report the AMCE alongside the IMCE standard deviation as the primary heterogeneity diagnostic. Use het_vimp() to identify moderator covariates. Works reliably with 500+ respondents (Robinson and Duch 2024). When interpretable respondent clusters and their moderator-driven membership are the primary target, fit the Bayesian mixture-of-regularized-regressions model in Goplerud, Imai, and Pashley (2025) as an alternative or complement.CRTConjoint (Ham, Imai, and Janson 2024). The same package tests profile-order, carryover, and fatigue assumptions that underlie standard AMCE estimation.CRTConjoint (or equivalent) tests of profile-order, carryover, and fatigue assumptions been planned or reported (Ham, Imai, and Janson 2024)?