s1-implement-boss

Implement Sonic 1 boss encounters in OpenGGF with ROM-accurate behavior.

6|1|Updated Jan 16, 2013
One-click install
npx skills add https://github.com/OpenGGF/OpenGGF --skill s1-implement-boss-openggf
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: s1-implement-boss
Source: https://github.com/OpenGGF/OpenGGF/tree/main/.claude/skills/s1-implement-boss
Command: npx skills add https://github.com/OpenGGF/OpenGGF --skill s1-implement-boss-openggf

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a structured workflow for implementing Sonic 1 boss encounters in OpenGGF with ROM-accurate behavior, reducing guesswork across disassembly research, arena setup, and gameplay logic.

Core Features & Use Cases

  • Disassembly-driven implementation: Maps boss object logic, state transitions, and child-object spawning from the Sonic 1 disassembly into engine code.
  • Arena and event setup: Handles camera locks, boundary changes, spawn timing, and boss music transitions through level event systems.
  • Hit and defeat sequencing: Recreates hit counts, palette flashes, invulnerability timing, and defeat sequences for zone-specific bosses.
  • Use case: A contributor can use this Skill to implement the Green Hill, Marble, or Final Zone boss and validate the result against the original ROM behavior.

Quick Start

Use this skill to implement a Sonic 1 boss in OpenGGF by matching the disassembly references, wiring the arena and event logic, and validating the resulting behavior against the original game.

Frequently Asked Questions about s1-implement-boss

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

FAQPage Schema
How do I implement Sonic 1 boss encounters with ROM-accurate behavior in OpenGGF?

To implement Sonic 1 boss encounters accurately, this Skill maps boss object logic, state transitions, and child-object spawning from the Sonic 1 disassembly directly into engine code. It ensures zone boss ports match original ROM behavior by validating obRoutine and ob2ndRout logic.

What is the best way to set up Sonic 1 boss arenas and camera boundaries?

Setting up Sonic 1 boss arenas requires configuring camera locks, boundary changes, spawn timing, and boss music transitions. This is achieved through the engine's level event systems to ensure arena locking and event triggers match the original disassembly references.

How do boss hit handling and defeat sequences work in the Sonic 1 disassembly?

Boss hit handling and defeat sequences in the Sonic 1 disassembly rely on specific hit counts, palette flash timing, and invulnerability frames. This Skill recreates these exact state transitions and defeat sequences for zone-specific bosses to ensure ROM-accurate validation.

Can I use this Skill to port Green Hill or Marble Zone bosses to a custom game engine?

Yes, you can use this Skill to port Green Hill, Marble, or Final Zone bosses into OpenGGF. It provides a structured workflow for matching disassembly references, wiring arena logic, and validating resulting gameplay behavior against the original ROM.

Why do my Sonic 1 boss ports have incorrect state machine transitions in OpenGGF?

Incorrect Sonic 1 boss state machine transitions often occur when obRoutine and ob2ndRout behaviors are mismatched. This Skill requires matching these exact routines, child-object spawning, and registry integration to guarantee ROM-accurate boss validation.

Do I need the Sonic 1 disassembly to implement boss encounters with this Skill?

Yes, the Sonic 1 disassembly is required as it drives the implementation. This Skill maps object logic, state transitions, and child-object spawning from the disassembly references into engine code for accurate boss behavior validation.