OpenParable
Skip to content
← Back to skills

F8 Editor Event Workflow

Testing & Quality
f8-editor-event-workflow

F8 Editor Event Workflow is an Agent Skill for testing & quality published in the TippingGame/F8Framework repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.

Use when working with Event editor tools — event system monitor window for debugging active listeners in F8Framework.

View on GitHub ↗
QUICK START

How to use this skill

Bring this guide into your coding agent with a prompt tailored to the tool you use.

  1. Open your project in Codex.
  2. Copy and paste the prompt below.
  3. Review files and risks before approving any action.
Prompt to paste
Inspect the Agent Skill at https://github.com/TippingGame/F8Framework/blob/HEAD/Tests/AISkills/f8framework-skills/editor/f8-editor-event-workflow/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/f8-editor-event-workflow, but wait for my approval before writing files or running scripts.

Copying this prompt does not install or run the skill. Review third-party files before use.

Event Editor Workflow

Use this skill when

  • The task involves debugging event listeners or tracking event dispatch in Editor.
  • The user asks about the Event System Monitor window.

Path resolution

  1. Editor code: Assets/F8Framework/Editor/Event

Sources of truth

  • Editor module: Assets/F8Framework/Editor/Event
  • Test docs: Assets/F8Framework/Tests/Event/README.md

Key editor features

FeatureDescription
Event System MonitorEditor window showing all registered listeners, their event IDs, and subscriber objects

Workflow

  1. Open Event System Monitor from the F8Framework menu.
  2. View all active event listener registrations.
  3. Identify event IDs and which objects are listening.
  4. Debug event dispatch issues by verifying listener presence.
  5. Detect potential memory leaks from unremoved listeners.

Output checklist

  • Event monitor opened and reviewed.
  • Listener registrations verified.
  • Dead listeners identified and cleaned.