Writing Work About Newsletter Login
Module 6, Lesson 6: Writing the Base Authentication

Module 6, Lesson 6: Writing the Base Authentication

14 min read min

Before We Start

From previous lessons:

  • You completed your first issue, merged it to main, and pushed it to your remote. Module 6, Lesson 5
  • You know the pattern by now: pick up an issue, ask Claude Code to review and ask clarifying questions, answer as the product owner, review the plan, let it implement, test, commit. Module 6, Lesson 5
  • Your Clerk account exists and you've referenced it in a previous story. Module 6, Lesson 5

Tools / setup you'll need:

  • WebStorm, with your backend (API) and mobile frontend modules open
  • Claude Code, with your YouTrack MCP connection active
  • Your emulator, up and running
  • A Clerk account with an application provisioned, or ready to provision one
  • Your .env.local files for both API and mobile, ready to receive Clerk keys

By the end of this lesson, you'll:

  • Have finished the issue you left running, merged it, and cleared your context for a new batch of work
  • Have picked up a group of related issues at once instead of one at a time
  • Have provisioned Clerk, wired up your keys, and corrected your Clerk dashboard settings to match your spec
  • Have watched Claude Code drive your emulator directly against a live Clerk instance and a live database, catch a real bug, and fix it
  • Have tested Google SSO yourself, hit a real regression, reported it clearly, and watched Claude Code debug it with you in real time
  • Have a working sign up, sign in, and sign out flow with Google SSO, ready for the next lesson

About This Lesson

Duration: ~32 minutes video
Skill Level: Intermediate
What You'll Build: A working authentication flow, email OTP through Clerk, Google and Apple SSO, and sign out, driven end to end by Claude Code and verified by you in the emulator.

This lesson picks up right where the last one left off. We close out the issue we already had running, then move into a bigger chunk of work: three related issues, tackled together instead of one at a time. This is the first time in the course you'll see me batch issues, and it's also the first time you'll see Claude Code actually drive the emulator itself, not just write code and hope it works.

There's also a real bug in here. Not a staged one. I want you to see what it looks like when something breaks after you thought it was fixed, and how you report that back to Claude Code so it can actually find the problem.

Paid members

This content is for Paid Members

Unlock full access to Dele Tosh and see the entire library of members-only content.

Subscribe