What problem does it solve? When a product ships on multiple client surfaces, changes made in one client often drift out of sync with the others, causing broken API contracts, inconsistent auth flows, and undocumented feature gaps. This Skill enforces a structured protocol to keep the WeChat mini-program, admin portal, server, and shared package aligned. ## Core Features & Use Cases - Cross-Surface Change Protocol: Apply changes in a fixed order — shared types first, then server, then mini-program, then admin — so contracts never diverge. - Parity Gap Auditing: Systematically check auth flows, API conventions, WeChat Pay integration, onboarding nextStep handling, and UI copy consistency across surfaces. - Anti-Pattern Guardrails: Prevents blind component porting between Taro and React, surface-specific DTOs, and accidental targeting of the archived web client. - Use Case: You add a new payment flow to the mini-program. Use this Skill to update the shared API types, extend the server route, expose management controls in the admin portal, and validate both builds. ## Quick Start Ask the AI to audit feature parity between the mini-program and admin portal for the feature you are currently changing.