gum-tool-file-watch

Monitor Gum project file changes and dispatch reloads by file type.

597|79|Updated Mar 11, 2015
One-click install
npx skills add https://github.com/vchelaru/Gum --skill gum-tool-file-watch
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gum-tool-file-watch
Source: https://github.com/vchelaru/Gum/tree/main/.claude/skills/gum-tool-file-watch
Command: npx skills add https://github.com/vchelaru/Gum --skill gum-tool-file-watch

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill tackles the challenge of keeping Gum projects synchronized with external file modifications, preventing outdated assets and ensuring real-time updates without manual intervention.

Core Features & Use Cases

  • File Monitoring Pipeline: Tracks changes via FileSystemWatcher, queues events, and flushes with debouncing to handle rapid edits efficiently.
  • Smart Directory Watching: Automatically determines directories to monitor based on referenced files in project elements, with deduplication for optimal performance.
  • Ignore and Reaction Logic: Suppresses self-induced changes to avoid loops and dispatches updates by file type, such as reloading textures or elements.
  • Use Case: When editing a PNG texture in an external tool like Photoshop while working in Gum, this system detects the save and refreshes the wireframe preview instantly, streamlining iterative design workflows.

Quick Start

Describe the Gum FileWatch pipeline for handling a changed .gusx element file during project development.

Frequently Asked Questions about gum-tool-file-watch

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automatically reload Gum project files when external assets change?

To automatically reload Gum project files, you can monitor external file changes using a FileSystemWatcher pipeline that queues events and applies debouncing to refresh textures and elements without triggering false reloads.

How does file change detection handle rapid external edits to UI layout assets?

File change detection handles rapid edits by queuing FileSystemWatcher events and flushing them with debouncing, ensuring multiple consecutive saves result in a single synchronized asset reload instead of performance bottlenecks.

Can I prevent false reloads caused by self-induced file modifications in Gum projects?

Yes, you can prevent false reloads by applying an ignore mechanism that suppresses self-induced file modifications, effectively breaking feedback loops and ensuring only external asset edits trigger the synchronization pipeline.

Does the file watcher automatically determine which directories to monitor for Gum elements?

The file watcher automatically determines directories to monitor by scanning referenced files within project elements, applying deduplication to optimize performance and ensure only relevant locations are watched for asset updates.

How do you reload textures and elements differently when monitoring external file changes?

To reload textures and elements differently, the file monitoring system dispatches updates based on file extensions, ensuring specific asset types like PNG textures or .gusx element files trigger their appropriate refresh workflows.