boundary-bbcr-fallback
Execute automatic BBCR (Collapse-Rebirth Correction) when knowledge boundaries are exceeded or reasoning fails.
Create systematic digital twins with data quality validation and real-world calibration loops.
$ npx -y skills add qdhenry/Claude-Command-Suite --agent claude-codeHow it fires
How this command gets triggered: by you, by Claude, or both.
/digital-twin-creatorContext preview
What this command does when you run it.
Create systematic digital twins with data quality validation and real-world calibration loops.
Create systematic digital twins with data quality validation and real-world calibration loops.
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**
**Critical Information Validation:**
**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"
**Map the structure and boundaries of your target system:**
**Quality Gate**: Validate that your system definition is:
**Evaluate and improve data quality systematically:**
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]
**Build the digital twin using systematic modeling approaches:**
**Ensure model accuracy through systematic testing:**
A comprehensive development toolkit designed following Anthropic's Claude Code Best Practices for AI-assisted software development.
Repo: qdhenry/Claude-Command-Suite
Execute automatic BBCR (Collapse-Rebirth Correction) when knowledge boundaries are exceeded or reasoning fails.
Analyze semantic position relative to knowledge boundaries to prevent hallucination and identify uncertainty zones.
Generate a visual heatmap of knowledge boundaries showing safe zones, risk areas, and semantic coverage.
Evaluate the current risk level and provide detailed analysis of potential hallucination or reasoning failure.
Find and construct semantic bridges to safely navigate from current position to target concept without crossing dangerous boundaries.
Takes an input prompt and returns ONLY a token-optimized version that preserves meaning while minimizing token count. Based on LLM tokenization principles:…