coco-research / coco-research/coco
[GFI] Add Antigravity (Google) adapter
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 251
- Forks
- 12
- Avg merge
- 7d 6h
- Merged PRs (30d)
- 80
Description
Goal
Add an antigravity IDE adapter so Coco artifacts install into Google's Antigravity editor. The README's System Compatibility table lists Antigravity as Planned for v0.2 — this issue tracks building it.
Files involved
adapters/antigravity/manifest.json(new) — mirror an existing adapter's manifestadapters/antigravity/install.sh(new) — link/compile skills, commands, agents, rules into Antigravity's config locationadapters/antigravity/README.md(new)install.sh—detect_adapter()may add an Antigravity heuristic
Reference
adapters/cursor/ and adapters/vscode-continue/ are the closest patterns. The generic adapter (AGENTS.md producer) is a good fallback model if Antigravity supports AGENTS.md.
Acceptance criteria
-
bash install.sh --adapter antigravityinstalls without error - Skills, commands, agents, and rules are wired into the correct Antigravity location
-
manifest.jsonvalidates; README documents the target paths - CI passes (frontmatter linter, manifest validator, install script syntax check)
- README System Compatibility row updated from "Planned" to "Beta/Stable"
Hints
- Adding an adapter:
CONTRIBUTING.md - Frontmatter spec:
docs/architecture.md
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with adapters/cursor/, adapters/vscode-continue/, and the generic adapter, then read CONTRIBUTING.md and docs/architecture.md. Add adapters/antigravity/manifest.json, install.sh, and README.md, update the root install.sh detection and README compatibility row, and run the documented CI checks plus bash install.sh --adapter antigravity. Done means the manifest validates, installation succeeds, all artifact types are wired to documented Antigravity paths, and CI passes.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- shell
- Domain
- developer-experience, tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100