How Do New Developers Onboard Faster with AI?

Why Is Codebase Onboarding So Slow for New Developers?

Onboarding to a large, established codebase is one of the most frustrating experiences in software engineering. You're expected to contribute quickly, but the repository has years of history, undocumented conventions, and architectural decisions that only make sense if you were there when they were made.

Traditionally, new developers spend their first week or two reading code, asking questions when they can find a free senior engineer, and hoping their mental model is roughly correct before submitting their first PR.

Priscila Andre's Comprehend-First AI Coding Skill replaces this painful ramp-up with a structured, repeatable process. Instead of passively reading code, you actively interrogate it using AI as your always-available senior engineer.

How Do You Use Catch Me Up on Your First Day?

Start by creating a prompt using the Catch Me Up format:

1. Declare your role: "I am a new contributor to this repository. I have no prior context."

2. Select exploration modes: Begin with Architecture (to understand overall structure) and Convention (to learn coding standards).

3. Ask a specific question: "How is this repository structured, and what are the key naming conventions and lint rules I should follow?"

4. Request visual output: "Show me a component tree and a table of the main modules with their responsibilities."

The AI produces a structured summary you can internalize in minutes rather than days. But critically, you don't stop there—you verify. Ask follow-up questions: "Does module X actually communicate with module Y, or is there an intermediary?" This verification step is where real understanding is built.

What Exploration Modes Matter Most for Onboarding?

For your first few days, focus on three modes:

- Architecture: Gives you the structural overview—what components exist, how they relate, and where boundaries are.

- Convention: Reveals the coding standards, lint rules, and naming patterns you must follow. This prevents your first PR from being rejected for style violations.

- Testing: Shows you how tests are structured, what they actually simulate vs. intercept, and where you should add tests for your contributions.

Once you have these three foundations, use Feature mode to understand the specific area you'll be working in, and Trace mode to follow the execution path of the feature you're about to modify.

How Do You Know When You're Ready to Write Code?

Apply the comprehension gate from the Research → Comprehend → Plan → Implement workflow. Ask yourself: Can I explain, in plain language, what this code does and why? If yes, move to planning. If no, run another round of Catch Me Up with a more targeted question.

The goal is not to understand the entire codebase—it's to understand enough about the area you're working in to produce what Priscila Andre calls keynote code: intentional, well-understood contributions you'd be proud to present publicly.

Don't fall into the trap of skipping comprehension because you feel pressure to ship. Slop code—code shipped without understanding—creates more work for your team and undermines your credibility as a new contributor.

What Should You Do Next?

Create a Catch Me Up Markdown template and save it in your dotfiles or project root. Every time you encounter an unfamiliar part of the codebase, invoke it with the appropriate exploration mode. Within your first week, you'll have a structured, verified mental model that would normally take a month to build through passive code reading. Start with Architecture mode today.