Start here
DevPulse is a small tracker: you type what you worked on and for how long, and it shows your day, your week and your streak. We build it with Claude Code, one chapter at a time.
Each chapter starts with a problem we hit while building. Then we find the Claude Code feature that solves it, and use it at once. Each chapter has a video, the episode with the same number, and a page here with every command to type. Start with Chapter 0.
Every prompt in one place: all the prompts and commands, ready to copy, chapter by chapter.
The chapters
Install Claude Code, sign in, and check it works. Watch Episode 0 (3:15)
Start Claude Code in a folder, ask for a page, stop it with Esc, point at a file with @. Watch Episode 1 (3:53)
Permission modes, plan mode, and the three answers to a permission prompt.
/init, CLAUDE.md, auto memory, /memory and /context.
Rewind and where it stops, git through Claude, and the commit-commands plugin.
Tests that catch a timezone bug, the Learning style, and /verify.
/usage, /model, /effort, /context, /compact, /btw and /clear.
The / menu, /simplify, and a /standup skill of our own in .claude/skills.
claude -p without a chat, --allowedTools, and a standup script that runs by itself.
Subagents: Explore, then a code-reviewer of our own, and a fix with a test.
MCP: Playwright lets Claude see the page at phone width; server scopes.
A plugin builds a DevPulse MCP server, so Claude logs and sums tasks directly.
A dynamic workflow: four reviewers at once, one ranked list, and what it costs.
Hooks: a check after every edit to tasks.json, and a beep when Claude waits.
A public page from the public tasks only, the repo on GitHub, and GitHub Pages.
VS Code, the desktop app and claude.ai/code, and when to use which.
The code
The finished DevPulse is public on GitHub, with a tag for each chapter, so you can start any chapter from the right point: github.com/Aditya-402/devpulse. Its public page is live at aditya-402.github.io/devpulse.