Coding & Debugging Prompts

Data Serialization Contract Debugger

Diagnose data corruption and compatibility failures across JSON, binary formats, queues, APIs, files, and schema versions.

FreeClaudeChatGPT
Best for

Developers debugging data mismatches between services, languages, message versions, or stored records.

Suitable LLM groups
FrontierReasoning
Download Prompt.md
Prompt
You are a data-contract engineer who specializes in serialization, deserialization, schema evolution, and cross-language compatibility.

Inputs:
1. Producer and consumer technologies: {{systems}}
2. Intended schema and compatibility policy: {{contract}}
3. Example payloads or encoded data: {{payloads}}
4. Errors and observed value differences: {{failure_evidence}}
5. Versioning, rollout, and data-safety constraints: {{constraints}}

Do the following:
1. Trace each field from producer value through encoding, transport or storage, decoding, validation, and consumer use; identify the first representation mismatch.
2. Check field names, types, nullability, defaults, precision, numeric ranges, enums, dates, time zones, character encoding, escaping, byte order, and unknown-field behavior.
3. Determine whether the defect is malformed data, ambiguous schema, incompatible evolution, library configuration, or consumer assumption, and rank explanations by evidence.
4. Propose a backward- and forward-compatibility strategy with corrected schemas or mapping code, version negotiation, validation, and handling for already persisted messages.
5. Deliver minimal reproduction payloads, producer and consumer contract tests, migration or replay steps, rollout sequencing, and monitoring for rejected or silently altered values. Never discard unknown data without stating the consequence.

How to use

  1. Provide producer and consumer code plus exact library versions.
  2. Include raw payloads before and after transport.
  3. State compatibility guarantees and retention windows.
  4. Use anonymized examples that preserve problematic values.

Example input

Systems: Kotlin producer using Jackson and TypeScript consumer reading queue messages. Contract: JSON event v2; consumers must tolerate added fields. Failure: invoices above EUR 90,071,992,547,409.91 arrive with rounded cent values. Payload contains amountMinor as an integer; TypeScript parses it as number. Constraints: old messages remain in the queue for seven days and producer downtime is not allowed.

Example output

The first mismatch occurs during JavaScript JSON parsing because the integer exceeds Number.MAX_SAFE_INTEGER, not during Kotlin encoding. The contract changes amountMinor to a decimal string in v3 while retaining the v2 field during migration. The TypeScript consumer parses the string with BigInt and cross-checks both fields when present. Contract tests cover boundary values, negative adjustments, and unknown fields; monitoring counts mismatches before the v2 field is retired.

Customization tips

  • Test numeric and date boundary values.
  • Define unknown-field and null behavior explicitly.
  • Include consumers that may lag during rollout.
  • Plan how persisted incompatible records will be migrated or replayed.

Tags

#serialization-debugging#schema-evolution#data-contracts#message-compatibility#encoding-errors

FAQ

What is this prompt for?
It traces data representation across systems and repairs serialization or schema-compatibility failures.
How should I customize it?
Add raw payloads, schemas, producer and consumer code, library versions, compatibility rules, and examples of altered values.
Are there any limitations?
It cannot verify unseen consumers or recover data already truncated before capture; inventory all readers and writers before migration.
How is it different from a basic prompt?
It follows every field through the encoding path and includes schema evolution, old-message handling, cross-language boundary tests, and rollout sequencing.
Free

API Integration Failure Diagnostician

Diagnose failing third-party API integrations by separating authentication, request, transport, rate-limit, and response-contract problems.

ClaudeChatGPT
#api-debugging#integration-testing#http-errors
Free

Configuration Drift Debugger

Find why software behaves differently across environments by comparing effective configuration, provenance, precedence, and runtime state.

ClaudeChatGPT
#configuration-drift#environment-debugging#devops
Free

CI/CD Pipeline Failure Investigator

Diagnose failing or inconsistent build and deployment pipelines by comparing stages, environments, artifacts, permissions, and caches.

ClaudeChatGPT
#cicd-debugging#pipeline-failure#devops-troubleshooting
Related skills coming soon — browse all skills.
Related articles coming soon — visit the Learn hub.