ic-explain

smileynet's avatarfrom smileynet

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 Dec 25, 2025
[Tutoring and Explanations]

When & Why to Use This Skill

The ic-explain Claude skill simplifies complex IC10 scripts from the game Stationeers into plain, understandable English. It provides a comprehensive breakdown of code logic, device requirements, and execution flows, making it an essential educational tool for players looking to master IC10 programming and automate their bases effectively.

Use Cases

  • Understanding Community Scripts: Paste a complex IC10 script found online to receive a clear explanation of how it manages base systems like power or atmospheres.
  • Learning IC10 Logic: Use the skill as a personal tutor to learn how specific assembly-like commands translate into real-world in-game behaviors.
  • Hardware Configuration Guidance: Identify exactly which devices need to be connected to which logic slots for a script to function as intended.
  • Logic Walkthroughs: Get a step-by-step breakdown of conditional triggers and thresholds within a script to understand why certain actions occur during gameplay.
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"