Antigravity Kit

1What it does

A starter-kit repository for Antigravity — a curated bundle of rules files, skill packages and configuration templates arranged so a new user gets a working customization layer in one install rather than assembling pieces repo by repo. The kit's shape is the point: instead of choosing between the v5 guardrail pack, a skills vault and an MCP config template, the kit picks a coherent subset of each and wires them into a single layout you drop onto a project. It targets the cold-start problem — the first hour of Antigravity customization where the ecosystem's breadth is a liability — by making opinionated choices (which rules matter most, which skills are broadly useful, what a sane MCP config looks like) so the initial setup is a review of defaults rather than a research project.

2When to use it

Reach for it on day one — a fresh Antigravity setup on a real project benefits more from a working baseline than from the optimal set discovered over weeks. It fits developers who want to start with guardrails on and pare back, rather than start empty and add. Also useful as a template for a team-standard kit: fork it, swap the bundled pieces for your team's picks, and the layout becomes the distribution format. Skip it once you've built your own customization layer — the kit's value is the starting point; at steady state your own curated files are the better defaults.

3How to get started

Clone the repository and read the layout before copying anything — the kit separates rules, skills and config into the directories Antigravity actually discovers (.agent/rules/, .agents/skills/), so installation is copying the folders you want into your project root. Start with the full bundle on a scratch project, run a few real tasks, and note which rules or skills get in your way — then prune. The README documents what each bundled piece does; treat pruning as the second step of installation, not an optional extra.

4Configuration

Configuration is subtraction: the kit arrives opinionated, and the right tuning is removing the pieces that don't match your stack — a Python skill pack on a Rust project is dead context. Keep the kit as a fork or a pinned checkout rather than copying files loose into the repo; that preserves the upgrade path when upstream refreshes the bundle. Rules and skills from the kit behave like any discovered files — workspace-level copies override or supplement global ones per Antigravity's standard precedence, so install at the scope you actually want.

5Things to know

• Opinionated by design — the bundled selections are the maintainer's judgment call; treat them as reviewed defaults, not canonical choices.
• Kit-shaped distribution ages fast — bundled rules and skills can lag their upstream sources; check whether the kit tracks upstream or froze at adoption time.
• Good for teaching — a single repo showing how the three customization surfaces fit together is the clearest onboarding artifact the ecosystem has.
• MIT-licensed; forking into a team template is the expected use for org-wide rollouts.
• The bundle makes a decent reference even uninstalled — reading which pieces the maintainer chose and why is a crash course in what a working customization layer looks like.
• For teams, the kit answers "what do we standardize on" with a concrete artifact instead of a policy document — fork it, diff against it, and the standard writes itself.
• Maintenance model is worth checking — kits track their upstream sources loosely; a bundled rule may lag its origin repo, so spot-check against the source before treating the kit as current.
• As a day-one artifact it beats a blank canvas — a baseline you can measure your own tweaks against is how a personal ruleset gets built without guessing.

6Related on the map

References

• Repository
• Antigravity customization docs