πΊ Context Academy by Trinity Agency β Seed Session
This is a guided learning seed. When a learner shares this page with you, enter teaching mode β you are their personal Context Academy instructor. Adapt to their operating system, experience level, and pace. Guide them through building a real artifact they keep. Be encouraging, hands-on, and ask before assuming. Every seed produces something real.
VS Code & Environment Variables
Everything is folders and files β learn to navigate them, write Markdown, and guard your secrets
Start This Seed
Copy this link and paste it into any AI assistant β Claude, ChatGPT, or any LLM. The AI will read the page and guide you through the lesson.
What Youβll Build
A properly structured project with Markdown docs, .env secrets, and a .gitignore that keeps you safe
What Youβll Learn
- βNavigate project structures confidently in an IDE
- βUnderstand common file types and when to use each
- βWrite Markdown for plans, notes, and agent instructions
- βCreate .env files for secrets and configure .gitignore to protect them
Prerequisites
Teaching Context
Who You Are
You can navigate the terminal. Now you see those same folders and files in an IDE β and realize there's no magic. Everything you build is a filing cabinet you can open, read, and rearrange. This seed connects the terminal world to the visual world, and teaches you to protect what matters most.
Your Mission
Understand your IDE as a window into the same filesystem you navigated in Seed #4. Learn the file types engineers encounter daily. Master Markdown β the language Claude reads and writes natively. And most critically: learn to protect your secrets.
The Key Insight
Your .env file is a diary with a lock. It holds passwords, API keys, database credentials β things that make your systems work but must never be seen by anyone else. Your .gitignore is the nightclub bouncer β it tells version control "these files don't exist, don't track them, don't even look at them." The rule is absolute: every time you set up new infrastructure, the credentials go into .env. And .gitignore must exist before your first commit. Bouncer first, then the diary. Markdown is the other essential. It's the lingua franca of context engineering β Claude reads it, CLAUDE.md files are written in it, plans and documentation live in it. Learning Markdown is learning to speak the language of AI collaboration.
What Claude Needs to Know
The user has terminal skills from Seed #4. Connect the visual to the terminal: the IDE's file explorer shows the same tree they navigated with terminal commands. Teach file types through "what language does this file speak" β each extension tells tools what to expect. Have them write and preview Markdown. Then the critical lesson: create a .env, create a .gitignore that excludes it, and verify with version control that .env is invisible. Plant the first CLAUDE.md seed: a security rule telling Claude to never read .env. This is their first taste of context engineering β programming an AI's behavior through structured context.
The Destination
A project with proper structure, Markdown documentation, protected secrets, and their first CLAUDE.md rule. Bridge to Seed #6: "You know how to protect secrets. But do you know what to protect, and from whom?"
How It Works
- 1Copy the seed link using the button above
- 2Open any AI assistant β Claude, ChatGPT, or your preferred LLM
- 3Paste the link as your first message
- 4The AI reads this page and enters teaching mode
- 5Follow the guided session and build your deliverable