data-contracts

Applies predefined business-rule checks to validate and normalize incoming/outgoing API payloads.

Updated May 17, 2026
One-click install
npx skills add https://github.com/cheetah-alo/NegritaOS --skill data-contracts-cheetah-alo
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: data-contracts
Source: https://github.com/cheetah-alo/NegritaOS/tree/main/.codex/skills/data-contracts
Command: npx skills add https://github.com/cheetah-alo/NegritaOS --skill data-contracts-cheetah-alo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents downstream bugs by ensuring JSON contracts and typed normalization rules are consistently validated and enforced across services.

Core Features & Use Cases

  • Schema validation with explicit rules: Validates required fields, naming, nullability, and supported values deterministically.
  • Contract-driven casting and normalization: Applies visible, deterministic transformations so types are standardized at the boundary.
  • Stable contract violation errors: Produces consistent, contract-enforced error behavior when inputs break contract expectations.
  • Use Case: You change an API contract JSON or profile loader behavior and need to guarantee that transaction metadata and financial KPI computations still receive correctly shaped, normalized inputs.

Quick Start

Use the data-contracts skill to validate and apply schema-enforced transformations for backend/app/configs/*.json and the contract surface at backend/app/api/rules_api_contract.json.

Frequently Asked Questions about data-contracts

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I validate JSON schema and enforce data contracts for API payloads?

Schema validation enforces data contracts by checking required fields, naming, nullability, and supported values. It applies deterministic typed normalization to API payloads, ensuring inputs are correctly shaped and standardized at the boundary.

What is deterministic typed normalization for data contracts?

Deterministic typed normalization applies visible transformations to standardize types at the boundary. It ensures JSON contracts and typed normalization rules are consistently enforced across services to prevent downstream bugs.

How do I ensure stable errors when contract violations occur in API payloads?

Stable contract violation errors are produced by applying explicit field checks and consistent contract-enforced error behavior. This guarantees deterministic outcomes when inputs break contract expectations in API payloads.

Can I use data contract validation for financial KPI computations and transaction metadata?

Yes, data contract validation works for financial KPI computations and transaction metadata. It enforces contract-like rules in services that derive transaction and KPI outputs, guaranteeing correctly shaped normalized inputs.

What is the best way to update validation behavior in contract profile loaders?

The best way to update validation behavior is modifying contract JSON files and profile loaders with explicit field checks and visible casting semantics. This maintains stable errors when contract violations occur.

Why do I need explicit field checks for schema validation in backend services?

Explicit field checks are needed for schema validation to prevent downstream bugs. They ensure JSON contracts and typed normalization rules are consistently validated, producing stable errors when inputs break contract expectations.