Project Name
Vault template
First committed by asakin
Published in asakin/llm-context-base. Publisher page
74 GitHub stars
What it is
A git template for building your own LLM-powered personal wiki. Training period, metadata standard, lint system included. Clone and go.
AutoGineer overview, from the brain’s own files
llm-context-base is an opinionated template designed to turn a local git repository into an LLM-powered personal wiki. It implements a three-layer pattern consisting of raw source documents, an LLM-maintained wiki, and a schema configuration. The system is designed to adapt to a user's workflow over time, eliminating the need for upfront taxonomy design. It includes a metadata standard for queryable files, an inbox-first capture system with a 7-day TTL, and a linting system to maintain document health. It supports various AI tools including Claude Code, Cursor, and GitHub Copilot, providing a consistent interface for managing personal knowledge.
How it works
Memory model: LLM wiki
AutoGineer overview, from the brain’s own files
The system uses a specific folder structure including 1-Projects, 2-Knowledge, 3-Journal, and 4-Private, alongside configuration and metadata folders. Users capture information into an _inbox folder, which the AI then processes and files according to a metadata standard. The system is bootstrapped via configuration files in .claude, .cursor, and .github, which direct the AI to follow instructions located in _config and _meta. It uses a training period to learn user patterns and maintains documentation through a split README file that separates user-specific content from framework documentation.
| Folder | Role | Files |
|---|---|---|
| .claude | agent-config | 2 |
| .cursor | agent-config | 1 |
| .github | agent-config | 1 |
| .obsidian | obsidian-config | 7 |
| assets | attachments | 2 |
| docs | docs | 13 |
| examples | examples | 4 |
| 1-Projects | folder | 3 |
| 2-Knowledge | folder | 5 |
| 3-Journal | folder | 1 |
| 4-Private | folder | 1 |
| _config | folder | 4 |
| _inbox | folder | 1 |
| _meta | folder | 14 |
| _output | folder | 1 |
| _sources | folder | 2 |
The agent reads
- CONTRIBUTING.md evidence: .claude/CLAUDE.md
- _config/config.md evidence: README.md
The agent writes
- _config/config.md evidence: .claude/CLAUDE.md
- _config/context.md evidence: .claude/CLAUDE.md
- _inbox/ evidence: .claude/CLAUDE.md
- _output/ evidence: README.md
Requirements
Apps: Obsidian
Databases: MongoDB, PostgreSQL
Works with: Claude Code, GitHub Copilot, Cursor, Devin (ex-Windsurf)
Set it up
- Download the brain as a ZIP and unzip it where you keep your notes or project: https://mp-staging.autogineer.com/agent-brains/asakin/llm-context-base/download
In Obsidian, choose “Open folder as vault” and pick the folder.
Claude Code reads .claude/CLAUDE.md from this folder automatically.
cd llm-context-base && claude
AutoGineer scanned these files at commit 3c096ca.
First committed by asakin. Published in asakin/llm-context-base. Licence: Apache License 2.0.
Usage
AutoGineer overview, from the brain’s own files
- Capture unstructured notes into the inbox for later organization by the AI.
- Maintain decision records with context, options, and rationale.
- Query the wiki to synthesize information across multiple documents.
- Run linting commands to identify stale files or missing metadata.
- Manage project initiatives with briefs and timeline tracking.
- Generate reports or summaries from stored knowledge.
- “Capture this: here's how our onboarding process works...”
- Creates a file in the inbox and offers to file it in the appropriate location.
- “We decided to use PostgreSQL over MongoDB, let me document why”
- Generates a decision record with context, options, rationale, and an outcome section.
- “What do we know about our hiring process?”
- Scans file summaries and synthesizes an answer with source citations.
- “Lint the wiki”
- Surfaces stale files, missing metadata, and orphaned documents.
Documentation by asakin
[Project Name]
This README will be personalized during your first session.
<!-- llm-context-base:framework-readme -->
llm-context-base
An opinionated template for building your own LLM Wiki.
Use the template, point your AI assistant at it, and start talking. Over time, it learns how you work and adapts its structure to your needs without you having to design anything upfront.
How This Relates to Karpathy's LLM Wiki
Andrej Karpathy's LLM Wiki gist describes a three-layer pattern: raw source documents → an LLM-maintained wiki → a schema config file (like CLAUDE.md or AGENTS.md). The LLM reads sources, maintains structured wiki pages, and follows the schema config to stay consistent.
llm-context-base implements this pattern as a ready-to-use template — so you don't have to build it from scratch. What it adds on top of the base pattern:
Metadata standard — every file gets a queryable header (type, summary, tags, status, date). The LLM scans these instead of loading full files, which scales cleanly to hundreds of documents.
Inbox-first capture — a frictionless landing zone with a 7-day TTL. You capture without deciding where things go. The LLM files them later.
Training period — the system starts chatty (learning your patterns) and goes quiet as it adapts. You never design a taxonomy upfront.
Lint system — surfaces stale files, missing metadata, and orphaned docs on demand.
Multi-LLM support — bootstrap shims for Claude Code, Cursor, Copilot, Windsurf, and others. One config, any tool.
Full comparison with the Karpathy pattern →
Quick Start
1. Create your copy. Click "Use this template" on GitHub. Make it private. Clone it.
git clone https://github.com/YOUR-USERNAME/my-wiki.git
cd my-wiki2. Set up your workspace. Open the repo as an Obsidian vault on one side, your AI agent on the other. You talk to the AI — it builds the wiki. You watch it happen in Obsidian.
Full Obsidian setup → · No Obsidian? Any editor + any supported AI tool works fine.
3. Fill in your profile. Open _config/config.md, fill in the About You section, and set Training Start Date to today.
4. Start talking. Open in your AI tool of choice and go:
"Capture this: here's how our onboarding process works..."
"We decided to use PostgreSQL over MongoDB, let me document why"
"What do we know about our deployment process?"
"Lint the wiki, what needs attention?"
That's it. The system adapts to what you actually need.
Want to stay updated as the framework improves? The template approach gives you a clean start but disconnects you from upstream. If you want to pull future improvements (new protocols, better training behavior, bug fixes), use the Framework Track setup instead.
What Makes This Different
It learns how you work. The first 30 days are a training period. Your AI asks questions, suggests directories, and logs what it learns. By day 45, it's quiet and efficient. You never design a taxonomy upfront. Full details →
Capture first, organize later. Everything lands in _inbox/ with a 7-day TTL. You never hesitate to capture because you don't have to decide where it goes yet. Your AI files it later.
Your README stays yours. This file has two sections split by a marker. Above it: your personal project README, maintained by your AI as the wiki evolves. Below it: the framework docs, which track upstream cleanly. You get living documentation without merge conflicts.
Patterns are captured as they emerge. When your AI learns a new convention or preference during a conversation, it writes it down immediately, not at commit time. Nothing is lost if you commit from the command line without AI involvement.
Every file is queryable. A metadata standard on every document means your AI can scan summaries and tags without loading full files. This scales to hundreds of documents.
It maintains itself. Lint checks surface stale files, missing metadata, and orphaned docs. The system even reviews its own instruction efficiency to prevent context window bloat as your wiki grows.
What You Can Do
| Say this | What happens |
|---|---|
| "Capture this: here's how we set up monitoring..." | Creates a file in _inbox/, offers to file it |
| "We decided to use Terraform over Pulumi, document why" | Decision record with context, options, rationale, and an outcome section to fill in later |
| "What do we know about our hiring process?" | Scans summaries, synthesizes an answer with source citations |
| "Lint the wiki" | Surfaces stale files, missing metadata, orphaned docs |
| "Start a new initiative: migrate to Kubernetes" | Project workspace with brief, timeline, artifact tracking |
| "Create a slide deck summarizing Q1 decisions" | Generates output in _output/, dated and organized |
These form a cycle. Capture feeds queries, queries inform decisions, decisions get tracked, lint keeps it all healthy. The system compounds over time.
Go Deeper
| Topic | What's there |
|---|---|
| Training Phases | How the system adapts to you over 30 days |
| Directory Structure | What each folder is for, why there are only 4 |
| Journal Sync & Privacy | Syncing 3-Journal/ across devices — plaintext, git-crypt, or external |
| Metadata Standard | The format that makes everything queryable |
| Supported Tools | Claude Code, Cursor, Copilot, Windsurf, ChatGPT, and others |
| Obsidian Setup | Pre-configured vault, plugins, web clipper |
| Design Decisions | Why the system works the way it does |
| FAQ | Common questions |
| Linked Code Repos | Connect wiki project entries to real code repos — workspace files, context files, Obsidian plugin dev |
| Extending & Contributing | Customize locally vs. contribute upstream |
| Future Directions | Where this is headed |
| Philosophy | The deeper thinking behind the system |
The examples/ directory has four sample files showing the metadata standard in action. Read them, then delete them when you're comfortable.
Credits
Built on Andrej Karpathy's LLM Wiki Pattern. Implementation by Ariel Sakin, refined over several months of daily use managing business operations.
License
Apache 2.0. See LICENSE.
LICENSE
Shown as plain text.
Apache License
Version 2.0, January 2004
http://www.apache.org/licenses/
TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
1. Definitions.
"License" shall mean the terms and conditions for use, reproduction,
and distribution as defined by Sections 1 through 9 of this document.
"Licensor" shall mean the copyright owner or entity authorized by
the copyright owner that is granting the License.
"Legal Entity" shall mean the union of the acting entity and all
other entities that control, are controlled by, or are under common
control with that entity. For the purposes of this definition,
"control" means (i) the power, direct or indirect, to cause the
direction or management of such entity, whether by contract or
otherwise, or (ii) ownership of fifty percent (50%) or more of the
outstanding shares, or (iii) beneficial ownership of such entity.
"You" (or "Your") shall mean an individual or Legal Entity
exercising permissions granted by this License.
"Source" form shall mean the preferred form for making modifications,
including but not limited to software source code, documentation
source, and configuration files.
"Object" form shall mean any form resulting from mechanical
transformation or translation of a Source form, including but
not limited to compiled object code, generated documentation,
and conversions to other media types.
"Work" shall mean the work of authorship, whether in Source or
Object form, made available under the License, as indicated by a
copyright notice that is included in or attached to the work
(an example is provided in the Appendix below).
"Derivative Works" shall mean any work, whether in Source or Object
form, that is based on (or derived from) the Work and for which the
editorial revisions, annotations, elaborations, or other modifications
represent, as a whole, an original work of authorship. For the purposes
of this License, Derivative Works shall not include works that remain
separable from, or merely link (or bind by name) to the interfaces of,
the Work and Derivative Works thereof.
"Contribution" shall mean any work of authorship, including
the original version of the Work and any modifications or additions
to that Work or Derivative Works thereof, that is intentionally
submitted to the Licensor for inclusion in the Work by the copyright owner
or by an individual or Legal Entity authorized to submit on behalf of
the copyright owner. For the purposes of this definition, "submitted"
means any form of electronic, verbal, or written communication sent
to the Licensor or its representatives, including but not limited to
communication on electronic mailing lists, source code control systems,
and issue tracking systems that are managed by, or on behalf of, the
Licensor for the purpose of discussing and improving the Work, but
excluding communication that is conspicuously marked or otherwise
designated in writing by the copyright owner as "Not a Contribution."
"Contributor" shall mean Licensor and any individual or Legal Entity
on behalf of whom a Contribution has been received by the Licensor and
subsequently incorporated within the Work.
2. Grant of Copyright License. Subject to the terms and conditions of
this License, each Contributor hereby grants to You a perpetual,
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
copyright license to reproduce, prepare Derivative Works of,
publicly display, publicly perform, sublicense, and distribute the
Work and such Derivative Works in Source or Object form.
3. Grant of Patent License. Subject to the terms and conditions of
this License, each Contributor hereby grants to You a perpetual,
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
(except as stated in this section) patent license to make, have made,
use, offer to sell, sell, import, and otherwise transfer the Work,
where such license applies only to those patent claims licensable
by such Contributor that are necessarily infringed by their
Contribution(s) alone or by combination of their Contribution(s)
with the Work to which such Contribution(s) was submitted. If You
institute patent litigation against any entity (including a
cross-claim or counterclaim in a lawsuit) alleging that the Work
or a Contribution incorporated within the Work constitutes direct
or contributory patent infringement, then any patent licenses
granted to You under this License for that Work shall terminate
as of the date such litigation is filed.
4. Redistribution. You may reproduce and distribute copies of the
Work or Derivative Works thereof in any medium, with or without
modifications, and in Source or Object form, provided that You
meet the following conditions:
(a) You must give any other recipients of the Work or
Derivative Works a copy of this License; and
(b) You must cause any modified files to carry prominent notices
stating that You changed the files; and
(c) You must retain, in the Source form of any Derivative Works
that You distribute, all copyright, patent, trademark, and
attribution notices from the Source form of the Work,
excluding those notices that do not pertain to any part of
the Derivative Works; and
(d) If the Work includes a "NOTICE" text file as part of its
distribution, then any Derivative Works that You distribute must
include a readable copy of the attribution notices contained
within such NOTICE file, excluding any notices that do not
pertain to any part of the Derivative Works, in at least one
of the following places: within a NOTICE text file distributed
as part of the Derivative Works; within the Source form or
documentation, if provided along with the Derivative Works; or,
within a display generated by the Derivative Works, if and
wherever such third-party notices normally appear. The contents
of the NOTICE file are for informational purposes only and
do not modify the License. You may add Your own attribution
notices within Derivative Works that You distribute, alongside
or as an addendum to the NOTICE text from the Work, provided
that such additional attribution notices cannot be construed
as modifying the License.
You may add Your own copyright statement to Your modifications and
may provide additional or different license terms and conditions
for use, reproduction, or distribution of Your modifications, or
for any such Derivative Works as a whole, provided Your use,
reproduction, and distribution of the Work otherwise complies with
the conditions stated in this License.
5. Submission of Contributions. Unless You explicitly state otherwise,
any Contribution intentionally submitted for inclusion in the Work
by You to the Licensor shall be under the terms and conditions of
this License, without any additional terms or conditions.
Notwithstanding the above, nothing herein shall supersede or modify
the terms of any separate license agreement you may have executed
with Licensor regarding such Contributions.
6. Trademarks. This License does not grant permission to use the trade
names, trademarks, service marks, or product names of the Licensor,
except as required for reasonable and customary use in describing the
origin of the Work and reproducing the content of the NOTICE file.
7. Disclaimer of Warranty. Unless required by applicable law or
agreed to in writing, Licensor provides the Work (and each
Contributor provides its Contributions) on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
implied, including, without limitation, any warranties or conditions
of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
PARTICULAR PURPOSE. You are solely responsible for determining the
appropriateness of using or redistributing the Work and assume any
risks associated with Your exercise of permissions under this License.
8. Limitation of Liability. In no event and under no legal theory,
whether in tort (including negligence), contract, or otherwise,
unless required by applicable law (such as deliberate and grossly
negligent acts) or agreed to in writing, shall any Contributor be
liable to You for damages, including any direct, indirect, special,
incidental, or consequential damages of any character arising as a
result of this License or out of the use or inability to use the
Work (including but not limited to damages for loss of goodwill,
work stoppage, computer failure or malfunction, or any and all
other commercial damages or losses), even if such Contributor
has been advised of the possibility of such damages.
9. Accepting Warranty or Additional Liability. While redistributing
the Work or Derivative Works thereof, You may choose to offer,
and charge a fee for, acceptance of support, warranty, indemnity,
or other liability obligations and/or rights consistent with this
License. However, in accepting such obligations, You may act only
on Your own behalf and on Your sole responsibility, not on behalf
of any other Contributor, and only if You agree to indemnify,
defend, and hold each Contributor harmless for any liability
incurred by, or claims asserted against, such Contributor by reason
of your accepting any such warranty or additional liability.
END OF TERMS AND CONDITIONS
Copyright 2026 Ariel Sakin
Licensed under the Apache License, Version 2.0 (the "License");
you may not use this file except in compliance with the License.
You may obtain a copy of the License at
http://www.apache.org/licenses/LICENSE-2.0
Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.
73 files
- .claude/CLAUDE.md
- .claude/settings.json
- .cursor/rules/bootstrap.mdc
- .cursorrules
- .github/copilot-instructions.md
- .gitignore
- .obsidian/app.json
- .obsidian/appearance.json
- .obsidian/core-plugins.json
- .obsidian/daily-notes.json
- .obsidian/graph.json
- .obsidian/snippets/llm-wiki.css
- .obsidian/templates.json
- .windsurfrules
- 1-Projects/README.md
- 1-Projects/_SHIPPED/.gitkeep
- 1-Projects/_parked/README.md
- 2-Knowledge/Decisions/.gitkeep
- 2-Knowledge/HowTo/.gitkeep
- 2-Knowledge/README.md
- 2-Knowledge/References/.gitkeep
- 2-Knowledge/log.md
- 3-Journal/README.md
- 4-Private/README.md
- ATTRIBUTION.md
- CODE_OF_CONDUCT.md
- CONTRIBUTING.md
- LICENSE
- PHILOSOPHY.md
- README.md
- WIKI-LOG.md
- _config/config.md
- _config/context.md
- _config/standard.md
- _config/tools.md
- _inbox/README.md
- _meta/instructions/agent-write.md
- _meta/instructions/blog-posts/instructions.md
- _meta/instructions/definition-of-done.md
- _meta/instructions/general.md
- _meta/instructions/knowledge-lint.md
- _meta/instructions/knowledge-query.md
- _meta/instructions/optimization-review.md
- _meta/templates/blog-post.md
- _meta/templates/decision.md
- _meta/templates/inbox-capture.md
- _meta/templates/initiative.md
- _meta/templates/journal-entry.md
- _meta/templates/knowledge-article.md
- _meta/templates/meeting-notes.md
- _output/README.md
- _sources/.gitkeep
- _sources/README.md
- assets/.gitkeep
- assets/clipper-template.json
- docs/claude-code-setup.md
- docs/design-decisions.md
- docs/directory-structure.md
- docs/extending-and-contributing.md
- docs/faq.md
- docs/future-directions.md
- docs/journal-sync.md
- docs/linked-code-repos.md
- docs/llm-wiki-pattern.md
- docs/metadata-standard.md
- docs/obsidian-setup.md
- docs/supported-tools.md
- docs/training-phases.md
- examples/example-decision-record.md
- examples/example-inbox-capture.md
- examples/example-initiative.md
- examples/example-knowledge-article.md
- migrate-to-yaml-frontmatter.py
Advantages
- The system adapts to user patterns over a 30-day training period without requiring upfront taxonomy design. evidence: README.md
- Metadata standards on every document allow the AI to scan summaries and tags without loading full files, enabling scalability. evidence: README.md
- The inbox-first capture system allows for frictionless entry of information with a 7-day TTL for later filing. evidence: README.md
Limitations
- The template approach disconnects the user from upstream updates unless the Framework Track setup is used. evidence: README.md
Security
Risk level: No risk found
This brain runs
Agent instructions that run or fetch something (1)
.claude/CLAUDE.md:**Exception:** If the user's first message is a `/init` command or a meta question about the repo setup, complete that first — then run the Session Start Protocol on the next exchange.
Attribution and licence
- First committed by
asakin
- Publisher
- Ariel Sakin (Community)
- Source
- asakin/llm-context-base · commit 3c096ca
- Licence
- Apache License 2.0 (files served here)
- ATTRIBUTION.md (written by AutoGineer)
- Synced
- Contributors
- asakin, claude
AutoGineer is not affiliated with or endorsed by asakin.
Download
The ZIP holds the files AutoGineer serves, with ATTRIBUTION.md and the licence. Download llm-context-base.zip