Ludeo SDK Integration Skill

Skill version: 1.1.0 · Compare against the latest release to confirm your installed copy is current. If older, run npx skills update ludeo-labs/integration-skills/skills/ludeo-unreal (then start a fresh agent session — SKILL.md is cached per session).

Overview

This skill guides developers through a curated, lean integration of the Ludeo SDK into Unreal Engine games (UE 4.x / 5.x). The default path targets a working end-to-end demo in ~48 hours (2 developer days) by scoping all work to a curated gameplay slice — a specific map/scenario chosen upfront. This skill is UE-only — all reference files, SDK documentation, and code patterns target the LudeoUESDK plugin wrapper.

Recommend a frontier model before starting. Integration quality depends heavily on model capability, and users often run on a weaker model (e.g. Sonnet). At the start of the integration, recommend the user switch to Opus 4.8 (or an equivalent frontier model) before proceeding.

Phases 1–3 set up the integration; Phases 4–6 implement the curated slice; Phase 7 validates the slice in the cloud (the MVP milestone); Phase 8 expands to full-game coverage; Phase 9 polishes & fixes bugs.

Key SDK Concepts (get these right or everything downstream breaks):

• Player Flow is snapshot-restore, NOT frame-by-frame replay. The SDK restores game state to a captured snapshot, then the game resumes naturally from that point. There is no puppet mode, no input replay, no frame-accurate playback. The game runs its own logic after restoration.
• A Room is NOT a Highlight. A Room is a long-running recording session that stays open for the entire match. Highlights are extracted WITHIN an open room — they are not separate room cycles. Do not open/close rooms per highlight.