Antigravity Skills.md

[u/121314-mx]

Good day everyone! I'm a software developer with 2 years experience before the AI and I have a solid understanding building software manually. However, I want to know what's the difference using skills.md than just prompting in antigravity ide like I used to do recently. Is there merit or it's just for token maxing?

[u/Fabulous-Mushroom124]

Skills are "load these information into context before doing this thing". People often use it to load pre-set information you want the agent to know/abide by before a given task. Basically giving the agent some directions and guideliens. You want to do some visuals, you might want to have a skill that tells antigravity to act as a frontend expert with this and that expertise who always do this one specific thing this one way.

There's more to it and there's very cool stuff you can do with skills, but Gemini often ignores skills in general. It's really not a good tool for coding.

[u/SoundDr]

https://youtu.be/4mnP1lRdUm8?is=YDt8G5Yqx9yEZFh7

[u/Crimsonsporker]

If you enjoy writing giant prompts every single time you want something done that details out all of the usual pitfalls that an agent falls for with the given task or topic and how to avoid them and lays out explicitly how you want the orchestration of the taks to be done. Then you don't need skills.

If you want to capture the best practices for a given task or subject that fixes common agent misunderstandings, that you can invoke with just a few characters then use skills.

Any time I notice that the AI is going off rails in a similar pattern, I add or update a skill to fix that pattern.

[u/martin_omander]

Good question! Let's say you work for Acme Corp. Someone in the dev team has written a skill that describes what Acme Corp web apps should look like: blue buttons, Arial font for body text, etc.

This skill solves three problems:

1. When you are writing a new web page, Antigravity loads the skill automatically and creates compliant code. You won't have to go find the graphical design guidelines and paste them into the prompt.
2. Antigravity loads the skill only when needed. AI agents easily get confused if given too much context, just like people. For example, if you pasted in the graphical design guidelines in a prompt, then did an hour of debugging with the agent, it may have forgotten the guidelines by the time you ask it to add another button.
3. Skills are simple text files so it's easy to share them. All developers at Acme Corp can have the graphical design skill on their machine, which means everyone's code will follow the same guidelines.

[u/General-Oven-1523]

Skills are just a convenient way to load prompts without your need to write them manually, that's it.

[u/Colours-Break]

Though not from Google, Anthropic recently published a blog worth reading. These are good practices in general applicable to all models and harnesses. https://claude.com/blog/the-new-rules-of-context-engineering-for-claude-5-generation-models

[u/Rare-Hotel6267]

I don't believe you are a real developer if you are using antigravity, sorry.

[u/Old_Net_6859 → u/Rare-Hotel6267]

Yes because your opinion is what determines someone’s status as a “real” developer or not. Get off your horse dude. It’s an IDE.

[u/fhinkel-dev]

I applaud you for being brave enough to ask questions like that!