// week 1
Your first 5 missions.
One quest per day. Each one builds on the last and gets you closer to being fully operational. Don't wait until you feel ready — ship the thing, then iterate. That's the culture here.
How to use the starter prompts: Each quest includes a prompt you can paste straight into Claude. Treat it as a launchpad, not a script — fill in the brackets, add your own context, and iterate. The goal is to build the habit of thinking with AI, not copy-pasting outputs.
The quests
01
📅 Book your 1-1s
Google Calendar
Claude
View starter prompt + steps ↓
Starter prompt → Claude
I'm a new joiner at Lana, a green finance startup building financial infrastructure for the energy transition. I'm having a 30-min 1-1 with a teammate this week. Help me draft a short, friendly meeting agenda covering: 1. A brief intro about me: who I am, my background, what I'm excited about 2. Questions to learn about them: their role, what they're working on, top challenges 3. One or two questions specifically relevant to green finance / fintech Keep it conversational — not a formal interview. Under 200 words. [Tip: add the teammate's name and anything you know about their role]
Then in Google Calendar: create a 30-min slot, paste the agenda in the description, add a one-line personal note at the top.
After each chat, debrief with Claude: "I just had a 1-1 with [Name]. Here's what I learned: [notes]. Summarise the key takeaways and suggest one follow-up action."
○ todo
02
📣 Ship your intro to #general
Claude
Slack
View starter prompt + steps ↓
Starter prompt → Claude
Write a short Slack intro message for me to post in #general at Lana. Lana builds financial infrastructure for the global energy transition. About me: - Name: [Your name] - Background: [2–3 sentences about where you've worked or what you've done] - Role at Lana: [Your job title] - Why I joined: [One honest sentence] - One fun or unexpected fact about me: [Something memorable] Tone: warm, genuine, a little personality — not a LinkedIn post. Under 120 words. End with a question for the team to make it two-way.
Iterate: Try "make the opening line more memorable", "cut to 80 words", or "less formal — more like a real Slack message." Don't settle for the first draft.
Post via Slack connector
Use the Slack connector to post this message to the #general channel: [Paste your final intro message here]
○ todo
03
🌍 Green finance crash course
Claude
View starter prompt + steps ↓
Starter prompt → Claude
I'm a new joiner at Lana, a fintech building financial infrastructure for the green energy transition. My background is in [your field]. Generate a mini-syllabus covering: 1. Green finance & sustainable finance — what it is, why it matters 2. Project finance — deal structures, key players, key terms 3. Biofuel projects — types, how they get funded, what makes them risky 4. The financing gap in the energy transition — why it exists and how fintechs like Lana are trying to close it For each topic: explain simply, give one real-world example, and list 2–3 questions I should be able to answer by end of week.
Key terms to get fluent in: SPV · Senior / mezzanine / junior debt · Green bond · Carbon credit · MRV · Blended finance · DSCR · IRR · Off-take agreement · Financial close
Tip: Ask Claude to quiz you: "Give me 5 quick-fire questions on what we just covered." Cements understanding faster than reading.
○ todo
04
🔍 Read the product
Claude
Slack
GitHub
View starter prompt + steps ↓
Slack connector prompt
Use the Slack connector to read all canvases and pinned messages in #product-general. Summarise everything for a new joiner. I need to understand: 1. What is the product and who is it for? 2. What is currently being built? What's in progress vs planned? 3. What stage is the product at? 4. What are the current priorities? 5. What are the open questions the team is working through?
GitHub connector prompt
Use the GitHub connector to look at the lana-app repository. Summarise it for a new joiner: 1. What does this app do at a high level? 2. How is it structured? (key folders, main modules) 3. What tech stack is it built on? 4. What's the most active area of development right now? 5. Any open issues or PRs I should know about?
○ todo
05
🚀 Build & ship your team page
Claude Code
GitHub
Cloudflare Pages
View starter prompt + steps ↓
Starter prompt → Claude Code
I'm adding my card to the Lana internal team directory. The repo is lana-internal on GitHub. There's a file at team/template.html I should copy and fill in. Help me: 1. Clone the repo (walk me through it if I'm new to git) 2. Copy team/template.html to team/[my-name].html 3. Fill it in with my details: - Name: [Your name] - Role: [Your role] - Background: [2–3 sentences] - Fun facts: [3 things] - Why I joined Lana: [1–2 sentences] 4. Add a link to my card in team/index.html 5. Open a pull request on GitHub Explain each git command as you go — I want to understand what I'm doing, not just copy-paste commands.
When it merges: Cloudflare Pages auto-deploys. Your card goes live in under 60 seconds. Post the link in #general.
○ todo
🌿 One last thing: If something in this guide doesn't make sense, ask Claude first. If you're still stuck, ask a teammate. We'd rather you ship something imperfect and learn than wait for everything to be perfect.