local-cloud-sync-audit

Audit ZINC Fusion V16 local-cloud Supabase wiring without starting local services.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/zincdigitalofmiami/zinc-fusion-v16 --skill local-cloud-sync-audit
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: local-cloud-sync-audit
Source: https://github.com/zincdigitalofmiami/zinc-fusion-v16/tree/main/.kilo/skills/local-cloud-sync-audit
Command: npx skills add https://github.com/zincdigitalofmiami/zinc-fusion-v16 --skill local-cloud-sync-audit

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Systematic audit and fix workflow for ZINC Fusion V16 local/cloud Supabase wiring. This skill is for the boundary between local compute and cloud canonical state, not generic app coding.

Core Features & Use Cases

  • Loop-driven audits including pre-flight, environment, connection-path, drift/migration, Vault/pg_cron, and a change-plan with an approval gate to ensure cloud-only posture without local deployments.
  • Explicit guardrails: the skill never starts local Supabase or Docker and enforces non-destructive cloud-state checks.

Quick Start

Run the end-to-end audit workflow to validate local-cloud Supabase wiring and cloud-canonical posture without starting local Supabase.

Frequently Asked Questions about local-cloud-sync-audit

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

FAQPage Schema
How do I audit local-cloud Supabase sync drift without starting Docker?

The audit enforces cloud-only posture by running non-destructive Vault and pg_cron validation checks, ensuring proper separation between local compute and cloud canonical state without deploying local containers.

What is cloud-canonical posture in a local-cloud Supabase wiring audit?

Cloud-canonical posture ensures the cloud database remains the single source of truth by enforcing guardrails that prevent local deployments from altering canonical state during pre-flight and connection-path checks.

How do I validate Supabase Vault and pg_cron configurations for cloud posture?

Run the dedicated Vault and pg_cron validation audit loop to verify configurations non-destructively, ensuring approved-change planning meets cloud-only posture requirements without starting local Supabase instances.

Can I run a pre-flight environment loop for Supabase migrations without local deployments?

Yes, the audit workflow runs pre-flight environment loops and drift reviews that validate Supabase migrations without local deployments, enforcing strict separation between local compute and cloud canonical state.

What are the limitations of running a non-destructive local-cloud audit?

The primary limitation is that the audit never starts local Supabase or Docker, meaning it cannot execute live integration tests; it only provides non-destructive recommendations and approved-change planning for cloud-only posture.