One CLI Command Exposed My Entire Project Architecture

Last week I opened CLAUDE.md , stared at it for 30 seconds, typed "Next.js app with Postgres and Drizzle," and closed the file. That was my entire context file. Three seconds later I asked Claude to add an API endpoint, and it hallucinated an import path that doesn't exist in my project — because "Next.js app with Postgres" tells it almost nothing. The truth is, a useful context file needs your import graph, your database tables, your environment variables, your export catalog — the structural DNA of your project. Nobody writes that by hand. So I built Orbit , a free, open-source CLI that does it automatically, and I ran it on 5 different project archetypes to see what it actually picks up. How It Works Two commands. That's it. npm i -g @orbit-cli/core orbit scan -g Orbit walks your source tree, detects your tech stack, maps the import graph, finds database tables, counts pages and API routes, discovers environment variables, and outputs a structured Markdown file. It supports multiple