liveBook · Manning

Feature menu

As explained in Crack Any Codebase with AI

A feature menu is an organized view of an API surface that groups endpoints by user-facing product features.

A feature menu turns a flat API inventory into a product-oriented map: a few named groups, each with a description and its endpoints. It replaces alphabetical file listings with the features users recognize, making a large surface easier to comprehend. section 8.3

Build the menu by:

  • Reading route definitions as a product menu rather than a file listing. section 8.3
  • Grouping endpoints by the feature a user would name. section 8.3
  • Sorting groups largest first so the biggest product investments appear first. section 8.3
  • Tagging each endpoint as public, available to signed-in users, or restricted to admins. section 8.3

When to use one

Cal.com's 295 endpoints are too numerous to hold in one mental model, so a feature menu can organize them into a guided tour. A small CLI or ten-function library usually needs no menu because its help output or public exports are already visible at once. section 8.3

How Crack Any Codebase with AI covers it

How deep it goes
Groups every endpoint, describes features, orders groups, and tags callers, while stopping short of implementation analysis.
Examples
Uses Cal.com's 295 endpoints and an online-shop structure spanning Catalog, Cart, Checkout, and Account.
What it assumes
Assumes crawled route or endpoint definitions and teaches product-oriented grouping instead of alphabetical file inspection.
What you can do after
Apply it via an LLM to organize a complete route inventory into a feature menu and guided tour.
How it connects
Connects API endpoints with product features, guided tours, route definitions, access control, and README interpretation.

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Crack Any Codebase with AI. The section links point to the parts of the book it draws on.