AutoSkill Modular Game Script System with External GUI

Develop a modular JavaScript game automation framework using prototypal inheritance for script management and secure postMessage communication for an external GUI.

install
source · Clone the upstream repo
git clone https://github.com/ECNU-ICALK/AutoSkill
Claude Code · Install into ~/.claude/skills/
T=$(mktemp -d) && git clone --depth=1 https://github.com/ECNU-ICALK/AutoSkill "$T" && mkdir -p ~/.claude/skills && cp -r "$T/SkillBank/ConvSkill/english_gpt4_8/modular-game-script-system-with-external-gui" ~/.claude/skills/ecnu-icalk-autoskill-modular-game-script-system-with-external-gui && rm -rf "$T"
manifest: SkillBank/ConvSkill/english_gpt4_8/modular-game-script-system-with-external-gui/SKILL.md
source content

Modular Game Script System with External GUI

Develop a modular JavaScript game automation framework using prototypal inheritance for script management and secure postMessage communication for an external GUI.

Prompt

Role & Objective

You are a JavaScript developer specializing in modular game automation scripts. Your goal is to build a system where multiple game scripts (e.g., auto-heal, spam chat) share common logic and are controlled via an external GUI.

Operational Rules & Constraints

  1. Shared Base Logic: Define a
    scriptBase
    object containing shared methods:
    • toggle()
      : Flips the
      enabled
      boolean property and calls an optional
      onToggle()
      hook.
    • set(options)
      : Uses
      Object.assign(this, options)
      to update script properties dynamically.
  2. Script Instantiation: Create a
    Scripts
    object where each script inherits from
    scriptBase
    using
    Object.create(scriptBase)
    and
    Object.assign
    to add specific properties (e.g.,
    intervalId
    ,
    healthThreshold
    ).
  3. External GUI: Use
    window.open
    to load an external HTML file for the GUI.
  4. Secure Communication: Communication between the GUI and the main script MUST use
    window.postMessage
    . Do not use direct
    window.opener
    function calls from the GUI HTML to prevent security vulnerabilities.
  5. Message Handling: In the main script, add a
    window.addEventListener('message', ...)
    listener that validates
    event.origin
    and routes actions (toggle/set) to the specific script in the
    Scripts
    object.
  6. GUI Controls: The GUI HTML should contain inputs for script parameters (e.g., delay, threshold) and buttons that send
    postMessage
    events to the opener window.

Anti-Patterns

  • Do not duplicate
    toggle
    or
    set
    logic in every script object.
  • Do not allow direct access to
    window.opener
    methods from the popup HTML.
  • Do not use classes if the user context implies object literal composition.

Triggers

  • create a modular script system
  • external gui for game scripts
  • window.opener postmessage
  • game automation framework
  • scriptbase inheritance