AiImported version
Maintenance Obsidian
/Users/fabien/Desktop/AI/PROMPTS/-ai/-memory/Maintenance obsidian.odt
Folder-ai/-memory
Versions0
Imported2026-06-28
StatusActive
## _brainai Personal Knowledge Base — Workflow Prompts A set of prompts for running a personal knowledge base built on a `raw/` folder (unprocessed sources) and a `wiki/` folder (structured knowledge), governed by a `CLAUDE.md` schema. ## SCHEMA (The Rules File) What this does: Checks the CLAUDE.md rules file that governs how your entire knowledge base operates. Run this every month. Everything else depends on it. You'll have a working knowledge brain that gets smarter over time. Check/update (or create if not existing yet) the CLAUDE.md file for _brainai personal knowledge base system. The system uses a raw/ folder for unprocessed sources and a wiki/ folder for structured knowledge. Define these workflows: 1. INGEST: How to process a single source from raw/ into wiki/pages (summary page, concept pages, entity pages, index update, backlinks, contradiction flags, log entry). 2. QUERY: How to answer questions using wiki/index.md as the entry point, cite sources, and optionally create new pages. 3. LINT: How to health-check all wiki pages for orphans, broken links, stale content, missing backlinks, and contradictions. 4. Page format: Each wiki page needs title, source references, summary, key concepts, related pages (backlinks), and a last-updated timestamp. Keep the schema under 200 lines. Optimize for clarity over completeness. The AI should be able to follow it without asking questions. ## LINT What this does: Runs a health check on your entire wiki. Catches errors before they compound. Suggests new sources to fill knowledge gaps. The AI writes something slightly wrong. You save it back. The next answer builds on the wrong thing. Two months later, five pages reinforce the same mistake. One lint check per month. Ten minutes. Don't skip it. Run a full health check on wiki/ per the lint workflow in CLAUDE.md. Output to wiki/lint-report-[date].md with severity levels. Suggest 3 articles to fill the biggest knowledge gaps. ## EXPLORE What this does: Surfaces hidden patterns and unexpected connections across your wiki. The "what am I missing" prompt. This is where the system pays for itself. You'll find angles and patterns that would take weeks of manual reading to spot. Read wiki/index.md and scan all concept pages. Find the 3 most surprising connections between topics that aren't currently linked. For each connection: explain why it matters, which wiki pages are involved, and whether a new concept page should be created. Also identify 2 topics that appear in multiple sources but don't have their own dedicated page yet. ## HEALTH - Find orphan notes (mentions of people, projects, or companies that don't have their own files yet). Create those files. - Consolidate duplicate notes. - Update relevant MOCs with new links. ## PROMPT #1: INGEST What this does: Reads a single source, extracts key ideas, builds wiki pages, and connects everything to your existing knowledge base. Start with one source at a time. Read the summaries. Guide the AI on what to emphasize. This produces dramatically better results than batch-processing. Read the schema in CLAUDE.md. Then process [FILENAME] from raw/. Read it fully, discuss key takeaways with me, then: create a summary page in wiki/, update wiki/index.md, update all relevant concept and entity pages, add backlinks, flag any contradictions, and append to wiki/log.md. ## PROMPT #2: BATCH INGEST What this does: Processes multiple sources in sequence when you have a backlog. Less control per source, but faster for bulk loading. Use this after you've done 5-10 manual ingests and trust the schema. The AI knows your preferences by then. Read the schema in CLAUDE.md. List all unprocessed files in raw/. For each file: read it fully, create a summary page in wiki/, update wiki/index.md, update all relevant concept and entity pages, add backlinks, flag contradictions, and append to wiki/log.md. Process them one at a time. Pause after every 3 files and show me a progress summary with key themes emerging across sources. ## PROMPT #3: QUERY What this does: Asks your knowledge base a question and cites which wiki pages informed the answer. New connections get filed back automatically. Read wiki/index.md. Based on what's in the knowledge base, answer: [YOUR QUESTION]. Cite which wiki pages informed your answer. If this reveals new connections worth preserving, create a new page in wiki/ and update the index. Try these to see the system's power: - "What are the three biggest gaps in this knowledge base?" - "Which sources disagree with each other, and on what?" - "Write a 500-word briefing on [topic] using only wiki content." ## PROMPT #4: LINT What this does: Runs a health check on your entire wiki. Catches errors before they compound. Suggests new sources to fill knowledge gaps. The AI writes something slightly wrong. You save it back. The next answer builds on the wrong thing. Two months later, five pages reinforce the same mistake. One lint check per month. Ten minutes. Don't skip it. Run a full health check on wiki/ per the lint workflow in CLAUDE.md. Output to wiki/lint-report-[date].md with severity levels. Suggest 3 articles to fill the biggest knowledge gaps. ## PROMPT #5: EXPLORE What this does: Surfaces hidden patterns and unexpected connections across your wiki. The "what am I missing" prompt. This is where the system pays for itself. You'll find angles and patterns that would take weeks of manual reading to spot. Read wiki/index.md and scan all concept pages. Find the 3 most surprising connections between topics that aren't currently linked. For each connection: explain why it matters, which wiki pages are involved, and whether a new concept page should be created. Also identify 2 topics that appear in multiple sources but don't have their own dedicated page yet. ## PROMPT #6: BRIEF What this does: Generates a polished research brief on any topic using only your wiki content. Ready to send to a client, team, or use in your own work. Replace [LENGTH] with 300, 500, or 1000 depending on your need. Replace [TOPIC] with whatever you're working on. The wiki does the research. You just ask. Read wiki/index.md. Write a [LENGTH]-word research brief on [TOPIC]. Use only information from the wiki. Structure it as: Executive Summary (3 sentences), Key Findings (numbered list), Areas of Disagreement Between Sources, Gaps in Current Knowledge, and Recommended Next Steps. Cite wiki page names inline. If this brief surfaces new connections, create a wiki page for it. ## PROMPT #7: SCHEMA (The Rules File) What this does: Generates the CLAUDE.md rules file that governs how your entire knowledge base operates. Run this first. Everything else depends on it. Run this once. Then run Ingest on your first source. You'll have a working knowledge base in under 30 minutes. Create a CLAUDE.md file for a personal knowledge base system. The system uses a raw/ folder for unprocessed sources and a wiki/ folder for structured knowledge. Define these workflows: 1. INGEST: How to process a single source from raw/ into wiki/pages (summary page, concept pages, entity pages, index update, backlinks, contradiction flags, log entry). 2. QUERY: How to answer questions using wiki/index.md as the entry point, cite sources, and optionally create new pages. 3. LINT: How to health-check all wiki pages for orphans, broken links, stale content, missing backlinks, and contradictions. 4. Page format: Each wiki page needs title, source references, summary, key concepts, related pages (backlinks), and a last-updated timestamp. Keep the schema under 200 lines. Optimize for clarity over completeness. The AI should be able to follow it without asking questions.