platform-parity

Audit cross-platform drift between web and desktop implementations in a Foundry monorepo.

Updated Apr 10, 2026
One-click install
npx skills add https://github.com/qdhenry/Foundry-OSS --skill platform-parity
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: platform-parity
Source: https://github.com/qdhenry/Foundry-OSS/tree/main/.agents/skills/platform-parity
Command: npx skills add https://github.com/qdhenry/Foundry-OSS --skill platform-parity

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Cross-platform parity drift between web and desktop implementations in a Foundry monorepo can cause feature drift, inconsistent UX, and wasted effort. This Skill helps teams audit and enforce alignment across apps/web and apps/desktop, ensuring shared packages are used consistently.

Core Features & Use Cases

  • Drift audits across web and desktop to detect identical components, similar functionality, and opportunities for extraction into shared packages.
  • Layer placement checks to ensure code resides in the correct layer (apps, packages) and adheres to project conventions.
  • Abstraction seams validation to enforce proper interfaces and adapters between UI and backend components.
  • Parallel implementation detection to surface duplication and guide consolidation.
  • Schema readiness checks to ensure Convex schemas and runtime considerations are aligned for cross-platform execution.

Quick Start

Run a full parity audit on a pull request that touches both web and desktop code paths to surface drift, layer violations, and seam issues.

Frequently Asked Questions about platform-parity

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

FAQPage Schema
How do I audit cross-platform drift between web and desktop apps in a monorepo?

Cross-platform drift audits identify identical components and similar functionality across apps/web and apps/desktop, quantifying inconsistencies and surfacing opportunities to consolidate code into shared packages.

How do I validate layer placement to ensure monorepo code resides in the correct apps or packages directories?

Layer placement validation checks that code resides in the correct layer, verifying that apps and packages adhere to project conventions to prevent structural violations and maintain architectural integrity.

What is the best way to detect parallel implementations and duplicated logic in a Foundry monorepo?

Parallel implementation detection surfaces duplicated logic and similar functionality across web and desktop apps, guiding consolidation efforts by highlighting abstraction seams and opportunities for extraction.

How do I verify abstraction seams between UI and backend components in a multi-platform repository?

Abstraction seam verification enforces proper interfaces and adapters between UI and backend components, ensuring cross-platform implementations maintain consistent boundaries and interact through validated contracts.

Can I check Convex schema readiness for cross-platform execution across web and desktop apps?

Schema readiness checks ensure Convex schemas and runtime considerations are aligned for cross-platform execution, verifying that web and desktop implementations share consistent data structures.

Does this parity audit work with shared packages in a Foundry monorepo?

Parity audits work directly with shared packages in a Foundry monorepo, detecting drift in shared package usage and validating that apps/web and apps/desktop consume them consistently.