Day 00

Workshop Readiness Protocol

Moving from a consumer environment to a builder environment.

Your 4-Day Arc

Each day builds on the last. By Friday you will have gone from browser user to deployed app builder.

Day 0 (now)Install your tools. Enter the workshop ready to build.
Day 1 — TueRun AI locally on your own hardware (Ollama, tokenization, context windows).
Day 2 — WedBuild with AI inside your IDE (terminal, AGENTS.md, pair programming).
Day 3 — ThuConnect AI to live data (APIs, Python, the research pipeline).
Day 4 — FriShip a portfolio web app, compete in the Arena, and present at Demo Day.

If this feels overwhelming right now, that is normal. By Day 2 afternoon, the workflow will feel natural. Trust the process.

🎒 The Digital Backpack

Before we begin building, every Space Professional—whether academic, engineer, or operator—needs their tools. We are moving from a consumer environment (Browser) to a builder environment (IDE).

1. The Workbench: VS Code & Python

Metaphor: This is your Lab Bench. It's where you organize your thoughts, your data, and your tools.

2. The Partner: AI Pair Programming

Metaphor: The Lab Partner. You are the Architect; the AI is the Builder.

You will not be coding alone. You will be "Directing" an AI agent inside VS Code using extensions like Gemini Code Assist or GitHub Copilot. In practice: you describe what you want, the AI writes the code, you review and iterate.

3. The Playground: Prompt Engineering

Metaphor: The Wind Tunnel. Test your aerodynamics (prompts) before you build the rocket.

Use low-friction environments for behavior exploration. Whether it is Google AI Studio for raw model access, the Antigravity Playground, or chat interfaces like ChatGPT and Claude, this is where you iterate on logic before committing to code.


🛠️ Setup Checklist

Complete these in order. Steps 01-02 are required before Day 1. Steps 03-06 can be finished during the workshop if needed.