Now liveThe Skillselion MCP - thousands of ranked skills, loaded into your agent mid-task. No install.Get it →
lyndonkl avatar

Design Of Experiments

  • 124 installs
  • 138 repo stars
  • Updated August 4, 2026
  • lyndonkl/claude

design-of-experiments is a Claude agent skill that generates factorial, response-surface, and Taguchi experimental designs for developers who must optimize multi-factor systems within a limited run budget.

About

design-of-experiments is a Claude agent skill from lyndonkl/claude that helps developers plan statistically rigorous experiments when optimizing systems with multiple controllable factors under run-budget constraints. The six-step workflow defines objectives and constraints, lists factors levels and responses, selects a design type, plans randomization and replication, writes design-of-experiments.md with the run matrix, and validates against rubric_design_of_experiments.json at a minimum average score of 3.5. It covers five common patterns: screening 10–30 factors via Plackett-Burman or fractional factorial, optimizing 2–5 factors, mapping response surfaces with central composite or Box–Behnken designs, Taguchi robust designs against noise factors, and sequential screening-to-confirmation flows. Guardrails require randomized run order, replicated center points, Resolution IV or higher when interactions matter, correlation below 0.3, and power analysis targeting beta at most 0.20. Reach for design-of-experiments when tuning software performance parameters, running A/B/n experiments, or replacing one-factor-at-a-time tuning that misses interactions.

  • Six-step workflow ending in design-of-experiments.md validated by JSON rubric (≥ 3.5)
  • Five patterns: screening, optimization, response surface, Taguchi robust, sequential
  • Screening designs handle 10–30 factors via Plackett-Burman or fractional factorial
  • Guardrails: randomize runs, replicate center points, Resolution IV+, beta ≤ 0.20
  • Typical planning time 15–90 minutes depending on design complexity

Design Of Experiments by the numbers

  • 124 all-time installs (skills.sh)
  • +7 installs in the week ending Aug 2, 2026 (Skillselion tracking)
  • Ranked #764 of 2,064 Data Science & ML skills by installs in the Skillselion catalog
  • Data as of Aug 4, 2026 (Skillselion catalog sync)
npx skills add https://github.com/lyndonkl/claude --skill design-of-experiments

Add your badge

Show developers this skill is listed on Skillselion. Paste this into your README.

Listed on Skillselion
Installs124
repo stars138
Last updatedAugust 4, 2026
Repositorylyndonkl/claude

How do you plan factorial experiments with limited runs?

Generate a design-of-experiments.md run matrix with factorial or Taguchi layouts, randomization plan, and analysis protocol for multi-parameter performance tuning.

Who is it for?

Developers or data engineers optimizing multi-parameter systems—ML training configs, manufacturing processes, or A/B/n tests—who need fewer runs than one-factor-at-a-time tuning.

Skip if: Teams with unlimited trial budget, purely qualitative research, or single-knob adjustments where interactions and curvature do not matter.

When should I use this skill?

User mentions factorial design, A/B/n testing, parameter tuning, Taguchi methods, response surface mapping, or process optimization with multiple factors.

What you get

design-of-experiments.md with factor table, design matrix, randomization protocol, and planned statistical analysis.

  • design-of-experiments.md

By the numbers

  • Six-step experimental design workflow with five documented common patterns
  • Screening pattern targets 10–30 candidate factors to identify 3–5 critical ones
  • Quality rubric requires minimum average score ≥ 3.5; power analysis targets beta ≤ 0.20

Files

SKILL.mdMarkdownGitHub ↗

Design of Experiments

Table of Contents

Workflow

Copy this checklist and track your progress:

Design of Experiments Progress:
- [ ] Step 1: Define objectives and constraints
- [ ] Step 2: Identify factors, levels, and responses
- [ ] Step 3: Choose experimental design
- [ ] Step 4: Plan execution details
- [ ] Step 5: Create experiment plan document
- [ ] Step 6: Validate quality

Step 1: Define objectives and constraints

Clarify the experiment goal (screening vs optimization), response metric(s), experimental budget (max runs), time/cost constraints, and success criteria. See Common Patterns for typical objectives.

Step 2: Identify factors, levels, and responses

List all candidate factors (controllable inputs), specify levels for each factor (low/high or discrete values), categorize factors (control vs noise), and define response variables (measurable outputs). For screening many factors (8+), see resources/methodology.md for Plackett-Burman and fractional factorial approaches.

Step 3: Choose experimental design

Based on objective and constraints:

  • For screening 5+ factors with limited runs → Use resources/methodology.md for fractional factorial or Plackett-Burman
  • For optimizing 2-5 factors → Use resources/template.md for full or fractional factorial
  • For response surface mapping → Use resources/methodology.md for central composite or Box-Behnken
  • For robust design against noise → Use resources/methodology.md for parameter vs noise factor arrays

Step 4: Plan execution details

Specify randomization order (eliminate time trends), blocking strategy (control nuisance variables), replication plan (estimate error), sample size justification (power analysis), and measurement protocols. See Guardrails for critical requirements.

Step 5: Create experiment plan document

Create design-of-experiments.md with sections: objective, factors table, design matrix (run order with factor settings), response variables, execution protocol, and analysis plan. Use resources/template.md for structure.

Step 6: Validate quality

Self-assess using resources/evaluators/rubric_design_of_experiments.json. Check: objective clarity, factor completeness, design appropriateness, randomization plan, measurement protocol, statistical power, analysis plan, and deliverable quality. Minimum standard: Average score ≥ 3.5 before delivering.

