ic-explain

majiayu000's avatarfrom majiayu000

Explain IC10 code behavior in plain English. Use when user pastes IC10 code and asks what it does, how it works, or wants to understand existing Stationeers scripts.

⭐0stars🔀0forks📁View on GitHub🕐Updated Jan 5, 2026
[Tutoring and Explanations]

When & Why to Use This Skill

The ic-explain Claude skill is a specialized tool designed to translate complex IC10 scripts from the game Stationeers into clear, plain English. By analyzing code structure and execution flow, it provides users with a comprehensive breakdown of script logic, device requirements, and operational thresholds, making technical automation accessible to all players.

Use Cases

  • Understanding Community Scripts: Paste complex IC10 code found on workshops or forums to receive a human-readable explanation of how it manages base systems.
  • Learning IC10 Programming: Use the step-by-step logic breakdown as a tutorial to learn how specific commands and logic flows work within the Stationeers environment.
  • Device Configuration Guidance: Automatically identify which devices need to be connected to specific pins and understand their intended roles within a script.
  • Logic Flow Visualization: Walk through the execution path of a script to see exactly how it handles environmental variables like pressure, temperature, and power levels.
nameic-explain
descriptionExplain IC10 code behavior in plain English. Use when user pastes IC10 code and asks what it does, how it works, or wants to understand existing Stationeers scripts.

IC10 Code Explanation

Explain IC10 code behavior in clear, understandable language.

Workflow

  1. Analysis Phase Use Task tool to spawn:

    • code-analyzer - Analyze code structure, execution flow, and behavior

  2. Explanation Phase Take the analysis output and create a human-readable explanation

Instructions

When the user asks to explain IC10 code:

  1. Launch code-analyzer agent with the provided code

  2. From the analysis, create a clear explanation that includes:

    • Overview: 1-2 sentences describing what the code does
    • Device Setup: What devices need to be connected where
    • How It Works: Step-by-step explanation of the logic
    • Key Behaviors: What happens under different conditions

  3. Keep the explanation accessible:

    • Use plain language, not just code terms
    • Relate to real-world behavior (e.g., "when pressure is too high")
    • Highlight important thresholds and values

  4. If issues are found, mention them but don't fix (that's for ic-debug)

Example Triggers

  • "What does this code do?"
  • "Explain this script"
  • "How does this work?"
  • "Can you walk me through this?"
  • "I don't understand this code"