suede-parity-contract

Generates cross-surface parity contracts so shared constants fail tests instead of drifting.

123|10|Updated May 24, 2026
One-click install
npx skills add https://github.com/JasonColapietro/suede-creator-skills --skill suede-parity-contract-jasoncolapietro
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: suede-parity-contract
Source: https://github.com/JasonColapietro/suede-creator-skills/tree/main/skills/suede-parity-contract
Command: npx skills add https://github.com/JasonColapietro/suede-creator-skills --skill suede-parity-contract-jasoncolapietro

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When the same rule, threshold, ladder, or stated fact lives on two or more surfaces (web, iOS, Android, docs, a second service), hand-copied values silently drift apart, and users or answer engines discover the contradiction first. This Skill replaces manual copying with a generated contract so any divergence fails a test instead of reaching production. ## Core Features & Use Cases - Generated contracts: Builds a JSON contract by importing live constants from one designated reference surface, never by retyping values, with stable key ordering for byte-identical vendoring. - Staleness and follower tests: Adds a reference-side test that fails when the committed contract drifts from the code, plus follower tests that assert through public behavior rather than reimplementing formulas. - Divergence management: Records existing differences under knownDivergences with reasons, guards the exact expected set, and halts with a structured report when a new divergence is found mid-build. - Use Case: Your pricing threshold is defined in your web backend and copied into your iOS app. Use this Skill to generate a contract from the backend constants, vendor it byte-identical to the iOS repo, and add tests that fail the moment either side changes. ## Quick Start Use the suede-parity-contract skill to generate a parity contract from my reference service's constants and set up assertion tests in the follower app.

Frequently Asked Questions about suede-parity-contract

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

FAQPage Schema
How do I keep constants in sync across multiple platforms?

Designate one reference surface, generate a JSON contract by importing its live constants, and vendor a byte-identical copy to each follower. Follower tests then assert against the contract through public behavior, so any drift fails a test instead of shipping.

How do I detect when shared values drift between my app and website?

Add a staleness test on the reference side that rebuilds the contract in memory and compares it to the committed file, naming the key that moved. On followers, compare SHA-256 hashes of the vendored copies to prove they match the reference.

Should follower tests reimplement the reference formula?

No. A follower test that reimplements the formula only proves you can write the same bug twice. Assert observable behavior instead, such as feeding contract values to the public accessor and checking the returned result at boundaries.

What happens when two surfaces already disagree on a value?

The skill halts and reports the divergence with both values and options, without deciding which side is correct. Existing divergences are recorded under knownDivergences with reasons and guarded so the list matches exactly the expected set.

When should I not use a parity contract?

Do not use it to decide which surface's value is correct, review diffs, wire merge gates, or audit a page for generative search. It also must not carry credentials, hostnames, or per-environment configuration, only domain constants.