Common Patterns

Pattern 1: Screening (many factors → vital few)

  • Context: 10-30 candidate factors, limited budget, want to identify 3-5 critical factors
  • Approach: Plackett-Burman or fractional factorial (Resolution III/IV)
  • Output: Pareto chart of effect sizes, shortlist for follow-up optimization
  • Example: Software performance tuning with 15 configuration parameters

Pattern 2: Optimization (find best settings)

  • Context: 2-5 factors already identified as important, want to find optimal levels
  • Approach: Full factorial (2^k) or fractional factorial + steepest ascent
  • Output: Main effects plot, interaction plots, recommended settings
  • Example: Manufacturing process with temperature, pressure, time factors

Pattern 3: Response Surface (map the landscape)

  • Context: Need to understand curvature, find maximum/minimum, quantify tradeoffs
  • Approach: Central Composite Design (CCD) or Box-Behnken
  • Output: Response surface equation, contour plots, optimal region
  • Example: Chemical formulation with ingredient ratios

Pattern 4: Robust Design (work despite noise)

  • Context: Product/process must perform well despite uncontrollable variation
  • Approach: Taguchi inner-outer array (control × noise factors)
  • Output: Settings that minimize sensitivity to noise factors
  • Example: Consumer product that must work across temperature/humidity ranges

Pattern 5: Sequential Experimentation (learn then refine)

  • Context: High uncertainty, want to learn iteratively with minimal waste
  • Approach: Screening → Steepest ascent → Response surface → Confirmation
  • Output: Progressively refined understanding and settings
  • Example: New product development with unknown factor relationships

Guardrails

Design requirements:

1. Randomize run order: Eliminates time-order bias and confounding with lurking variables. Use random number generator, not "convenient" sequences.

2. Replicate center points: For designs with continuous factors, replicate center point runs (3-5 times) to estimate pure error and detect curvature.

3. Preserve critical interactions: In fractional factorials, avoid confounding important 2-way interactions with main effects. Choose Resolution IV or higher if interactions matter.

4. Check design balance: Ensure orthogonality (factors are uncorrelated in design matrix). Correlation > 0.3 reduces precision and interpretability.

5. Define response precisely: Use objective, quantitative, repeatable measurements. Avoid subjective scoring unless calibrated with multiple raters.

6. Justify sample size: Run power analysis to ensure design can detect meaningful effect sizes with acceptable Type II error risk (beta at most 0.20).

7. Document assumptions: State expected effect magnitudes, interaction assumptions, noise variance estimates. Design validity depends on these.

8. Plan for analysis before running: Specify statistical tests, significance level (alpha), effect size metrics before data collection to prevent p-hacking.

Common pitfalls:

  • One-factor-at-a-time (OFAT): Misses interactions, requires more runs than factorial designs
  • Ignoring blocking: If runs span days/batches/operators, block accordingly or confound results with time trends
  • Too many levels: Use 2-3 levels initially. More levels increase runs exponentially.
  • Unmeasured factors: If an important factor isn't controlled/measured, it becomes noise
  • Changing protocols mid-experiment: Breaks design structure. If necessary, restart or analyze separately.

Quick Reference

Key resources:

  • [resources/template.md](resources/template.md): Quick-start templates for common designs (factorial, screening, response surface)
  • [resources/methodology.md](resources/methodology.md): Advanced techniques (optimal designs, Taguchi, mixture experiments, sequential strategies)
  • [resources/evaluators/rubric_design_of_experiments.json](resources/evaluators/rubric_design_of_experiments.json): Quality criteria for experiment plans

Typical workflow time:

  • Simple factorial (2-4 factors): 15-30 minutes
  • Screening design (8+ factors): 30-45 minutes
  • Response surface design: 45-60 minutes
  • Robust design (Taguchi): 60-90 minutes

When to escalate:

  • User needs mixture experiments (factors must sum to 100%)
  • Split-plot designs required (hard-to-change factors)
  • Optimal designs for irregular constraints
  • Bayesian adaptive designs

→ Use resources/methodology.md for these advanced cases

Inputs required:

  • Process/System: What you're experimenting on
  • Factors: List of controllable inputs with candidate levels
  • Responses: Measurable outputs (KPIs, metrics)
  • Constraints: Budget (max runs), time, resources
  • Objective: Screening, optimization, response surface, or robust design

Outputs produced:

  • design-of-experiments.md: Complete experiment plan with design matrix, randomization, protocols, analysis approach

Related skills

How it compares

Use design-of-experiments for multi-factor statistical run planning; use decision-matrix when choosing between discrete named alternatives without running experiments.

FAQ

What designs does design-of-experiments support?

design-of-experiments supports full and fractional factorial designs, Plackett-Burman screening for 8+ factors, central composite and Box–Behnken response surfaces, Taguchi inner-outer arrays, and sequential screening-to-confirmation workflows.

What deliverable does design-of-experiments produce?

design-of-experiments outputs a design-of-experiments.md plan containing objectives, a factors table, the design matrix with run order, response variables, execution protocol, and a pre-planned statistical analysis approach.

Why avoid one-factor-at-a-time tuning?

design-of-experiments explicitly warns that one-factor-at-a-time (OFAT) approaches miss interaction effects and typically require more runs than factorial designs covering factor combinations systematically.

Data Science & MLanalyticspipelines

This week in AI coding

Five minutes, every Monday - the tools, releases and tactics for developers.

unsubscribe anytime.