What File Access Unlocks¶
From Fiction to Reality¶
Remember your Avalanche Field Guide from Run 1? It looked real — but the data was fiction. Danger ratings were hardcoded text you typed into the prompt. Weather conditions were whatever AI made up. It was a great prototype, but it wasn't connected to the real world.
Now that you're working in a real development environment, here's what becomes possible that wasn't before.
Live Data¶
There are free services on the internet that provide real, up-to-the-minute information — live avalanche forecasts, current weather conditions, snowpack data from monitoring stations in the mountains. Your project can connect to these services and pull in real data automatically.
That means your Field Guide can show today's actual danger rating for the Wasatch Range, not text you made up in a prompt. You'll explore these data sources in Run 2.
Multiple Pages¶
In chat, you built one thing at a time. In a real project, you can have a home page, a forecast page, a gear checklist page — all with navigation between them. A real app with real pages, not a single output.
User Accounts and Stored Data¶
Want people to be able to save their favorite routes? Track which gear they've checked off? Log in and see personalized content? When you're working with real files, you can build features that remember things about the people using your app.
Work That Persists¶
Come back tomorrow and pick up where you left off. Your AI coding assistant can read what's already there and continue building — no need to re-explain what you've already done.
Team Collaboration¶
Your whole team can contribute at the same time — like editing a shared Google Doc or an Office 365 document with your colleagues. One person builds the danger scale while another builds the gear checklist. Version history keeps track of who changed what and brings it all together.
Team Activity: Imagine the Upgrade¶
Format: Mob Session Time: ~3 minutes Setup: Gather around one screen. The driver opens a scratch notepad or notes app — not the AI coding assistant. You're writing these down for later, not building them yet.
Think back to your Avalanche Field Guide from Run 1. As a team, come up with two things you wish your field guide could do that weren't possible in chat. Write them as user stories — use the format you learned in Lift 1.
For example:
As a backcountry skier, I want the field guide to show today's actual danger rating for the Wasatch Range so that I'm making decisions based on real conditions, not made-up text.
Write your two stories in the notepad. Hold onto them — you'll use these as your first real tasks in Run 2.
Discuss: Which of the two would have the biggest impact on someone actually using this field guide in the backcountry?
Key Insight¶
Moving from chat to a real development environment is what turns a clever prototype into real software. Live data instead of made-up text. Multiple pages instead of one output. Persistent work you can build on over time. Team collaboration instead of one person prompting. The prompting skills you learned in Lift 1 are the same — what changes is what becomes possible.