1 vue rules available
One Gemini rule matches vue: a Vue 3 developer rule with the Composition API and TypeScript. The GEMINI.md section can live in a GEMINI.md inside src/ to keep it out of backend folders. GEMINI.md has no glob scoping, so the section names the files it applies to; a GEMINI.md inside a subfolder is the way to limit it to that folder.
Gemini CLI loads instructional context from GEMINI.md files: a global ~/.gemini/GEMINI.md, files in your workspace directories and their parents, and files discovered in subfolders as the agent works. The file name is configurable, so a project can tell Gemini CLI to read AGENTS.md instead of, or alongside, GEMINI.md. The rules in this directory are written as plain system instructions, so the same text can also be used as a system instruction in Gemini API or Google AI Studio requests.
GEMINI.mdStarting point, not a tested configuration for your repository. GEMINI.md has no file-scoping front matter; add this as a section, or place a GEMINI.md in the relevant subfolder. Review the instructions, adapt the file paths and run your project's existing checks.
## Vue.js development
Applies to: **/*.vue, src/composables/**/*.ts, src/stores/**/*.ts
# Vue.js instructions for Gemini CLI
## Focus for this project
- Convert components only when asked; otherwise follow the API style already in the file.
- Keep emitted event names and prop names unchanged during a conversion.
- Report vue-tsc results after the change.
## Vue.js conventions
- Use <script setup lang="ts"> with type-based defineProps<{ ... }>() and defineEmits for new components; keep the Options API only in files that already use it.
- Use computed for derived values and watch only for side effects.
- Put shared logic in composables named useXxx under src/composables.
- Do not mutate props; emit an event or use defineModel for two-way binding.
## Before you finish
- Run npx vue-tsc --noEmit, the lint script and the unit tests (for example Vitest) and report the actual output. If you cannot run them, say so and list the exact commands instead of saying they pass.
- Summarize which of the rules above affected the change.
- If shell commands are not approved in this session, stop after the edit and list the exact commands for the user to run.
Create your own Gemini rules for Vue.js and share with the community.
Ask for a small change to one matching file. Check the tool's loaded context or instruction view, inspect the diff for the requested convention, and run the relevant build or test. A well-formatted file does not guarantee the model follows every instruction.
The Gemini CLI documentation states that Gemini CLI was replaced by Antigravity CLI on June 18, 2026 for unpaid-tier and Google One users. Check which CLI your account uses; Antigravity rules are covered on the Antigravity page. Gemini CLI does not need a separate AGENTS.md mechanism: its context file name is configurable through context.fileName in settings.json (the docs show ["AGENTS.md", "CONTEXT.md", "GEMINI.md"]). Without that setting it looks for GEMINI.md.
Documentation checked 2026-11-05: Gemini CLI docs: GEMINI.md context filesGemini CLI docs: System prompt override
Illustrative input and expected result. This example is a verification guide, not a recorded model run.
You use Gemini CLI to convert an Options API component and want <script setup> with typed props.
Convert src/components/UserCard.vue from the Options API to <script setup lang="ts">.
A <script setup lang="ts"> version with defineProps<...>() and defineEmits, identical props and events, computed values preserved, and vue-tsc results or the command to run.
Content reviewed 2026-11-05. Confirm instruction activation in your installed client before relying on it.