darling-martech-data

Validate site data shapes and slug uniqueness against /data/ schemas.

Updated Mar 18, 2026
One-click install
npx skills add https://github.com/DarlingMarketingandTech/darling-martech --skill darling-martech-data
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: darling-martech-data
Source: https://github.com/DarlingMarketingandTech/darling-martech/tree/main/skills/darling-martech-data
Command: npx skills add https://github.com/DarlingMarketingandTech/darling-martech --skill darling-martech-data

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill acts as the authoritative data layer manager for all site content, centralizing schemas and ensuring consistent data structures across labs, services, work, and testimonials.

Core Features & Use Cases

  • Defines the data contracts for /data/ content (labs.ts, services.ts, testimonials.ts, work/index and work/data).
  • Validates slug uniqueness and cross-file references when adding new content (e.g., new case study, new lab tool, new service).
  • Provides a single source of truth for data shape, enabling components to consume typed objects safely.

Quick Start

Add or update content in /data/ only after validating slug uniqueness and data shape against the defined schemas.

Frequently Asked Questions about darling-martech-data

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

FAQPage Schema
How do I validate slug uniqueness when adding new content to a TypeScript data layer?

To validate slug uniqueness in a TypeScript data layer, add or update content in the /data/ directory only after validating slug uniqueness and data shape against the predefined schemas. This enforces exact data shapes and cross-file consistency.

What is a typed data schema and when do I need it for site content?

A typed data schema defines the data contracts for content files like labs, services, and testimonials. You need it when adding new pages or components to ensure consistent data structures and provide a single source of truth for safe object consumption.

How do I enforce cross-file consistency across labs, services, and work indices?

You enforce cross-file consistency across labs, services, and work indices by using a centralized data layer manager. It validates cross-file references and data shapes against predefined schemas when wiring up new slugs or updating data entries.

Does this data validation approach work without external dependencies?

Yes, this data validation approach works without external dependencies. It enforces exact data shapes, slug uniqueness, and cross-file consistency using predefined /data/ schemas directly within your TypeScript workflow.

What are the limitations of managing a data layer with predefined schemas?

The limitation of managing a data layer with predefined schemas is that content must strictly conform to exact data shapes. You must validate slug uniqueness and cross-file references before adding or updating any entries in the /data/ directory.