Problem
What problem this solves
A sync feature can look simple while silently deleting local work, replaying data into the wrong account, syncing sensitive content, or promising reinstall recovery that has not been proven.
Menu Open navigation menu Close navigation menu
Build & Fix Featured
Skill Detail
sg-local-cloud-sync
Design local-to-cloud sync without losing user data.
A data-sync skill for local data promotion, cloud hydration, merge/conflict policy, sync UX states, sensitive-data exclusions, and proof routing.
Outcome
What changes when it works
You get a sync contract that defines data domains, account association, promotion, hydration, merge, conflict, tombstones, offline queue, sync/save UX states, sensitive-data policy, proof route, and docs impact.
Why It Matters
What this changes for a solo founder
Cloud sync is a trust feature. Users forgive missing advanced options more easily than losing work after they create an account.
When to use it
- Before adding accounts or cloud sync to a local-first product
- When local data must be promoted, merged, hydrated, exported, imported, or recovered
- When sync UI needs saved, synced, pending, retrying, blocked, and error states
- When you want a SocialGlowz-style real-time sync guidance overlay after sign-in
- When secrets, clipboard content, private settings, or tenant boundaries are in scope
What you give it
- The project, feature, or data domains that need sync
- Known local stores, cloud stores, auth providers, and account flows
- Any known conflict policy, delete behavior, offline requirement, or sensitive-data class
What you get back
- A local-to-cloud Sync Contract
- A promotion, hydration, merge, conflict, and tombstone decision matrix
- Security and privacy stop conditions
- UX guidance for sync/save state, refresh, retry, and recovery
- A reusable SocialGlowz-inspired sync guidance overlay and local/cloud merge pattern when the product needs real-time post-auth feedback
- Routes to spec/build, onboarding, docs, browser/auth proof, or manual QA when needed
Typical examples
- /sg-local-cloud-sync plan sync for clipboard snippets and settings
- /sg-local-cloud-sync audit whether account creation can preserve local data
- /sg-local-cloud-sync create the sync contract before we promise reinstall recovery
Limits
- It does not replace sg-build for implementation lifecycle
- It does not replace sg-customer for broad activation and setup guidance
- It routes product-access and entitlement-ledger decisions to sg-product-entitlements before final sync contracts
- It blocks unsafe defaults such as silent local wipe, cross-account replay, vague latest-wins, and convenience secret sync
- It does not promise provider-specific sync behavior without fresh official docs and proof
Arguments
Some arguments change the workflow, not just the wording.
These are the argument switches documented for this skill. For the general rule behind skill arguments, read the skill modes tutorial.
project or feature
Creates a Sync Contract for the named local/cloud data surface.
Consequence
Useful before implementation or before writing a ready spec.
audit
Reviews an existing sync plan or implementation for data-loss, account-boundary, conflict, UX, and proof gaps.
Consequence
Useful when sync already exists but trust or correctness is uncertain.
Flutter
Adds Flutter/Riverpod/local-store proof guidance and mobile/web validation order.
Consequence
Useful for Android-first or Flutter Web projects.
secrets / sensitive data
Focuses on default exclusions, privacy, logging, consent, and secure future-spec boundaries.
Consequence
Useful when clipboard content, tokens, credentials, private settings, or regulated data may appear.
sync overlay / SocialGlowz
Uses the reusable SocialGlowz sync guidance overlay and merge pattern.
Consequence
Useful when future apps need a polished post-auth overlay with real-time stages, cloud/local decisions, durable retry, and ready feedback.
Related Skills
See the rest of the loop around this move.
Build & Fix
sg-product-entitlements
Design product entitlement ownership and server-side access gates before premium behavior changes.
A product-entitlement skill for suite and standalone access models, provider events, redemption codes, support diagnostics, backend authorization, and sync handoffs.
Open skill page Build & Fix
sg-build
Run non-trivial work from story to spec, build, verification, closeout, and ship without making the user drive every gate.
The master user-facing lifecycle orchestrator for carrying a story, bug, or goal through ShipGlows's spec, readiness, implementation, verification, onboarding consideration, documentation, closure, and shipping gates.
Open skill page Build & Fix
sg-customer
Turn shipped features into clear, trusted customer journeys.
A customer-experience skill for UX/UI clarity, friction, trust, first-success paths, onboarding, setup sequencing, recoverable states, docs coherence, and proof routing.
Open skill page Operate & Ship
sg-docs
Create or repair documentation so the repo stays navigable for both humans and agents.
A documentation skill for maintaining docs, metadata, and governance-layout compliance across project surfaces.
Open skill page Build & Fix
sg-test
Guide the human through the real user flow, then turn the result into test evidence and actionable bugs.
A manual QA skill for creating guided test campaigns, capturing structured outcomes, and preserving bug history after implementation.
Open skill page Build & Fix
sg-browser
Open a URL in a real browser and verify one observable non-auth objective.
A general browser verification skill for checking public UI, previews, production pages, visible assertions, screenshots, console messages, and network signals without turning every page check into auth debugging or manual QA.
Open skill page Build & Fix
sg-auth-debug
Debug a broken auth flow in a real browser before you start guessing from static code alone.
A browser-level auth diagnosis skill for reproducing login failures, reading local Clerk/Google/Convex/Flutter references, and isolating the exact break point in the flow.
Open skill pageGo Deeper
This public page explains the move. The repository explains the execution contract.
Use the public catalog for education and workflow selection. Move to the docs and GitHub when you want the operator-grade execution details behind the skill system.