What problem does it solve? Changing the Guardian server contract (gRPC proto, HTTP JSON payloads, status enums, auth requirements) without updating every downstream consumer leads to broken clients, mismatched semantics between Rust and TypeScript SDKs, and stale documentation. This Skill enforces a server-first propagation workflow so contract changes stay consistent across the entire repository. ## Core Features & Use Cases - Server-first workflow: Classifies the change as gRPC-only, HTTP-only, or shared behavior, then updates guardian.proto or the HTTP/service modules before touching any client. - Cross-stack propagation: Guides updates through the Rust client, TypeScript client (server-types.ts, conversion.ts, http.ts), both multisig SDKs, examples, and docs. - Guardrails and validation: Flags high-risk changes (auth, proposal status, JSON optionality), forbids permissive parsing fallbacks, and defines a minimum test set (cargo test -p guardian-server, cargo test -p guardian-client, guardian-client npm tests) with expansion rules. - Use Case: You add a field to a proposal response in guardian.proto. The Skill walks you through updating the Rust client mappings, TypeScript conversion layer, multisig SDK proposal handling, example harnesses, and the matching spec/docs, then reports every surface touched. ## Quick Start Use the guardian-contract-change skill to propagate my change to guardian.proto across the server, both clients, the multisig SDKs, examples, and docs.