1. Prompts#
#gemini
1.1. AI Instructions - Models#
Provide in Markdown. Wrap the entire output—frontmatter and all—inside a single code block using FOUR backticks (````) so that the internal triple-backticks do not break the block. I want one single 'Copy' button for the entire file.
SoundDash - Update these files with new features only if needed.
/Users/marc/Xcode/SoundDash/SoundDash Manuals/Page List.md
/Users/marc/Xcode/SoundDash/SoundDash Manuals/Technical Reference Manual.md
/Users/marc/Obsidian/DashApps/Notes/en/sounddash/Quick Start Guide.md
/Users/marc/Obsidian/DashApps/Notes/en/sounddash/User Manual.md
For the manual, if they have to be modified, start with EN, the translate to FR and ES.
DockDash - Update these files with new features only if needed.
/Users/marc/Xcode/DockDash/DockDash Manuals/Page List.md
/Users/marc/Xcode/SoundDash/SoundDash Manuals/Technical Reference Manual.md.md
/Users/marc/Obsidian/DashApps/Notes/en/dockdash/Quick Start Guide.md
/Users/marc/Obsidian/DashApps/Notes/en/dockdash/User Manual.md
For the manual, if they have to be modified, start with EN, the translate to FR and ES.
GPS
Update /Users/marc/Xcode/GPSDash/GPSDash Manuals/Technical_Reference_Manual.md, /Users/marc/Xcode/GPSDash/GPSDash Manuals/pages_list.md if needed and then, if needed only, update /Users/marc/Obsidian/DashApps/Notes/en/sounddash/Quick Start Guide.md and /Users/marc/Obsidian/DashApps/Notes/en/sounddash/User Manual.md. Start with EN and the translate to ES and FR. Start with EN, then translate to FR and ES
Create an Obsidian note at *** as a project plan, use /Users/marc/Obsidian/Homelab/Notes/Archive/Apple Store Submission Checklist.md as a model, I need sections, checkboxes, numbered tasks using #, ##, ###, ####.
Format the following text into the Proxmox Markdown model below. Wrap the entire output—frontmatter and all—inside a single code block using FOUR backticks (````) so that the internal triple-backticks do not break the block. I want one single 'Copy' button for the entire file.
#Antigravity - Start a new chat
Read the MISSON.md file to bring you up to date. Tell me what you understand from the project. We will do minor corrections during this sessions. Wait for my prompts, do not modify any files now.
#gemini-cli
In /Users/marc/Xcode/GenDash, overwrite codebase.md using a single run_shell_command with a bash loop for maximum speed. Do not use sub-agents. Include ONLY: MISSION.md and these files from the GenDash/ folder: GeneratorProfile.swift, GeneratorRun.swift, HAServer.swift, GeneratorEnums.swift, ConsumptionEngine.swift, EnvironmentalPhysics.swift, HAManager.swift, GenDashApp.swift, BackupManager.swift, OnboardingWizardView.swift, and OperationCostView.swift. For each file, append the following to codebase.md: the string "FILE: " followed by the filename, the string "PATH: "followed by the absolute path, and then the file's content wrapped in a triple-backtick markdown block. Use a case statement in the loop to set the correct language hint (swift or markdown) for each block.
# ANTIGRAVITY TASK: RAG Self-Update (Roadmap) - Gemini 3 Flash
Act as a precise file surgeon following the **Dumb Terminal Protocol**. Your objective is to update the GenDash project roadmap to reflect recently completed work.
**Target File:** `.agent/skills/gendash-roadmap/SKILL.md`
**Update Parameters:**
- **Completed Task/Epic:** [INSERT FINISHED TASK HERE, e.g., Epic 7 Pre-Built Generator Library]
- **Promoted Task/Epic:** [INSERT NEXT TASK HERE, e.g., Epic 6 Trial features]
**Execution Steps:**
1. Read the current contents of the target file.
2. Relocate the **Completed Task** out of the "In Development" section and into the "Completed Features" section. Append today's date to the entry.
3. Relocate the **Promoted Task** into the "In Development" section to set it as the new active priority.
4. Write the updated file to disk immediately. Do NOT modify, summarize, or remove the frontmatter/metadata header at the top of the file.
5. Execute an atomic git commit with the message: `docs(rag): update roadmap skill - mark [INSERT FINISHED TASK HERE] as complete`
6. Output a brief success confirmation.
Do one step at a time, wait for my reply to continue.
# Exit a chat and restore
Summarize our current progress and any pending logic requirements in a single list. Add this to the MISSION.md file
# Replace hardcoded words by keys
Role: Senior iOS Architect
Task: Automated Key-First Migration for `GeneratorProfileForm.swift` and `en.xcloc`.
Objective: Surgically replace literal strings in the Swift code with keys, AND simultaneously update the English localization airlock file.
ACTION 1 (Swift File Surgery):
- Target: `/Users/marc/Xcode/GenDash/GenDash/GeneratorProfileForm.swift`
- Replace every literal English string (in Text() views or String(localized:)) with a descriptive `UPPER_SNAKE_CASE` key.
- Key Format: `GENERATOR_FORM_[ELEMENT]_[PURPOSE]` (e.g., `GENERATOR_FORM_TITLE_EDIT`).
- Handle all matches found in the file.
ACTION 2 (WAIT)
- Wait for marc to execute a build so the keys are populated in /Users/marc/Xcode/GenDash/GenDash Localizations/en.xcloc and /Users/marc/Xcode/GenDash/GenDash Localizations/fr.xcloc
ACTION 3 (Airlock Update):
- Path: `/Users/marc/Xcode/GenDash/GenDash Localizations/en.xcloc/Source Contents/Localizable.xliff`
- For every new key created in Action 1, add a corresponding `<trans-unit>` entry to this XLIFF file.
- The `<source>` must be the technical key (e.g., GENERATOR_FORM_TITLE_EDIT).
- The `<target>` must be the original literal English word/phrase from the code.
- Do the same for Fench
- Path: `/Users/marc/Xcode/GenDash/GenDash Localizations/fr.xcloc/Source Contents/Localizable.xliff`
- The `<source>` must be the technical key (e.g., GENERATOR_FORM_TITLE_EDIT).
- The `<target>` must be the translated literal French word/phrase
STRICT CONSTRAINTS:
1. DO NOT modify the internal `Localizable.xcstrings` file.
2. DO NOT change any UI layout or logic.
3. Provide a "KEY AND TRANSLATION CHEAT SHEET" table below the code so I can verify the mappings.
# Move fron MISSION.md tile to RAG
Act as a precise file surgeon following the Dumb Terminal Protocol. Your objective is to migrate the monolithic `MISSION.md` file into a modular Antigravity Skills (RAG) architecture. Do not summarize or paraphrase the content; use exact text extraction from the source file.
**Step 1: Read Source**
Read the entire contents of the `MISSION.md` file located in the current root directory.
**Step 2: Directory Creation**
Create the following directory structure in the project root. Do not ask for permission, execute the creation:
- `.agent/skills/gendash-conduct/`
- `.agent/skills/gendash-i18n/`
- `.agent/skills/gendash-hardware/`
- `.agent/skills/gendash-roadmap/`
- `.agent/skills/gendash-architecture/`
**Step 3: File Population (Extract & Write)**
Create a `SKILL.md` file within each of the new directories. Populate them by adding the exact YAML/Text frontmatter defined below at the top of each file, followed immediately by the exact text extracted from the corresponding sections of `MISSION.md`.
**A. Conduct Skill**
- **File:** `.agent/skills/gendash-conduct/SKILL.md`
- **Frontmatter to inject:**
```text
---
SKILL_NAME: Rules of Conduct
STATUS: Static
PRIORITY: Critical
---
- Content to extract: Extract the entirely of “Section 7. Development Rituals & Workflow” EXCEPT for the Localization/Airlock parts. Ensure the rules for “Dumb Terminal Protocol”, “Atomic Commits”, “No Emojis”, and “Data Sanitization” are included here.
B. i18n Protocol Skill
