lg-init

Liquid Galaxy Project Initializer

First step in the pipeline: Init -> Brainstorm -> Plan -> Execute -> Review -> Quiz (Finale).

⚠️ PROMINENT GUARDRAIL: The Critical Advisor (.agent/skills/lg-critical-advisor/SKILL.md) and LG Shield (.agent/skills/lg-shield/SKILL.md) are always active. If the student rushes or can't explain the LG architecture, STOP and invoke the Critical Advisor.

---

Contest: 3-Repository Workflow

This starter kit supports the Gemini Summer of Code 2026 — Agentic Programming Contest structure:

Repository	Purpose	Who Owns It
LGFlutterStarterKit	Template + .agent/ agent system	Contest organizer / team
Student's Demo App (e.g., LG-Task2-Demo)	The actual LG Flutter app	Student's GitHub account
Agent System (.agent/ inside StarterKit)	Skills, rules, workflows that power Antigravity	Submitted as part of StarterKit

The student's generated app is deliverable #2. It must be in its own repo, buildable, and demonstrate LG control.

---

CRITICAL: Separate Directory Rule

The new app MUST be created as a sibling directory inside the Antigravity workspace, NOT inside LGFlutterStarterKit.

The starter kit is a template/reference — it stays untouched. The new app gets its own directory and its own Git repo, but BOTH live inside the same workspace so the student can see them side-by-side in their IDE.

~/.gemini/antigravity/scratch/            ← ANTIGRAVITY WORKSPACE ROOT
├── LGFlutterStarterKit/                  ← THIS STAYS UNTOUCHED (template)
│   ├── .agent/                            ← Agent skills, rules, workflows
│   ├── flutter_client/                    ← Reference implementation
│   └── ...
└── LG-Task2-Demo/                        ← NEW APP GOES HERE (separate repo)
    ├── flutter_client/
    ├── docs/
    ├── .github/
    ├── README.md
    └── ...

After creating the app directory, add it to the IDE workspace so the student sees both repos in the file explorer.

---

CRITICAL: LG App Naming Convention

All generated apps MUST follow this naming pattern:

LG-<TaskName>

Examples:

• LG-Task2-Demo — For the basic Task 2 deliverable
• LG-Earthquake-Viz — For an earthquake visualizer
• LG-Satellite-Tracker — For a satellite tracking app
• LG-Historic-Tours — For a historical exploration app

Rules:

1. Always prefix with LG- — identifies it as a Liquid Galaxy app
2. Use PascalCase after the prefix (no underscores, no spaces)
3. Be descriptive — the name should tell you what the app does
4. NOT acceptable: my_app, flutter_test, earthquake_app, lg_demo
5. The Flutter package name in pubspec.yaml should be snake_case: lg_task2_demo

---

Phase 0: Repository Setup

⛔ WITHIN-PHASE INTERACTION RULES

DO NOT silently create the project directory and all files. Explain WHAT you're about to create and WHY before doing it. Pause after each significant step for student acknowledgment.

Step 1: Explain and Confirm Project Location

First, explain to the student what will happen:

"I'm going to create your LG app as a sibling directory next to the starter kit — inside the same Antigravity workspace. Both repos will be visible in your IDE side-by-side. Here's the layout:"

# The Antigravity workspace root
WORKSPACE_ROOT=$(dirname "$STARTER_KIT")   # ~/.gemini/antigravity/scratch/

# The starter kit location
STARTER_KIT=$(pwd)   # e.g., ~/.gemini/antigravity/scratch/LGFlutterStarterKit

# New app goes as a SIBLING inside the same workspace
APP_NAME="LG-Task2-Demo"   # Must follow LG-<TaskName> convention
APP_DIR="$WORKSPACE_ROOT/$APP_NAME"

Tell the student the exact path:

"Your new project will live at: ~/.gemini/antigravity/scratch/LG-Task2-Demo/" "The starter kit stays untouched at: ~/.gemini/antigravity/scratch/LGFlutterStarterKit/" "Both will be visible in your IDE workspace."

Ask: "This means your app code and the mentor's skills live side-by-side. Does this workspace layout make sense? Any questions about why we keep them separate but within reach?"

⛔ STOP and WAIT for the student's response.

Step 2: Create the New App Directory

mkdir -p "$APP_DIR"
cd "$APP_DIR"

Tell the student:

"📂 Created directory: ~/.gemini/antigravity/scratch/LG-Task2-Demo/" "To navigate here yourself: cd ~/.gemini/antigravity/scratch/LG-Task2-Demo"

Step 3: Copy Starter Kit Scaffolding

Explain what's being copied:

"I'm copying the Flutter client template, docs structure, GitHub workflows, and server as a starting point. I'll walk you through the structure after."

# Copy the Flutter client as a starting point
cp -r "$STARTER_KIT/flutter_client" "$APP_DIR/flutter_client"

# Copy docs structure
mkdir -p docs/plans docs/reviews docs/aimentor docs/screenshots docs/recordings docs/gifs

# Copy workflow files for CI/CD
cp -r "$STARTER_KIT/.github" "$APP_DIR/.github"

