1. Prompts#
#gemini
1.1. AI Instructions - Models#
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.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/Antigravity/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.# gemini-cli - Approve Plan
This is the proposed Antigravity implementation plan. Comment, no full prompt, comments and new directives only. Add your comments in a markdown block so I can copy and paste.# Prompt for Antigravity
Prepare a prompt for Antigravity, specify the model and mode to use. Prioritize Gemini Flash or Gemini 3.1 Pro (LOW) when possible. Use markdown. Wrap the entire output—front-matter 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.
Available models:
Gemini 3.1 Pro (High)
Gemini 3.1 Pro (Low)
Gemini 3 Flash
Claude Sonnet 4.6 (Thinking)
Claude Opus 4.6 (Thinking)
GPT-OSS 120B (Medium)
Can we use Gemini 3 Flash for this one?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/Antigravity/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/Antigravity/GenDash/GenDash Localizations/en.xcloc and /Users/marc/Antigravity/GenDash/GenDash Localizations/fr.xcloc
ACTION 3 (Airlock Update):
- Path: `/Users/marc/Antigravity/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/Antigravity/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
- File:
.agent/skills/gendash-i18n/SKILL.md - Frontmatter to inject:
--- SKILL_NAME: Airlock Protocol TRIGGERS: "localization", "translation", "fr.xcloc", "en.xcloc", "LBL_" --- - Content to extract: Extract the “i18n Protocol (The Airlock)” bullet point from Section 7, and the entire “Standard Feature Localization Workflow (Modern)” block (Stages 1 through 4).
C. Hardware & Physics Engine Skill
- File:
.agent/skills/gendash-hardware/SKILL.md - Frontmatter to inject:
--- SKILL_NAME: Hardware Profiles & Physics Engine TRIGGERS: "Hardware Profile", "Physics", "Propane Manifold", "Inverter", "Traditional", "Fuel", "TTE", "Load" --- - Content to extract: Extract Section 1 (Project Objective) and Section 3C (Fleet & Hardware Profiles).
D. Project Roadmap Skill
- File:
.agent/skills/gendash-roadmap/SKILL.md - Frontmatter to inject:
--- SKILL_NAME: Project Roadmap TRIGGERS: "priority", "roadmap", "Epic", "status", "next steps" --- - Content to extract: Extract Section 4 (In Development), Section 5 (Future Roadmap), Section 6 (Completed Features), and Section 8 (Completed & Archived Tasks).
E. Technical Architecture Skill
- File:
.agent/skills/gendash-architecture/SKILL.md - Frontmatter to inject:
--- SKILL_NAME: Technical Stack & UI TRIGGERS: "SwiftUI", "SwiftData", "ActivityKit", "Dashboard", "White Card", "Widget" --- - Content to extract: Extract Section 2 (Technical Stack) and Section 3 (Architecture Notes A, B, and D).
Step 4: Verification & Commit
- Read the newly created
.agent/skills/directory tree to verify all 5 folders andSKILL.mdfiles exist. - Inform the user that all files and folders were create, wait for his approval to continue
- Once you got the approval, Execute an atomic git commit with the message:
build: refactor MISSION.md into modular Antigravity skills architecture. - Output a success confirmation listing the created files. Do not delete the original
MISSION.mdfile; leave it intact for my manual review.
Press Cmd + Shift + F in Xcode.
Click the search icon (magnifying glass) and change it to Regular Expression.
Paste this: Text\("[^A-Z_]+"\)
This will highlight any Text view that contains lowercase letters, ignoring your UPPER_SNAKE_CASE keys.
## 2. AI Project State Transfer Protocol
Use this 4-step guide to freeze the state of your current session and "thaw" it perfectly in a new one.
---
### 2.1. The "Audit & Summary" Request
Before closing your current chat, issue this command to the AI. This forces the model to consolidate its internal memory into a portable text format.
**Command to AI:**
> "Summarize our progress in this session. Provide a bulleted list of:
> 1. **Completed Tasks:** Every feature or logic block finalized.
> 2. **Pending Requirements:** What was mid-build or planned next.
> 3. **Critical Logic Rules:** Specific constraints we established (e.g., specific variable names, safety overrides, or 'Stop = Pause' protocols).
> 4. **Known Technical Debt:** Any bugs we deferred or architectural 'hacks' the new AI should know about."
---
### 2.2. Update the "Source of Truth" (MISSION.md)
Always maintain a single file in your project (e.g., `MISSION.md` or `README_AI.md`) that acts as the "Constitution" for the project.
**Command to AI:**
```text
Update the `MISSION.md file to reflect our progress today. Ensure it includes:
- The **Current Version/Build** number.
- The **Project Vision** (What are we building and for whom?).
- The **Tech Stack** (Languages, Frameworks, Database).
- **Architecture Notes** (How data flows between components).
- **Active Constraints** (Specific rules like 'No Emojis' or 'Full Scripts Only').2.3. The Code/Document Snapshot#
Ensure your local environment (Xcode, VS Code, or Text Editor) has the absolute latest version of all files.
Pro Tip: If you aren’t sure if the AI has “drifted,” ask:
Provide a list of all files modified in this chat and verify their current version against our logic. Save these locally before we transition.2.4. The “Cold Start” Initialization Prompt#
When you open the New Chat, do not just start talking. Use a structured Initialization Prompt to feed the AI the “DNA” of your project.
Template for the New Chat (First Message):
Objective: Resume work on [PROJECT NAME].
1. Context Injection:
- [Briefly describe the project goals].
- Read the attached
MISSION.md[or paste summary here] for core logic and security rules.2. Current Baseline:
- We have already implemented [Feature A] and [Feature B].
- Current Version: [V1.X].
- Location/Testing Context: [e.g., Knowlton, QC / Simulator Info].
3. Immediate Goal:
- Our next task is [Describe the very next step].
4. Behavioral Constraints (Persistent Rules):
- Always provide full scripts for modified files.
- Use LaTeX for all formal math/science formulas.
- Maintain a [Tone Preference, e.g., Professional/Witty] persona.
- Wait for my input or output before providing additional steps or fixes.
5. Audit Request:
- Review the project structure and confirm you understand the ‘Session Stitching’ and ‘Refuel’ logic before we proceed.
2.5. Final Checklist for User#
- Is the local code compiled and working?
- Did the AI confirm the “Pending Tasks” list?
- Is the new Initialization Prompt ready to paste?
- Close the old chat tab. (Keeping it open creates a temptation to go back, which leads to fragmented logic).
# New instuctions
"We are continuing work on the GenDash project.
1. Read `MISSION.md` for the core logic and security rules and take a look at the snapshots at .snapshots/2026-04-07/
2. Use the Xcode bridge to scan the current project structure.
3. We have already implemented the basic UI and the `ConsumptionEngine`.