gsync is a repo-native context system for coding agents.
V1 is intentionally small:
- a reusable steady-state
GSYNCskill - a reusable
gsync-onboardingskill - a minimal
.gsync/config.jsoncontract - project-local docs that tell agents how this repo uses
gsync
The old Firebase prototype is preserved in legacy/firebase-prototype.
skills/
gsync/
gsync-onboarding/
legacy/
firebase-prototype/
Use skills/gsync/SKILL.md when a repo already has .gsync/ and the agent needs to work within it.
Use skills/gsync-onboarding/SKILL.md when a repo needs .gsync/ initialized or extended with new collections.
The onboarding skill should be sufficient on its own. The intended setup path is:
- install or load
gsync-onboarding - let the agent explain
gsyncbriefly - let the agent draft
.gsync/config.json,.gsync/GSYNC.md, and collection docs - hand off future operation to
GSYNC
V1 keeps one hard machine-readable contract:
{
"version": 1,
"collections": {
"activity": {
"path": ".gsync/data/activity",
"doc": ".gsync/data/activity/activity.md"
}
}
}Everything else is project-local and should be documented in:
.gsync/GSYNC.md- each collection's configured doc file
The rewrite source of truth is V1_REWRITE_SPEC.md.