# Copy .gitignore
cp "$STARTER_KIT/.gitignore" "$APP_DIR/.gitignore"

# Copy node_server if needed
cp -r "$STARTER_KIT/server" "$APP_DIR/server" 2>/dev/null || true

# Create fresh README and DEVELOPMENT_LOG
touch README.md DEVELOPMENT_LOG.md

After copying, show the student exactly what was created with full paths:

📁 Files created:
  ✅ ~/.gemini/antigravity/scratch/LG-Task2-Demo/flutter_client/  (Flutter app template)
  ✅ ~/.gemini/antigravity/scratch/LG-Task2-Demo/server/          (Node.js backend)
  ✅ ~/.gemini/antigravity/scratch/LG-Task2-Demo/docs/plans/      (Design & plan docs)
  ✅ ~/.gemini/antigravity/scratch/LG-Task2-Demo/docs/screenshots/ (Demo evidence)
  ✅ ~/.gemini/antigravity/scratch/LG-Task2-Demo/.github/          (CI/CD workflows)
  ✅ ~/.gemini/antigravity/scratch/LG-Task2-Demo/README.md
  ✅ ~/.gemini/antigravity/scratch/LG-Task2-Demo/DEVELOPMENT_LOG.md

"Here's what we just created. flutter_client/ is your main app code, docs/ is where plans and reviews go, server/ is the Node.js backend. Each folder has a specific purpose."

Ask: "Can you guess which folder your SSH service code will go in? Which folder will your screen widgets live in?"

⛔ STOP and WAIT for the student's answer. This confirms they understand the project structure.

Step 4: Initialize Git

cd "$APP_DIR"
git init
git add .
git commit -m "init: project scaffolding from LGFlutterStarterKit"

Tell the student:

"💻 Terminal command: cd ~/.gemini/antigravity/scratch/LG-Task2-Demo && git init && git add . && git commit -m 'init: project scaffolding from LGFlutterStarterKit'" "Git repo initialized with your first commit. To check status: cd ~/.gemini/antigravity/scratch/LG-Task2-Demo && git log --oneline"

Step 5: Add to IDE Workspace

CRITICAL: Make both repos visible in the IDE.

"I'm adding your new app to the current workspace so you can see both repos in the file explorer:" "📂 Workspace now contains:" " 1. LGFlutterStarterKit/ — The template + agent skills" " 2. LG-Task2-Demo/ — Your app (this is where we'll work)"

If using VS Code, add the folder to the workspace. If using another IDE, tell the student how to open both directories.

Step 6: Create GitHub Repo

Hand off to .agent/skills/lg-github-agent/SKILL.md to:

1. Create a new GitHub repo with the app name
2. Set origin remote
3. Push initial commit
4. Set up branch protection and templates

Tell the student the GitHub URL:

"GitHub repo created: https://github.com/<username>/LG-Task2-Demo" "To push manually: cd ~/.gemini/antigravity/scratch/LG-Task2-Demo && git push -u origin main"

---

Phase 1: Requirement Gathering

Ask the student these questions ONE AT A TIME. Wait for each answer before asking the next.

1. Project Name: "What should we name this app? It must follow the LG-<TaskName> convention. For Task 2, I'd recommend LG-Task2-Demo. For a custom project, describe what it visualizes."

2. LG Rig Config: "How many screens does your target LG rig have? (3 is the default for Task 2)"

3. App Type: "What kind of LG app are you building?"

   • Task 2 Demo: Minimum features (logo, pyramid, flyTo, clean) — contest requirement
   • Data Visualization: Live data on Google Earth (earthquakes, weather, satellites)
   • Educational: Guided tours, historical explorations, information balloons
   • Controller: Rig management dashboard

4. Platforms: Android (primary — required for release APK), plus optionally iOS, Linux, macOS.

5. External APIs: USGS, NASA, OpenWeather, custom, or none (Task 2 = none).

6. Tooling confirm: flutter analyze, flutter test, dart format.

---

Phase 1.5: Logo & Asset Guidance

After requirements, recommend visual assets:

"Every LG app needs a logo for the ScreenOverlay on the slave screen and an app icon. I recommend using the Nano Banana Asset Master to generate these. Here's what we need:"

Asset	Purpose	Spec
App Logo	ScreenOverlay on left slave screen	1024×512 PNG, transparent background
Placemark Icon	Custom marker for data points	512×512 PNG, transparent background
App Icon	Android launcher icon	1024×1024, follows Android adaptive icon spec

For Task 2: The logo is sent to the left slave screen (screen 3 in a 3-screen rig) as a <ScreenOverlay> KML element. It should include the project name and optionally the LG logo.

Generation: Use .agent/skills/lg-nanobanana-sprite/SKILL.md — it provides prompts with green-screen background removal for clean transparent PNGs.

Reference: See how Lucia handles the logo overlay in LG Master Web App.

---

Phase 2: Scaffolding

First, explain the layered architecture:

*"Your Flutter app uses a layered architecture

---

Content truncated.