DAY 1
Make your account
Sign up for an AI tool you'll actually use. We recommend Claude Pro at claude.ai. If your company already pays for Microsoft Copilot, Gemini, or ChatGPT, start there. Try one prompt today.
YOUR PROGRESS
0 of 30 reps complete
Your streak lives in this browser — that's how we keep this free and frictionless. Switch devices and you start fresh.
FREE · DAILY REPS · NO LOGIN
Atlas 30 · the Field Guide.
A 30-day daily-reps program for AI fluency. Ten minutes a day. Designed for HR leaders, not developers. One simple action per day. Tick the box. Tomorrow you wake up sharper.
Most of the curve is fear. The doing is the cure.
Ten minutes a day is the rep that shrinks the lump and starts the spike. Day 1 takes 10 minutes. By Day 7 you've shipped something real.
Add all 30 days to your calendar
Pick when you'll start and what time of day works for you. Then pick your calendar app. Each rep is a 10-min event with a 5-min reminder.
Day 1 is your start date. The other 29 days fall in line. You can change either picker anytime.
Pick your demo day
One date. The day you'll show one person what you built. A peer, your team, your CHRO, anyone who will witness it. Pick a date. Tell that person you'll show them. The deadline is half the magic.
WORKS IN
Claude RECOMMENDED
Microsoft Copilot
Google Gemini
OpenAI ChatGPT
The honest framing. Days 1-22 work in any AI tool · pick the one your company already pays for. Days 23, 28, 29, 30 use Claude Code (Anthropic-specific) because that's where the builder-path tooling lives today. In Microsoft Copilot, the closest equivalent is Power Automate; in Google Gemini, Apps Script; in ChatGPT, Scheduled Tasks. The reps still apply · just swap the verb.
Atlas 30 · the 30-day reps for AI fluency
© 2026 GLOBAL PEOPLE LABS · MAKING PEOPLE LEADERS THE LEADERS OF AI
The 30-day map
Click any day to jump to the full rep. Or print this whole grid as your wall poster.
Your streak saves automatically on this device. Switch devices and you start fresh — that's the deal. No accounts, no logins, no data collected.
1
Pin this tab
Open this page each weekday. Find today's card. Do the one thing. Tick the box.
2
10 min is the cap
If a rep stretches past 10 min, stop. Habit beats optimization.
3
End with proof
Day 30 = your first scheduled run. Pick a demo day above. Show one person what you built. That moment is the whole point.
0
Warmup · before the cohort starts
DAY 2
Sketch your AI landscape
List 5 AI tools you can use at work. Note what each does best.
DAY 3
Find 3 painful tasks
List 3 HR tasks you do every week that each take 30+ min.
1
Week 1 · install your first Skill
DAY 4
Prompting + context
Write one prompt that gives the AI your role, your audience, and your goal. Notice how the answer changes.
DAY 5
Let AI interview you
Ask your AI tool to interview you · 7-10 short questions about how you work. Save the output as a file called working-style · a Google Doc, a Word doc, or a text file all work. Skills from Day 6 onward will use it as context.
DAY 6
Pick your first Skill
Open the 20 HR Skills Build Kit. Pick the one closest to your weekly work. Read its SKILL.md spec and EXAMPLES. Copy it.
DAY 7
Run it on a real task
Use yesterday's Skill on a real piece of HR work. Screenshot.
DAY 8
Share your win
Show one colleague what worked. One line of context.
DAY 9
Open Door 2 · Cowork
Point Claude Cowork at a real HR folder. Ask one question.
DAY 10
Fill in your roadmap
Open the HR AI Roadmap workbook. Fill in even one row · your first use case, the IMPACT scoring, what to ship first.
2
Week 2 · define how you work
DAY 11
Read the CoS prompt
Open the Chief of Staff Template. Read the 6 sections (Role, Personality, Tools, Briefing, Formatting, Prioritization).
DAY 12
Expand your working-style
Open the working-style file you saved on Day 5. Add depth in 7 sections (role, priorities, decisions, comm style, sharp time, pet peeves, what good work looks like).
DAY 13
Fill first 3 sections
How I write · How I give feedback · How I decide. Real examples.
DAY 14
Fill last 4 sections
1:1s · Make a case · Leaders vs team · Superpower. One page total.
DAY 15
Save your CoS prompt
Save your CoS prompt as a file called chief-of-staff alongside your working-style file. Two files now · both feed your AI partner in Week 3.
DAY 16
Re-read your working-style
Read both files out loud · your working-style notes and your CoS prompt. Make one round of edits. Plus write 3 sentences on what surprised you this week.
DAY 17
Pick your worry
Name the one risk that worries you most about your AI use case (Security, Cost, Accuracy, Learning, Ease). One sentence why. SCALE framework explained →
3
Week 3 · build your Chief of Staff
DAY 18
Connect your inbox
Add Gmail or Outlook to your AI. Ask for three patterns it sees in your last 20 emails.
DAY 19
Make the Project
Open your AI tool's Projects feature (Claude Projects · ChatGPT Projects · Gemini Gems · Copilot Studio). Create a new one. Name it "My Chief of Staff."
DAY 20
Upload your brain
Add your working-style file and CoS prompt to Project knowledge.
DAY 21
Paste the 6-section prompt
Paste CoS instructions. Change [BRACKETS]. Run 1 test query.
DAY 22
3-Pass the weakest output
Ask Claude "Suggest 3 improvements" then "Incorporate them."
DAY 23
Install Claude Code
Install Claude Code. Run /init in a folder you own.
DAY 24
Ship CoS v1
Screenshot your Chief of Staff answering well. Save it. Send it to one person who'd recognize what you just built.
4
Week 4 · ship your first Routine
DAY 25
Audit your week with AI
Paste your calendar and your to-do list. Ask the AI: what should I drop this week? What can I delegate?
DAY 26
Pick your Routine
Pick 1 weekly task. Write what fires and when, in 1 sentence.
DAY 27
Draft routines/my-routine.md
Create routines/ folder. Add your routine file with 5 sections.
DAY 28
Run it manually
In Claude Code: "Run routines/my-routine.md once."
DAY 29
Commit + push
git add . && git commit -m "add routine" && git push.
DAY 30
First scheduled run
Your routine fires automatically. Save the proof. You've crossed from thinking to doing.
Beyond Day 30 · what fluent looks like
Atlas 30 isn't a thing you finish. Day 30 is the start line, not the finish. Four concrete checkpoints to keep you going.
EVERY MONDAY
One new Skill, one killed Routine
15 minutes. Add one Skill. Delete one Routine you stopped using. Keep the stack lean.
DAY 35
Demo day
The day you committed to. Show one person what you built. Tell them what it saves you each week.
DAY 45
Design a second Skill
Pick a different one from the Build Kit. Adapt its SKILL.md to your org. Run it once on real work.
DAY 60
Tighten your Routine
Open the Routine you built. Rewrite the part that has been disappointing you. Run it for a week.
DAY 90
Rebuild your stack
Update CLAUDE.md + working-style.md for who you are now. Three months in, you have changed.
EVERY QUARTER
Teach one person
Walk one colleague through your Chief of Staff. Teaching is the highest form of learning.