---
name: cut-design-debugger
description: Modify and validate Tornado3/Karisma election cut designs in this repository. Use when Codex needs to change a cut layout or asset mapping, troubleshoot scene-variable visibility or style issues, inspect T3_Cut scene behavior, or run repo-local validation after a cut change.
---

# Cut Design Debugger

Use this skill to make the smallest safe change to a cut-related workflow, then validate it with the repo's existing Karisma tools.

## Workflow

1. Identify the target before editing.
- Confirm the requested template, cut, channel, and visible symptom.
- Search the repo spec first: `SYSTEM_SPEC.md`, `RGB_SPEC_CUT_MAPPING.md`, and `CURRENT_IMPLEMENTATION_STATUS_2026-04-17.md`.
- Map the request to the owning code before changing anything. Read [repo-map.md](references/repo-map.md) when the affected area is not obvious.

2. Edit the smallest surface that can explain the behavior.
- Catalog or cut-list problems usually live in `FormatCatalogService`, `MainViewModel`, or thumbnail helpers.
- Scene resolution, path, and asset lookup issues usually live in `KarismaSceneResolver`, `KarismaSceneVariableCatalog`, `TornadoPathResolver`, or `KarismaTornado3Adapter`.
- Runtime value, visibility, color, and candidate-slot logic usually lives in `KarismaTornado3Adapter`.
- If the problem exists only inside external `T3_Cut` assets, call that out explicitly before assuming a repo-side fix exists.

3. Validate in layers after every meaningful change.
- Always run `dotnet build Tornado3_2026Election.slnx` when code changed.
- Use [validation-workflow.md](references/validation-workflow.md) for command selection.
- For a scoped live pass, prefer `scripts/validate-cut.ps1`.
- For scene-level snapshots or raw object checks, use `tools/KarismaTcpProbe` directly.
- If live Karisma or the fixed `D:\Elect2026\T3_Cut` root is unavailable, still run the build and document the missing external dependency.

4. Report the result in operational terms.
- Name the files changed.
- List the commands run.
- Say what was verified, what remains unverified, and whether external Karisma or `T3_Cut` access blocked anything.

## Repo Notes

- Treat the repo as the source of truth for cut metadata and validation helpers.
- Treat `D:\Elect2026\T3_Cut` as the fixed external dependency that may contain the real scene or asset causing the issue.
- Prefer targeted validation with a template or cut filter instead of sweeping the whole catalog unless the user asks for a broad audit.
- Reuse existing `tools/KarismaTcpProbe/scene-ops/*.json` fixtures when they match the symptom instead of inventing a new validation format.

## Resources

- `scripts/validate-cut.ps1`: run scoped live validation against the existing `KarismaTcpProbe` tool.
- [repo-map.md](references/repo-map.md): load when you need to find the owning file quickly.
- [validation-workflow.md](references/validation-workflow.md): load when you need the exact validation command for the current symptom.
