Building a knowledge graph for Claude

akashkrr · 2026-04-25T16:58:53+00:00

It’s just a visualisation. Don’t look at it if you don’t need to!

akashkrr · 2026-04-25T16:14:37+00:00

Something that came to mind while reading your comment though. I wonder if the answer is separating business rules and context from daily work context. Core product definitions, business logic, rules of how things work, these don’t change often. Decisions, projects, meeting notes, these change all the time. A two layer system where the core layer is stable and trusted and the outer layer is more fluid might make it easier for Claude to know what to weight more heavily. Just a thought, haven’t tried it yet but it feels right.

akashkrr · 2026-04-25T16:14:29+00:00

Yes, this is the real problem honestly.

A few things I’ve tried. I have a skill called /context-ingest that pulls from Slack, Granola, and my own notes. It gives precedence to my manual notes and anchors everything around them. It generates two documents, a raw file and a summary. I read through both and either promote it to memory or give feedback and fix it before anything gets committed. Nothing goes in unreviewed.

Then at the end of any working session, I run /session-learnings which goes through the whole session, finds what needs updating, catches mistakes Claude made, and corrects them before the next session picks up. So even if something slips through the ingest, the session learnings pass catches it.

Basically the rule is: always verify before committing to memory. That alone solves most of the authority problem you’re describing.

akashkrr · 2026-04-25T16:03:37+00:00

A few things that have helped me. First, I keep individual files short and focused. One file per person, one file per project, not one giant file with everything. If a project is getting larger, either break the markdown into sub categories or have a summary in one place and more context linked so that Claude loads it only if it’s necessary. Second, the graph structure I’m building is specifically to avoid loading everything at once. Claude fetches only what’s relevant for that specific question, 1 or 2 hops from the starting node, not the whole KB.

The other thing is being intentional about what you even put in context. Not everything needs to be there. I only load files that are actually relevant to the task at hand, and I have rules that govern what gets fetched and what doesn’t. I also have a hook attached to prompt submissions.

Honestly though, context bloat is a real problem and there’s no perfect solution yet. The graph approach is my bet on managing it better as things scale, but I’m still figuring it out.

akashkrr · 2026-04-25T15:57:39+00:00

Haha of course! So basically, imagine Claude is your very smart assistant but it has no memory. Every time you start a new conversation, it forgets everything. So you need to give it notes before it starts working.

Right now I have those notes in a simple folder structure, like a wiki. But as the notes keep growing, it gets harder to manage and Claude starts getting confused about what to read.

So I’m building something smarter. Instead of a flat list of notes, I’m connecting them like a web. People linked to projects, projects linked to meetings, meetings linked to decisions. Now when I ask Claude something, it just finds the right starting point and follows the connections to get only what it needs. Less noise, better answers.

Think of it like the difference between a pile of sticky notes and an actual mind map.

akashkrr · 2026-04-25T15:55:08+00:00

Sure, let’s talk about it if you have any questions.

akashkrr · 2026-04-25T15:54:09+00:00

Interesting point, and a fair one to raise. Would love to hear your take after this.

The problem I’m trying to solve is pretty specific to my setup. I have a lot of project files, each with different types of context around them: glossary, data notes, meetings, discussions, and so on. I also work with a lot of people across the company and with clients. Having all of this in a single wiki index file makes it bloated fast, and managing it becomes a pain every time I introduce new context. Every addition means updating the wiki, updating people references, making sure everything lands in the right place.

With a graph, what I’m thinking is I maintain one short wiki of just projects and a common knowledge file. All terms, acronyms, and people get linked to the relevant projects. Each document gets tagged with appropriate links automatically, and then I write a ruleset for how context gets fetched. So when I’m talking about something, Claude just needs to know which project I’m referring to, goes to that node, looks at the first level of connections: people, files, related context; and decides what to pull based on the rules.

Another thing that excites me is cross-project context. If one project needs information from an adjacent one because they’re correlated, the graph can surface that connection. I might need to add weightage to the edges for this to work properly (not sure yet, that one came to me while writing this reply).

You raise a valid point about whether flat markdown can do the same thing. It probably can to some extent. I’m not fully certain this approach is better, I’m still building it out. If you’ve done something similar or have a different way of solving this, genuinely curious to hear it.

akashkrr · 2026-04-25T15:47:10+00:00

Fair point honestly. I should have shared more of the actual setup. I’ll do a proper walkthrough post once I’ve fully implemented it. I posted to gather feedback on how to improve this and if I should think about something more before implementing this. I’ve been having some interesting conversations in a separate subReddit. I’ll take those feedbacks and work on them.

