platform-parity-check

Name: platform-parity-check
Availability: InStock
Author: treystu

Checks interoperability matrix across platforms for contract deviations.

2|Updated Feb 6, 2026

Search Tags:#cross-platform testing #consistency verification #platform parity #UniFFI #feature regression #messaging controls #api.udl

Ready to run

npx skills add https://github.com/Treystu/SCMessenger --skill platform-parity-check

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: platform-parity-check
Source: https://github.com/Treystu/SCMessenger/tree/main/skills/platform-parity-check
Command: npx skills add https://github.com/Treystu/SCMessenger --skill platform-parity-check

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents security-critical or user-critical features from behaving differently across Android, iOS, and Web/WASM, reducing regression risk and inconsistent user experiences.

Core Features & Use Cases

Parity workflow execution: Guides you to verify a specific feature/control end-to-end across Android, iOS, and wasm, ensuring identical critical-path behavior.
Implementation and contract alignment: Checks that platform implementations exist and match the core contract expectations, including UniFFI binding alignment via api.udl.
Parity matrix reporting: Produces a clear PASS/PARTIAL/FAIL outcome and identifies remediation needs when divergence is found.

Quick Start

Run the platform-parity-check on a single critical control (for example, Relay ON/OFF) and generate a parity matrix report with PASS, PARTIAL, or FAIL.

Frequently Asked Questions about platform-parity-check

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

FAQPage Schema

How do I verify cross-platform feature parity across Android, iOS, and Web/WASM?▼

Cross-platform feature parity is verified by checking platform implementation presence, comparing against core contracts, validating UniFFI binding alignment via api.udl, and generating a structured matrix with PASS, PARTIAL, or FAIL results for critical messaging controls.

What is platform parity testing for messaging controls and when do I need it?▼

Platform parity testing ensures security-critical messaging controls like relay toggles, identity exchange, and send/receive flows behave identically across Android, iOS, and Web/WASM. It is needed when behavior must match a shared core contract to prevent regression risk and inconsistent user experiences.

How do I check UniFFI binding alignment with an api.udl file for feature regression?▼

UniFFI binding alignment is checked by validating the api.udl file against platform implementations to ensure shared core contract expectations are met. This detects feature regression by confirming Android, iOS, and Web/WASM implementations match the defined bindings.

Does cross-platform testing work for settings alignment and consistent error handling?▼

Cross-platform testing works for settings alignment and consistent error handling by verifying these critical controls end-to-end across Android, iOS, and Web/WASM. It ensures identical critical-path behavior matches the shared core contract.

What's the best way to detect feature divergence across Android, iOS, and Web/WASM?▼

The best way to detect feature divergence is running a parity check that validates platform implementation presence against core contracts and UniFFI bindings. It produces a structured parity matrix identifying PASS, PARTIAL, or FAIL outcomes and remediation needs.