skills.rest
ITSalt
ITSaltCOMMUNITY
Explore all skills by this author →
GitHub

nacl-tl-sync

Compare backend and frontend implementations against the API contract to identify drift.

23|2|Updated Apr 10, 2026
Search Tags:#frontend#backend#sync#verify#api-contract#report-generation
One-click install
npx skills add https://github.com/ITSalt/NaCl --skill nacl-tl-sync
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: nacl-tl-sync
Source: https://github.com/ITSalt/NaCl/tree/main/nacl-tl-sync
Command: npx skills add https://github.com/ITSalt/NaCl --skill nacl-tl-sync

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Verifies that backend and frontend implementations stay in sync with the API contract, preventing runtime mismatches and integration issues.

Core Features & Use Cases

  • Compare BE/FE against the API contract and identify drift
  • Generate sync-report.md and update .tl tracking files
  • Validate prerequisites and provide remediation steps for blockers

Quick Start

Initiate the UC sync workflow to generate a report and update tracking files.

Frequently Asked Questions about nacl-tl-sync

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

FAQPage Schema
How do I prevent backend and frontend API contract drift after feature updates?▼

To prevent API contract drift, you must compare the API contract directly against backend and frontend implementations. This validation identifies mismatches and generates a sync report to prevent runtime integration issues.

What is API contract synchronization and when do I need to validate it?▼

API contract synchronization verifies that backend and frontend implementations match the documented API contract. You must validate it after API changes, feature updates, or UC changes to prevent runtime mismatches.

What files do I need to verify BE and FE API contract alignment?▼

Verifying BE and FE API contract alignment requires access to the api-contract.md file, backend and frontend source code, and shared types. These inputs enable the workflow to identify drift and output tracking files.

How do I generate a sync report for BE and FE implementations?▼

You generate a sync report by initiating the UC sync workflow, which compares your BE/FE source against the API contract. The workflow outputs a sync-report.md file and updates .tl tracking files.

Does validating API contract synchronization require specific dependencies?▼

Validating API contract synchronization has no external dependencies, but it requires prerequisite files like api-contract.md, BE/FE source, and shared types. It validates prerequisites and provides remediation steps for blockers.

What's the best way to check for runtime mismatches after API changes?▼

The best way to check for runtime mismatches is to compare the API contract directly against backend and frontend implementations. This identifies drift early and outputs a sync report to guide remediation.

Related Skills

Explore More Software Engineering Skills→
juan-estrada-ittijuan-estrada-itti

contract-define

Generate API contract documents from RFC and PRD inputs.

Community
Advanced
datamonsterrdatamonsterr

speckit-sync-propose

Generate drift-resolution proposals for spec and code divergences.

Community
Advanced
RomualdPRomualdP

API Contracts Generator

Generate synchronized DTOs and TypeScript types for Next.js and NestJS API contracts.

Community
Advanced
robotijnrobotijn
3

type-checker

Enforce strict-mode type checking across 7 mainstream programming languages.

Community
Advanced