structured-outputs-integration-gate

What problem does it solve?

This Skill prevents behavior regressions when migrating from prompt-based JSON extraction to API-side schema validation while legacy post-processing filters still exist, avoiding the situation where a previously “silently cleaned” legacy edge case suddenly becomes a hard failure.

Core Features & Use Cases

• Defines a two-layer test contract to protect both the new schema and the legacy wrapper behavior.
• Specifies a wrapper-path gate that is the only place you can observe the contract boundary between “new strict validator” and “old silent filters.”
• Prevents common anti-patterns such as relying on schema-unit tests alone or accidentally validating before legacy filters run.

Use cases include integrating any provider’s structured-output / JSON-schema / typed-parse endpoint into an existing response pipeline that already has response-cleaning logic.

Quick Start

Add this skill when your plan switches to API structured outputs and ensure your test plan includes both a schema unit test and a full wrapper-path test that injects the legacy “silent strip” scenario.