Sign in to your dashboard, the curriculum, and everyone building alongside you.
Five weekdays, seven lessons, mostly one a day. Each takes somewhere between fifteen minutes and an hour, and each ends with a plain check you make yourself: either the thing works on your machine or it doesn't yet. No quizzes, nobody grading you.
The shape of the week: Monday you get set up, turn on code together with the group, pick your project, and write a spec sheet with Claude. Tuesday Claude Code turns that spec into a skeleton, a real file you open. Wednesday the core starts working, with your real material in it. Thursday you finish version one, using your spec as the checklist. Friday you change it three times and show it. Every day starts from the spec you wrote Monday, so nothing later in the week arrives cold.
Everything runs in the Claude desktop app. There is nothing to install beyond that one app, and there is no command line anywhere in this week. If you have been putting this off because you assumed it starts with a scary black window, it doesn't.
You build your own project. Everyone in the group follows the same rhythm, spec then skeleton then core then finish, and what moves through that rhythm is yours. Because the rhythm is shared, the moment someone else gets stuck and unstuck, the answer helps you too.
Miss a day and you are not behind. The days stack, so if Wednesday gets away from you, do it Thursday and keep going. What matters is that the seven lessons are checked off by the end of Friday.
Before Monday, two things. First, a Claude account on a paid plan, because the desktop app needs it to work with files on your computer. Second, come with an idea for something small you want to build.
What counts as small: one page or one little tool that does one job, with a result you can see on your screen. A tracker for something you count, a calculator you keep redoing by hand, a page that turns your rough notes into something readable. If it needs accounts, logins, or an app store, it's a version two, not a this-week.
If you get stuck, say so in Slack. Post in #claude-code-sprint with what you asked for and what happened instead. We read it all week and will get you unstuck.
Joining the kickoff: we start live at 2:00pm ET on Monday July 27 using Go Live, which runs inside our Slack. A card posts in the #claude-code-sprint channel with the Google Meet link on it. RSVP on that card to put the session on your calendar, then join from the same card when it starts. Nothing gets emailed, so keep an eye on #claude-code-sprint.
spec.md is saved in your project folder.