domains / families / software-engineering / debug-extension

debug-extension

separate

Diagnose and fix failures in a built third-party `.ppmplugin` control: crashes, silent no-ops, PCF error outputs, or incorrect behavior. Uses the reported symptom, `shared/error-codes.md`, and file-level evidence to trace the manifest, Android/iOS modules, PCF dispatch, and build configuration. Produces a ranked diagnosis, asks for approval, then applies a surgical fix while keeping the committed manifest and affected contracts synchronized. Re-validates manifest changes through /generate-ppmplugin-manifest.

When to use

• Diagnose crashes in built .ppmplugin controls
• Fix silent no-ops in extension controls
• Trace PCF error outputs
• Resolve incorrect behavior in built controls
• Investigate parity or transport bugs
• Fix behavior drift in extension operations

When not to use

• Scaffolding new extension repos
• Designing brand-new operations
• Planned changes with known edits and no reported failure
• Build failures where no binary was produced
• Installing dependencies or building binaries

Skill page

Source