What problem does it solve? Structured data in a codebase can silently drift back to ad-hoc JSON writes on files and wire protocols, breaking format consistency and the migration ratchet. This Skill keeps every change to JavaScript or TypeScript source under apps or packages aligned with the TOON snapshot, TOONL stream, and TOON wire frame defaults. ## Core Features & Use Cases - TOON file discipline: Writes every *.toon file with the TOON encoder and reads it with the sniffing decoder, treating runtime JSON compatibility as a migration aid only. - Wire frame enforcement: Sends with encodeWireFrame and receives with decodeWireFrame from @reddb-io/shared/resident-wire.js, keeping owned wires on TOON frames while tolerating legacy JSON during rollouts. - JSON boundary classification: Records intentional JSON file or wire sites in .red/contracts/toon-json-file-io-allowlist.json as external or migrate, and prefers explicit --json output branches for caller-requested formats. - Use Case: When editing a TypeScript module that persists state or transports payloads, apply this Skill so the touched flow defaults to TOON, remaining JSON sites are classified, and toon-json-guard.test.ts passes. ## Quick Start Use the guard-serialization skill to review my changes to the TypeScript files under packages that read and write structured state, and make sure they default to TOON with any remaining JSON sites classified in the allowlist.