Profile My skills Saved Collections Edit profile Submit a skill

← all publishers

xcratch

@xcratch source repo

5 published skills

  1. ▌
    Xcratch Extension Debug · xcratch bundle
    Use when debugging an in-development Xcratch extension in VS Code. Trigger phrases: breakpoints not hit, source maps, debug on xcratch.github.io editor, live server HTTPS, extension not loading in editor.
    0
    installs
  2. ▌
    Xcratch Extension Create · xcratch bundle
    Use when setting up a new Xcratch extension project and local development environment. Trigger phrases: xcratch-create, scaffold extension, setup-dev, initialize extension repo, local extension setup.
    0
    installs
  3. ▌
    Xcratch Extension Stretch3 · xcratch bundle
    Use when adding an Xcratch extension to stretch3 (https://stretch3.github.io). Creates stretch3-install.sh, webpack-mjs-support.patch, and index-stretch.jsx. Trigger phrases: add to stretch3, stretch3 install, stretch3-install, stretch3 スクリプト.
    0
    installs
  4. ▌
    Xcratch Extension Debug Auto · xcratch
    Autonomously debug an Xcratch extension by loading it via the ?extension= query parameter into either the public xcratch.github.io editor or a local scratch-editor dev-server, with the extension served from a local HTTPS live server (https://0.0.0.0:5500/*). Use when: verifying an extension loads, checking console errors, inspecting extension blocks in the Scratch editor UI, or reproducing runtime failures with a specific extension URL — against the published editor (no local checkout needed) or against a local scratch-editor build on port 8601.
    0
    installs
  5. ▌
    Xcratch Extension Palette Refresh · xcratch bundle
    Use when a scratch-vm / Xcratch extension creates, deletes, or renames a variable or list programmatically (e.g. target.lookupOrCreateList / createVariable / deleteVariable) and the change does NOT appear in the editor block palette until the user re-opens the Code tab or switches sprites. Make sure to use this whenever programmatic changes to the VM variable/list model (or custom My Blocks procedures) are not reflected in the Scratch editor palette right away, or whenever someone asks how to force the Blockly toolbox / variable-list flyout to refresh from extension code. Also covers the companion bug this fix introduces: calling requestBlocksUpdate mid-execution orphans the running script's yellow stack-glow highlight (the outline stays lit until the Code tab is reopened, or disappears while still running). Trigger phrases: list created but not in palette, variable not showing until tab switch, requestBlocksUpdate / emitWorkspaceUpdate did not update the palette, refresh toolbox flyout, force variable catego
    0
    installs