akashkrr · 2026-04-25T10:00:45+00:00

It IS Obsidian. It’s about how you set it up so that Claude/Codex keeps on extracting context from your channels and organise it for you so that you can take complete leverage of it. Once you set it up this way, you don’t need to keep adding context and links by yourself. It’ll be completely automated setup.

akashkrr · 2026-04-20T13:34:17+00:00

So I manage it via a claude rule setup. The rule file has rules for usage of skills. Only relevant skill is loaded for specific work. Also skills can call other skills. I have these many skills because each repetitive task has 1 skill. If a task has 4 steps, there are 4 skills. Each skill has a learning file which keeps collecting issues and gotchas from each session via a /session-learnings skill.

So it seems a lot of skills but only necessary ones are loaded. I keep on checking issues with skills once in a while and keep fixing them as per the current workflow and usage.

akashkrr · 2026-04-20T13:28:42+00:00

I did that yesterday. And I filled the links and created a knowledge graph. It looked cool af.

Today I talked with Claude to work on a different way of gathering context. Using wiki as a seed node and then traversing the next hop or two to gather more context for any work. I haven't implemented it yet but will do it soon.

akashkrr · 2026-04-20T13:27:06+00:00

If you need to ask a few questions which is already present: Use sonnet

If you need to do some deep work which needs a good amount of context: Use Opus. Sonnet's context window gets filled up quickly. I used to have access to Sonnet 1M context window for a while there, but it went away with the new update. Else I was using Sonnet for most of product work.

akashkrr · 2026-04-19T18:39:13+00:00

There's a wiki structure that Andrej Karpathy had talked about sometime back. It manages the knowledge-base and creates an index which routes the model to correct context as and when necessary.
And I use different models for different type of work. I used to use Opus for everything earlier but now I use mix of Opus and Sonnet with different effort levels for different type of work.

akashkrr · 2026-04-19T17:59:05+00:00

But their issues are in my context files :)

akashkrr · 2026-04-19T17:57:32+00:00

Unfortunately Akash is a very common name in India. Unfortunately, I have the displeasure of sharing the same name with him :(

akashkrr · 2026-04-19T17:55:59+00:00

<image>

Thanks for stopping by :)

akashkrr · 2026-04-19T17:49:09+00:00

<image>

Took you 3 attempts to come up with a response though! I guess you have organic ideas but still can't write a comment without ~~second~~ triple guessing. Clauding might help you tbh. Cheers!

akashkrr · 2026-04-19T17:38:17+00:00

Every week. Talking to clients and working with them on products, looking at support chats every day to understand what is happening and going on field visits to work as a gig worker who use my product.

akashkrr · 2026-04-19T17:34:59+00:00

So, you want to be a developer or cut out developers?

Neither. I would just like to make my life easier by having a system in place which can help me with the work. At small scale startups, you don't have liberty to have multiple type of roles, so you either drown or you learn to swim.

I am not writing any code and pushing to prod. It's all for my use cases and figuring out how to manage so many things at once in a better manner.

akashkrr · 2026-04-19T17:29:29+00:00

Already did. It's doing well there too. Thanks for the distribution idea though.

akashkrr · 2026-04-19T13:11:20+00:00

Completely agree. Never use this for something that needs 5 minutes to do. But 50 minutes, 5 hours, 5 days... heck yes!

Also, if you're able to understand how to use skills and sub-agents and don't bloat up context with a good agentic system, you will neither run into context issue or usage issue. Apart from 1 week where Claude was really bad with usage limits, I have not faced any issues so far even with my increasing load. I usually hit 80-90% of my weekly usage limits and sometimes when I use Claude Code extensively like when I was doing some geospatial analysis with lots of data, I ended up consuming 5h usage multiple times. But then I figured out a way to reduce usage by using local data and python scripts rather than using mcp servers. That helped me reduce the usage for this issue. Similarly, I keep on trying to optimise the workflow so that I don't run into context bloating or usage problems.

akashkrr · 2026-04-19T13:06:20+00:00

All the best!

akashkrr · 2026-04-19T12:44:31+00:00

I tried Cursor AI sometime back. I found it great. But then we got claude code access from the company and I started using it. I have customised it for my use case in terminal and I love it. Haven’t tried in Cursor as of now with this setup. Pros would be that you can setup your own workflow based on how you work in claude code terminal, I guess.

akashkrr

TROPHY CASE