review-product-data

Name: review-product-data
Availability: InStock
Author: cesau78

Audit JSON product and batch data for camelCase keys and build-time loading.

Updated Apr 2, 2026

Search Tags:#data-validation #schema-drift #camelcase-keys #json-data #typescript-consumers #build-time-loading

Ready to run

npx skills add https://github.com/cesau78/cesau-skills --skill review-product-data

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: review-product-data
Source: https://github.com/cesau78/cesau-skills/tree/main/review-product-data
Command: npx skills add https://github.com/cesau78/cesau-skills --skill review-product-data

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Reviews JSON product and batch data under tektonology-spa/data/ for camelCase keys, consistency with TypeScript consumers, and build-time loading assumptions. Use when data JSON or loaders change, or when skills-advisor recommends this lens.

Core Features & Use Cases

Validates key naming conventions (camelCase) across products and batches.
Detects schema drift, shape inconsistencies, and duplicated or conflicting metadata.
Enforces static build loading patterns and identifies data loader assumptions to prevent runtime fetches.

Quick Start

Review tektonology-spa/data/ JSON to confirm camelCase keys, TypeScript compatibility, and static build loading.

Frequently Asked Questions about review-product-data

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

FAQPage Schema

How do I validate camelCase keys in JSON product data?▼

To validate camelCase keys in JSON product data, audit the files to verify key naming conventions across products and batches, ensuring consistency for TypeScript consumers. This process detects duplicated or conflicting metadata and confirms structural compliance.

How do I detect schema drift in JSON batch data?▼

Detecting schema drift in JSON batch data involves auditing the data files for shape inconsistencies and conflicting metadata. The review identifies where data structures have diverged across batches, ensuring type-safe consumption.

What is build-time loading for JSON data and why does it matter?▼

Build-time loading for JSON data enforces static read patterns during the build process, preventing runtime fetches. It matters because it ensures data loader assumptions are valid and the data is fully resolved for TypeScript consumers before deployment.

Can I use this data audit for TypeScript consumers and static build loading?▼

Yes, you can use this data audit for TypeScript consumers and static build loading. It verifies JSON data compatibility with TypeScript interfaces and enforces static build-time reads, ensuring no unexpected runtime fetches occur.

When should I audit JSON data for build-time loading assumptions?▼

You should audit JSON data for build-time loading assumptions when data JSON files or loaders change. This prevents runtime fetches by verifying that static build loading patterns and data loader assumptions remain valid after modifications.