Skip to content
Development
Command

/digital-twin-creator

Create systematic digital twins with data quality validation and real-world calibration loops.

From plugin
claude-command-suite
1.3k199 skills89 agents199 commands
Install
$ npx -y skills add qdhenry/Claude-Command-Suite --agent claude-code

How it fires

How this command gets triggered: by you, by Claude, or both.

  • Fires itselfClaude auto-loads it when your prompt matches the work.
  • You can call itInvoke it directly when you want it.
  • Slash command/digital-twin-creator

Context preview

What this command does when you run it.

Create systematic digital twins with data quality validation and real-world calibration loops.

Command definition

digital-twin-creator.md

Digital Twin Creator

Create systematic digital twins with data quality validation and real-world calibration loops.

Instructions

You are tasked with creating a comprehensive digital twin to simulate real-world systems, processes, or entities. Follow this systematic approach to build an accurate, calibrated model: **$ARGUMENTS**

1. Prerequisites Assessment

**Critical Information Validation:**

  • **Twin Subject**: What specific system/process/entity are you modeling?
  • **Purpose & Decisions**: What decisions will this twin inform?
  • **Fidelity Level**: How accurate does the simulation need to be?
  • **Data Availability**: What real-world data can calibrate the model?
  • **Update Frequency**: How often will the twin sync with reality?

**If any prerequisites are missing, guide the user:**

Missing Twin Subject:
"I need clarity on what you're modeling. Are you creating a digital twin for:
- Physical systems: Manufacturing line, vehicle performance, building operations
- Business processes: Sales pipeline, customer journey, supply chain
- Market dynamics: Customer segments, competitive landscape, demand patterns
- Technical systems: Software performance, network behavior, user interactions"

Missing Purpose Clarity:
"What specific decisions will this digital twin help you make?
- Optimization: Finding better configurations or strategies
- Prediction: Forecasting future outcomes or behaviors  
- Risk Assessment: Understanding failure modes and vulnerabilities
- Experimentation: Testing changes before real-world implementation
- Monitoring: Detecting anomalies or performance degradation"

Missing Fidelity Requirements:
"How precise does your digital twin need to be?
- High Fidelity (90%+ accuracy): Critical safety/financial decisions
- Medium Fidelity (70-90% accuracy): Strategic planning and optimization
- Low Fidelity (50-70% accuracy): Conceptual understanding and exploration"

2. System Architecture Definition

**Map the structure and boundaries of your target system:**

System Components

  • Core elements and their relationships
  • Input/output interfaces and data flows
  • Control mechanisms and feedback loops
  • Performance metrics and success indicators
  • Failure modes and edge cases

Boundary Definition

  • What's included vs. excluded from the model
  • External dependencies and influences
  • Environmental constraints and variables
  • Time horizons and operational contexts
  • Abstraction levels and detail granularity

Relationship Mapping

  • Causal relationships between components
  • Correlation patterns and dependencies
  • Feedback loops and system dynamics
  • Emergent behaviors and non-linear effects
  • Lag times and temporal relationships

**Quality Gate**: Validate that your system definition is:

  • Complete enough for the intended purpose
  • Bounded to avoid unnecessary complexity
  • Focused on factors that impact key decisions
  • Grounded in observable reality

3. Data Foundation Assessment

**Evaluate and improve data quality systematically:**

Data Inventory

  • Historical performance data and patterns
  • Real-time sensor/monitoring data streams
  • Configuration settings and parameters
  • External data sources and market conditions
  • Expert knowledge and domain insights

Data Quality Analysis

For each data source, assess:
- Completeness: What percentage of required data is available?
- Accuracy: How reliable and error-free is the data?
- Timeliness: How current and frequently updated is the data?
- Consistency: Are there conflicts between data sources?
- Relevance: How directly does this data impact key decisions?

Quality Scoring (1-10 for each dimension):
Data Source: [name]
- Completeness: [score] - [explanation]
- Accuracy: [score] - [explanation]  
- Timeliness: [score] - [explanation]
- Consistency: [score] - [explanation]
- Relevance: [score] - [explanation]
Overall Quality Score: [average]

Data Gap Analysis

  • Critical missing information for model accuracy
  • Alternative data sources or proxies available
  • Data collection strategies for key gaps
  • Acceptable uncertainty levels for decisions

4. Model Construction Framework

**Build the digital twin using systematic modeling approaches:**

Component Modeling

  • Individual element behavior patterns
  • Performance characteristics and ranges
  • Response functions to different inputs
  • Degradation patterns and lifecycle factors
  • Optimization parameters and constraints

System Interaction Modeling

  • Interface behaviors between components
  • Network effects and cascade influences
  • Resource sharing and competition dynamics
  • Communication protocols and latencies
  • Synchronization and coordination mechanisms

Environmental Modeling

  • External factors affecting system performance
  • Market conditions and competitive dynamics
  • Regulatory constraints and compliance requirements
  • Economic factors and cost structures
  • Seasonal patterns and cyclical behaviors

Dynamic Behavior Modeling

  • State transitions and evolutionary patterns
  • Learning and adaptation mechanisms
  • Scaling behaviors and capacity constraints
  • Stability and resilience characteristics
  • Performance under stress conditions

5. Calibration and Validation

**Ensure model accuracy through systematic testing:**

Historical Validation

  • Back-test model predictions against known outcomes
  • Identify systematic biases and correction factors
  • Validate model accuracy across different conditions
  • Test edge cases and extreme scenarios
  • Measure prediction error distributions

Real-Time Calibration

  • Compare model outputs to live system data
  • Implement automated calibration adjustments
  • Monitor prediction accuracy over time
  • Detect model drift and degradation
  • Update parameters based on new observations

Sensitivity Analysis

  • Test model response to parameter variations
  • Identify critical assumptions and dependencies
  • Understand uncertainty propagation through model
  • Validate robustness to
Read more
Ships withclaude-command-suite

A comprehensive development toolkit designed following Anthropic's Claude Code Best Practices for AI-assisted software development.

Get the whole plugin