76 lines
2.1 KiB
Markdown
76 lines
2.1 KiB
Markdown
# How to Teach Antigravity New Skills
|
|
|
|
To teach me a new skill that persists across different sessions and folders, you can add it to your personal skills library.
|
|
|
|
## 1. Location
|
|
|
|
Skills are stored in your home directory under `.gemini/antigravity/skills`.
|
|
I have just created this directory for you if it didn't exist:
|
|
`/Users/jenstandstad/.gemini/antigravity/skills`
|
|
|
|
## 2. Structure
|
|
|
|
Each skill should be its own folder within the `skills` directory. The folder name should be the skill's identifier (e.g., `react-best-practices` or `python-data-analysis`).
|
|
|
|
Inside the skill folder, you **MUST** include a `SKILL.md` file.
|
|
|
|
Example structure:
|
|
```
|
|
/Users/jenstandstad/.gemini/antigravity/skills/
|
|
└── my-custom-skill/
|
|
├── SKILL.md (Required)
|
|
├── scripts/ (Optional: helper scripts)
|
|
└── templates/ (Optional: code templates)
|
|
```
|
|
|
|
## 3. The `SKILL.md` Format
|
|
|
|
The `SKILL.md` file is the core of the skill. It must start with YAML frontmatter defining its name and description, followed by the markdown instructions.
|
|
|
|
**Template:**
|
|
|
|
```markdown
|
|
---
|
|
name: [Skill Name]
|
|
description: [Short description of what this skill does and when I should use it]
|
|
---
|
|
|
|
# [Skill Name] Instructions
|
|
|
|
[Detailed instructions on how to perform the skill.]
|
|
|
|
## Guidelines
|
|
- Rule 1
|
|
- Rule 2
|
|
|
|
## Examples
|
|
...
|
|
```
|
|
|
|
## 4. How I Use Skills
|
|
|
|
When you ask me to perform a task, I will check your skills library. If a skill's description matches your request, I will read the `SKILL.md` file and follow its instructions.
|
|
|
|
## Example: Creating a "Code Review" Skill
|
|
|
|
1. Create the folder:
|
|
`mkdir -p ~/.gemini/antigravity/skills/code-review`
|
|
|
|
2. Create `~/.gemini/antigravity/skills/code-review/SKILL.md` with:
|
|
|
|
```markdown
|
|
---
|
|
name: Strict Code Review
|
|
description: Guidelines for performing a strict security and style validaton code review.
|
|
---
|
|
|
|
# Strict Code Review
|
|
|
|
When reviewing code, focus on:
|
|
1. **Security**: Check for injection vulnerabilities.
|
|
2. **Performance**: O(n^2) loops are banned.
|
|
3. **Style**: Use 4 spaces for indentation in Python.
|
|
```
|
|
|
|
Now, whenever you ask me to "review this code", I will apply these specific rules.
|