Wake up to your own codebase

When you ship faster with agents, the code still has to make sense to you six months later. The failure mode is not using AI—it is losing the habit of knowing where decisions live, which invariants matter, and how a change ripples through the system you actually maintain.

That gap shows up in review threads, incident triage, and onboarding: everyone can move lines quickly, but fewer people can trace behavior from symptom to owner without asking the agent to re-explain the repo from scratch.

codebase-coffee is built for developers who want speed and still need a daily map of their own codebase. It is not an AI coding assistant; it is a short literacy habit tied to the repository open in your editor.

Each session serves one brief—under 100 words—on a single concept in your repo: the pattern, why it exists, where it lives with file references, and one non-obvious gotcha. No headers, no bullet lists, no filler. If you want more, you can say yes to a short walkthrough.

On first run (or after a long gap), the skill scans the repo and writes a personal curriculum to `.codebase-coffee.md` at the project root: ranked concepts, file pointers, and what you have already covered. That file is yours; keep it local if you prefer.

The point is brevity on purpose. A verbose brief is a failed brief. You should finish in the time it takes to read a sharp Slack message, not a documentation chapter.

Install the skill once, then run coffee from whatever repo you are working in. [How it works](/codebase-coffee/how-it-works) walks through the curriculum scan, daily pick, and teammate queue-jump logic.

Setup differs slightly by host. [Install codebase-coffee](/codebase-coffee/install) has copy-paste commands for Cursor, Claude Code, and Codex. In Claude Code, you may get a morning offer automatically; elsewhere you start with `/codebase-coffee` or ask for your daily refresher.

Source, releases, and the skill definition live on GitHub.

Coffee keeps you oriented in the repo you ship from. EraCode gives you deliberate practice: daily and on-demand challenges across coding, quiz, terminal, and multi-part formats, scoped to the technologies you configure.

Together they form a small habit loop: read and remember how your codebase works, then rehearse judgment under light pressure. Neither replaces review or production debugging; both give you reps before those moments cost more.

Read [codebase-coffee and EraCode as one habit loop](/topics/codebase-coffee-and-eracode) for how literacy refreshers and challenge practice complement each other without moralizing about AI.

codebase-coffee is open source and maintained by EraCode. You can inspect the skill, track changes, and install from the repository directly.

If you want the full mechanism before you install, start with [how it works](/codebase-coffee/how-it-works). When you are ready, view the project on GitHub.