Carry — a local-first knowledge tool by Tonk. Contribute to tonk-labs/carry development by creating an account on GitHub.
Road to Tonk Substrate — Tonk
We're building a living, malleable software environment that allows you to shape, own, and share your digital world without asking anyone's permission.
LLM Knowledge Bases
A visual breakdown of Andrej Karpathy's approach to building personal knowledge bases powered by LLMs. Learn the 4-phase pipeline: ingest, compile, query, and maintain - with an interactive architecture diagram.
Notion on Twitter / X
New: Use skills with local agents!Keep your skills in Notion as your source of truth, then download them to Claude Code, Codex, Cursor, Gemini, or Grok.You’ll get a SKILL.md plus any approved files. So you can use your skills wherever you work. pic.twitter.com/jeEHZfHdQA— Notion (@NotionHQ) August 21, 2026
Atlassian's DESIGN.md is here: what we learned testing portable design context in practice - Inside Atlassian
We tested Google's DESIGN.md format against our MCP server and AI skills to see where a single portable markdown file fits in your design system tooling. Here's what we learned.
10 Easy Ways to Enhance Your LLM Wiki or Knowledge Base
Karpathy's LLM Wiki: What It Means & How to Build One
Karpathy's LLM Knowledge Base Wiki for Enterprise | Vijoy Pandey posted on the topic | LinkedIn
There's a new kind of computer media in the enterprise: Write once, Read never. The docs are perpetually stale, constantly diverging from reality, and scattered across Confluence, SharePoint, GitHub, Webex (or Slack) threads, Notion, Obsidian - and in my personal life, add Apple Notes, Goodnotes, web clippings, and multiple Google Drives worth of docs and slides that nobody is ever going back to. Karpathy tweeted his LLM knowledge base wiki architecture which went viral last weekend and I decided to give it a run yesterday. Verdict: You *have* to try this out. Prediction: You won’t be able to live without it soon. There were a few mods and decisions I made to the base Karpathy provided. First, the vault / folder structure in Obsidian. I already use Obsidian as a human. Instead of creating separate vaults and dealing with the sync nightmare, I just have folders for Human and Agent, and a Raw folder. (1) The Human/ folder is where I write long form articles and notes independent of the knowledge base wiki. No LLM or agent touches this folder. (2) I do have Arnold Layne, my OpenClaw agent, doing background tasks for me. Raw/ is where both Arnold and I, dump raw snippets. Inclusive of diverse kinds of media. (3) The Agent/ folder is where the LLM (Claude in my case) synthesizes the wiki. No human touches this folder. Second, some customizations to CLAUDE.md for enterprise-like usage - (4) Domain extensions - the agent needs to know that quantum computing and agentic AI have different entity types and different provenance thresholds. (5) Primary source protection, when I drop in my own original work, secondary sources can extend it or raise questions against it, but they cannot overwrite it. It sounds like a small thing but its’s not, especially at enterprise scale where provenance actually matters. Karpathy is upfront that what he’s built is working memory for a single agent, and it’s truly remarkable at that. The jump to Shared Context across teams, reconciling conflicting beliefs at org scale, ontologies that don’t collapse under the weight of a hundred contributors - those are much harder problems and what we are exploring with the Internet of Cognition. PS: The screenshot shows my Obsidian vault after just two runs: one with Karpathy’s original tweet and gist file itself (so meta!) and one with our Internet of Cognition paper. Claude (Sonnet) read it, compiled it into structured summaries, entity pages, concept pages, backlinks, merged all the information cohesively, and keeps it all maintained from there. You just read the Wiki. It’s simply magical.
How to Build an LLM Knowledge Base
A hands-on guide to building a simple LLM knowledge base with raw markdown sources, a compiled wiki, reusable prompts, and an agent that keeps improving the knowledge base over time.
skills/openverse/SKILL.md at main · toosean/skills
the skills i wrote. Contribute to toosean/skills development by creating an account on GitHub.
GitHub - MrLesk/Backlog.md: Backlog.md - A tool for managing project collaboration between humans and AI Agents in a git ecosystem
Backlog.md - A tool for managing project collaboration between humans and AI Agents in a git ecosystem - MrLesk/Backlog.md
ua-extensions/patterns/core-vs-extension.md at main · ua-community/ua-extensions
Contribute to ua-community/ua-extensions development by creating an account on GitHub.