FeynmanLM Docs

Appearance

GitHub Repos ​

FeynmanLM can generate flashcards from code repositories — useful for learning a new codebase, internalizing API patterns, understanding architecture decisions, or studying open-source projects.

Starred Repos (GitHub Sign-In) ​

Sign in with your GitHub account in the app to browse your starred repositories directly:

  1. Go to Settings and tap Sign in with GitHub.
  2. Open the Studio tab — your starred repos appear as available sources.
  3. Select a repo and click Generate Flashcards. The app fetches the README and key documentation files automatically.

This is the easiest way to add repos you've already bookmarked on GitHub.

Local Cloned Repos ​

For repos you have cloned on your Mac, you can point FeynmanLM at the local directory:

  1. Clone the repo to your Mac (e.g., ~/Developer/some-project).
  2. In the Studio tab, add the local path as a source.
  3. The app reads documentation files (README, docs/, etc.) from the local clone and generates flashcards.

Local repos are useful when you want to learn from private repositories or when you need the full codebase context (not just what's on GitHub).

Via the MCP (Claude / ChatGPT Integration) ​

If you have the MCP server running and connected to Claude or ChatGPT:

  1. Open a conversation with the AI assistant.
  2. Share repository content (paste code, README sections, or architecture notes).
  3. Ask the assistant to create flashcards: "Create 10 flashcards about the key patterns in this codebase."
  4. The assistant uses the create_flashcards_batch MCP tool to add the cards directly to your knowledge base as proposals.

Organizing Repo Cards ​

Use consistent tags to keep repo content organized:

  • pytorch-internals, react-hooks, kubernetes-api
  • You can create a sub-deck under Articles or a new top-level deck for engineering content

Tips ​

  • Focus on concepts, not syntax. Cards like "What does nn.Module.register_buffer do and when should you use it?" are far more valuable than "What is the syntax for X?"
  • READMEs and CONTRIBUTING files first. These explain the why behind design decisions — much richer source material than source code alone.
  • Changelog and release notes are great sources for "what changed and why" cards.