create-timeline-command

Automate adding a timeline command to the HS2 Sandbox workflow.

4|Updated Dec 1, 2025
One-click install
npx skills add https://github.com/SuitIThub/HS2-Sandbox --skill create-timeline-command
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: create-timeline-command
Source: https://github.com/SuitIThub/HS2-Sandbox/tree/main/.cursor/skills/create-timeline-command
Command: npx skills add https://github.com/SuitIThub/HS2-Sandbox --skill create-timeline-command

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates the addition of a new timeline command to the HS2 Sandbox workflow.

Core Features & Use Cases

  • Create Timeline/YourCommand.cs in Timeline/
  • Register in TimelineCommandFactory.cs
  • Add a toolbar button in SubWindows/ActionTimeline.cs
  • Enforces required payload/serialization conventions and IMGUI wiring
  • Use cases: when developers want to add new timeline commands, extend the timeline with new behavior, ensure consistent integration.

Quick Start

Create the command class file in Timeline/, register it in TimelineCommandFactory, and add a toolbar button in ActionTimeline to expose it.

Frequently Asked Questions about create-timeline-command

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

FAQPage Schema
How do I add a custom timeline command to the HS2 Sandbox workflow?

Adding a custom timeline command requires creating a command class file in Timeline/, registering it in TimelineCommandFactory.cs, and exposing it through a toolbar button in ActionTimeline.cs.

What files need to be modified when creating a new HS2 timeline command?

Creating a new HS2 timeline command involves modifying TimelineCommandFactory.cs for factory registration, SubWindows/ActionTimeline.cs for UI integration, and creating a new command class file in the Timeline/ directory.

Does adding a timeline command require manual payload and serialization setup?

Adding a timeline command requires payload and serialization setup, but the scaffolding process enforces required payload and serialization conventions along with the necessary IMGUI wiring automatically.

What is the best way to ensure consistent integration when extending the HS2 timeline?

The best way to ensure consistent HS2 timeline integration is to use a scaffolding process that enforces required files, factory registration, and UI hooks for every new custom command.

Can I expose a new timeline behavior through the ActionTimeline toolbar?

You can expose a new timeline behavior by adding a toolbar button in SubWindows/ActionTimeline.cs, which connects the registered custom command class to the timeline user interface.

Why does my timeline command not appear in the HS2 Sandbox factory?

A timeline command fails to appear in the HS2 Sandbox if it is not registered in TimelineCommandFactory.cs, which is a required step alongside creating the command class and wiring the UI button.