What problem does it solve? Keeping Modal serverless functions and their Python client in sync across two repositories is error-prone: registry entries get missed, generated clients drift, and secrets become unmanaged. This Skill enforces a single source-of-truth workflow so Modal functions are implemented, registered, deployed, and consumed consistently. ## Core Features & Use Cases - Guided Modal implementation: Add or update functions under src/functions/, register them in src/registry.py, and wire them into src/deploy.py with validation via tools/validate_registry.py. - Generated client sync: Run scripts/local/sync_win_modal_client.sh to regenerate services/modal/client_generated.py in the win repo, with drift checking via check_win_modal_client_drift.sh. - Secret management checklist: Use the manifest-based flow (modal_secrets_manifest.json plus the local canonical secret store) so stable runtime secrets stay managed instead of drifting. - Use Case: A user says "Implement this pipeline in Modal" — the Skill walks through implementing the function, registering it, syncing the generated client into win, updating tests, and verifying CI deploy. ## Quick Start Use the modal-function-sync skill to implement a new Modal function in modal_functions and sync the generated client into win.
