b/AI-Wiki
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

claude's suggested edits

Browse Source
This commit is contained in:
b
2026-05-13 19:44:10 -07:00
parent 47daa3d2f4
commit e42d056981
1 changed files with 64 additions and 43 deletions
Download Patch File Download Diff File Expand all files Collapse all files
CLAUDE.md
+64 -43
View File
@@ -5,7 +5,7 @@ Based on Andrej Karpathy's LLM Wiki pattern.
## Purpose ## Purpose
This wiki is a structured, interlinked knowledge base for planning a trip to Japan. This wiki is a structured, interlinked knowledge base for <ADD YOUR PURPOSE HERE>.
Claude maintains the wiki. The human curates sources, asks questions, and guides the analysis. Claude maintains the wiki. The human curates sources, asks questions, and guides the analysis.
## Folder structure ## Folder structure
@@ -13,83 +13,104 @@ Claude maintains the wiki. The human curates sources, asks questions, and guides
``` ```
raw/ -- source documents (immutable -- never modify these) raw/ -- source documents (immutable -- never modify these)
wiki/ -- markdown pages maintained by Claude wiki/ -- markdown pages maintained by Claude
wiki/index.md -- table of contents for the entire wiki wiki/index.md -- master table of contents with one-line descriptions
wiki/log.md -- append-only record of all operations wiki/log.md -- append-only record of all operations (newest entry first)
templates/ -- a directory of templates to be used when creating pages (optional)
``` ```
## Ingest workflow
When the user adds a new source to `raw/` and asks you to ingest it:
1. Read the full source document
2. Discuss key takeaways with the user before writing anything
3. Create a summary page in `wiki/` named after the source
4. Create or update concept pages for each major idea or entity
5. Add wiki-links ([[page-name]]) to connect related pages
6. Update `wiki/index.md` with new pages and one-line descriptions
7. Append an entry to `wiki/log.md` with the date, source name, and what changed
A single source may touch 10-15 wiki pages. That is normal.
## Page format ## Page format
Every wiki page should follow this structure: Every wiki page must follow this structure exactly:
```markdown ```markdown
# Page Title # Page Title
**Summary**: One to two sentences describing this page. **Summary**: One to two sentences describing this page.
**Sources**: List of raw source files this page draws from. **Sources**: `filename1.pdf`, `filename2.md`
**Last updated**: Date of most recent update. **Last updated**: YYYY-MM-DD
--- ---
Main content goes here. Use clear headings and short paragraphs. Main content here. Use clear headings and short paragraphs.
Link to related concepts using [[wiki-links]] throughout.
Link to related concepts using [[wiki-links]] throughout the text.
## Related pages ## Related pages
- [[related-concept-1]] - [[related-concept-1]] — one-line description of relationship
- [[related-concept-2]] - [[related-concept-2]] — one-line description of relationship
``` ```
Page naming: lowercase with hyphens (e.g. `transformer-architecture.md`).
## Log format
Each `wiki/log.md` entry must follow this exact format:
```
## YYYY-MM-DD — <operation type>
**Source**: filename (for ingests) or "n/a"
**Pages created**: page-a.md, page-b.md
**Pages updated**: page-c.md
**Summary**: One sentence describing what changed and why.
```
Entries are prepended (newest first). Never edit or delete existing entries.
## Ingest workflow
When the user adds a new source to `raw/` and asks you to ingest it:
1. Read the full source document
2. Read `wiki/index.md` to understand existing coverage
3. Identify which existing pages will be affected, and flag any overlap or contradiction with what's already in the wiki
4. Discuss key takeaways and your proposed page plan with the user before writing anything
5. Create a summary page in `wiki/` named after the source
6. Create new concept pages for major ideas not yet covered; update existing pages rather than duplicating coverage
7. Add [[wiki-links]] to connect related pages in both directions
8. Update `wiki/index.md` with all new pages and their one-line descriptions
9. Prepend an entry to `wiki/log.md` following the log format above
A single source may touch 10–15 wiki pages. That is normal. When unsure whether a concept warrants its own page vs. a section on an existing page, ask the user.
## Citation rules ## Citation rules
- Every factual claim should reference its source file - Every factual claim must reference its source using `(source: filename.pdf)`
- Use the format (source: filename.pdf) after the claim - If two sources disagree, note the contradiction explicitly and do not silently resolve it
- If two sources disagree, note the contradiction explicitly - If a claim has no source, mark it `[needs source]`
- If a claim has no source, mark it as needing verification - If a source is superseded by a newer one, note this on both pages
## Question answering ## Question answering
When the user asks a question: When the user asks a question:
1. Read `wiki/index.md` first to find relevant pages 1. Read `wiki/index.md` to identify relevant pages
2. Read those pages and synthesize an answer 2. Read those pages and synthesize a direct answer
3. Cite specific wiki pages in your response 3. Cite specific wiki pages in your response
4. If the answer is not in the wiki, say so clearly 4. If the answer is not in the wiki, say so clearly and identify which pages are closest
5. If the answer is valuable, offer to save it as a new wiki page 5. If answering the question surfaces new knowledge worth keeping, offer to save it as a new wiki page
Good answers should be filed back into the wiki so they compound over time. Good answers compound over time — file them back into the wiki.
## Lint ## Lint
When the user asks you to lint or audit the wiki: When the user asks you to lint or audit the wiki:
- Check for contradictions between pages - Check for contradictions between pages
- Find orphan pages (no inbound links from other pages) - Find orphan pages (pages with no inbound [[wiki-links]] from other pages)
- Identify concepts mentioned in pages that lack their own page - Find broken links ([[wiki-links]] pointing to pages that don't exist)
- Flag claims that may be outdated based on newer sources - Identify concepts mentioned in text that lack their own page
- Flag claims marked `[needs source]`
- Flag claims that may be outdated based on newer source dates
- Check that all pages follow the page format above - Check that all pages follow the page format above
- Report findings as a numbered list with suggested fixes - Report findings as a numbered list with suggested fixes, ordered by severity
## Rules ## Rules
- Never modify anything in the `raw/` folder - Never modify anything in `raw/`
- Always update `wiki/index.md` and `wiki/log.md` after changes - Always update `wiki/index.md` and `wiki/log.md` after any change
- Keep page names lowercase with hyphens (e.g. `machine-learning.md`) - Check existing wiki coverage before creating new pages — prefer updating over duplicating
- Write in clear, plain language - When uncertain about scope, categorization, or conflicts, ask the user before writing
- When uncertain about how to categorize something, ask the user - Write in clear, plain language — prefer short sentences over dense prose