liveBook · Manning

Repository

As explained in Vibe Engineering

A repository is a version-controlled project store containing source code, configuration, and recorded change history.

In AI-assisted development, repository structure is part of the context agents need to work reliably. Project-level instructions and source access can make an agent competent within one project, yet leave it without the system context needed across services and teams. section 10.0

Repository structure creates practical tradeoffs for agent navigation:

  • A monorepo can expose more code, but visibility alone does not make the code easy to navigate. section 10.0
  • Without topology and dependency information, agents may find files but miss how they connect to the larger system. section 10.2
  • Wrong turns consume tokens and reviewer attention; repeated navigation failures turn infrastructure gaps into team costs. section 10.2

The wrong checkout package

An agent infers that checkout-v2-experiment is the active implementation from commit dates, overlooking stable production code in packages/checkout. The mistake is an information failure: the repository gives the agent no clear way to distinguish active code from abandoned experiments. section 10.2

How Vibe Engineering covers it

How deep it goes
Traces navigation failures to missing topology and their token and review costs, without detailing a specific repository redesign.
Examples
Contrasts abandoned checkout-v2-experiment with stable production code in packages/checkout.
What you can do after
Diagnose agent navigation mistakes as information problems rather than reasoning failures.
How it connects
Connects repository structure to context engineering, monorepos, and dependency graphs.

Also explained in

Compare how 14 books explain repository →

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Vibe Engineering. The section links point to the parts of the book it draws on.