# Claude Code Beyond Coding: Research, Knowledge Bases, Learning > The final Claude Code tips: research instead of Google, a text interface to your computer, GitHub as a knowledge base, and the billion-token rule. Source: https://camnangai.com/en/for/developers/claude-code-tips-beyond-coding Published: 2026-10-24 Claude Code is not only a tool for writing code but a text interface to your whole computer: it researches, cleans up disks, edits video, keeps notes, and the more you use it, the better you understand what it can do. This is part nine, the last in a series that walks through all 50 **Claude Code tips** in YK Sugi's [claude-code-tips](https://github.com/ykdojo/claude-code-tips) repo. It groups six tips that reach beyond code: numbers 25, 29, 47, 20, 42, and 43. The first three cover non-programming work Claude Code does well; the last three cover how you keep getting better. If the whole series had to fit in one sentence, it would be a world-class rock climber's answer when asked how to get better at climbing: "By rock climbing." ## Can Claude Code work as a research tool? Yes, and in many cases it replaces both Google and "deep research" tools, while going further in a few ways. You can use it to investigate why a GitHub Actions run failed, run sentiment or market analysis on Reddit, explore a codebase, or dig through public information to find something specific. It works only as well as the access you give it: the right sources of information, and instructions on how to reach them. That might be the `gh` command in the terminal, the container approach from part seven, Reddit through the `reddit-fetch` skill, internal information through an MCP such as Slack MCP, or simply Cmd+A from part three. If Claude Code struggles to load a page, try Playwright MCP or the Chrome integration from part five. For scientific research, the repo author also built a [paper-search](https://github.com/ykdojo/paper-search) plugin for finding academic papers. The most memorable example is the story of saving $10,000 on a condo purchase. Googling for a realtor turned up nobody good enough, so the author asked Claude Code to find the best realtors in the area, exclude the ones already contacted, keep only those with an email address, and put the list into the clipboard, comma-separated; the whole process ran on voice input. From 15 candidates, filtered through their email replies and a few calls, the author picked one. Months later, that realtor proactively proposed offering 10% under the listing price and negotiated hard, saving $10,000 in the end. Against that month's $100 subscription, that is a 100x return. I like this example because it shows the value sits in narrowing the list, which Google won't do for you. ## Why call Claude Code a universal interface? Because almost any digital problem on your computer can be described to it, and it will figure out an approach. Need a quick video edit? It will work out how with ffmpeg or something similar. Need to transcribe a pile of local audio or video files? It might suggest Whisper through Python. Have data in a CSV? It suggests Python or JavaScript to analyze and chart it. Add internet access through Reddit, GitHub, and MCPs, and the possibilities are close to endless. It is also useful for operating the machine itself. Running out of storage? Ask it for advice on cleaning up: it walks your folders, finds what takes the most space, and suggests what to delete. In the author's case, it was some very large Final Cut Pro files that should have been cleaned up long ago. On your machine it might be unused Docker images and containers (`docker system prune`), or a cache you forgot was still there. "The CLI is the new IDE" still holds in one sense: it is a good place to open a project for quick edits, though serious projects still call for more care with the output than vibe coding allows. The more general point is this: computers started with a text interface, and we are coming back to one, except now you can open three or four tabs at a time. Each tab is like a "second brain" you can hand the boring or tedious work to, not the important things. Digging through GitHub Actions logs is the classic case: nobody wants to do it, and agents turn out to be very good at it. ## How do you use GitHub as a knowledge base? Use GitHub repos, mostly private ones, in place of Notion. Instead of opening a Notion page, you create a new repo or pick an existing private one for your notes. Thoughts get dictated by voice and developed into notes right there, and anything that needs research gets handed to Claude Code, which researches it and updates the repo directly. Repos also hold skills: repetitive work packaged so it can be reused. The missing piece is search. GitHub's search works poorly for private repos: the good code search engine (the one behind github.com/search) is web-only, while the REST API and the `gh` CLI still use the legacy engine, limited to the default branch, files under 384 KB, and repos with activity in the past year, and in practice it can return nothing at all for private repos. The fix is the `private-github-search` skill: shallow-clone (`--depth 1`) every repo locally and search with ripgrep. For 228 repos (161 private), the mirror takes 2.8 GB, and a full-text search takes about 1 second the first time and 11 milliseconds on repeat. Now you can just ask Claude Code "which repo has X?" Repos can also hold practically unlimited data. GitHub rejects files over 100 MB in regular commits, but large files can be attached to a release, up to 2 GB each with no total limit, and anything bigger can be split. Why this makes sense only now: creating, managing, and searching hundreds of repos used to be too much work, and coding agents make all of it far easier. ## What is the best way to get better at Claude Code? Use it. When a world-class rock climber was asked "How do you get better at rock climbing?", she simply said: "By rock climbing." There are supplementary things, of course, like watching videos, reading books, and learning tips (like this series), but using Claude Code is the best way to learn Claude Code, and using AI is the best way to learn AI. The repo proposes a "billion token rule" in place of the 10,000-hour rule: to get good at AI and build a real intuition for how it works, consume a lot of tokens. That is now feasible: since Opus 4.5, models have been powerful enough and affordable enough to run several sessions at once without worrying much about token usage, which frees you up a great deal. I agree with the spirit of it, with one caveat: spend the tokens on purpose. Twenty sessions of real work teach you more than two hundred throwaway prompts, because only real work shows you where Claude breaks. ## Why share what you learn and contribute? Because sharing is not a one-way street. The more you learn, the more you have to share with the people around you, through posts, books, courses, or videos. The repo author also ran an internal session for colleagues at Daft. And every time you share, information comes back: a Reddit post about the difference between slash commands and skills (part eight) brought new lessons in its comments. On contributing, the author has been filing issues on the Claude Code repo with no expectations. Then in version 2.0.67, the team shipped several suggestions from those reports: a fix for the scroll position resetting after deleting a permission rule in `/permissions`, and search inside `/permissions` itself. The team responds to requests surprisingly fast, which makes sense, since they use Claude Code to build Claude Code. ## Where do you keep learning about Claude Code? There are three effective sources. First, ask Claude Code itself: it has a specialized subagent for questions about its own features, from slash commands and settings to hooks and MCP servers. Second, type `/release-notes` to see what is new in your version; it is the best way to keep up with the latest features. Third, learn from the community, for example the r/ClaudeAI subreddit, where users share their workflows. The claude-code-tips repo is a living source too: it gets updated regularly, and the count has grown from the "45+" in its title to 50 tips today. If a tip in this series has gone stale for the version you are running, `/release-notes` and the official docs are the first places to check. ## Which non-coding task should you start with? Pick one boring task on your machine this week, such as cleaning up your disk, transcribing a video, or finding an old note, and hand it to Claude Code instead of doing it yourself. It is the cheapest exercise for starting your own "billion tokens", and for seeing the nine parts of this series come together as one way of working. ## References - [45+ Claude Code Tips: From Basics to Advanced — YK Sugi](https://github.com/ykdojo/claude-code-tips) - [How I saved $10,000 using Claude Code — YK Sugi](https://github.com/ykdojo/claude-code-tips/blob/main/content/how-i-saved-10k-with-claude-code.md) - [Why GitHub is the best knowledge base — YK Sugi](https://github.com/ykdojo/claude-code-tips/blob/main/content/why-github-is-the-best-knowledge-base.md) - [The missing private GitHub search — YK Sugi](https://github.com/ykdojo/claude-code-tips/blob/main/content/the-missing-private-github-search.md) - [How We Use AI Coding Agents — Daft](https://www.daft.ai/blog/how-we-use-ai-coding-agents)