loop-library

Keep this project's graph lean and trustworthy — merge duplicates, retire stale notes (respecting task hierarchy), resolve contradictions, fix links, resolve entities, flag type drift, re-derive the per-entity timelines, regenerate the index-views, and surface stale tasks. Suggest-only; asks before deleting. Use periodically, before an important piece of work, or when the graph feels noisy. (brainkit's name for Karpathy's "lint".)

Capture new material into this project's graph as a typed entity — resolve what it mentions to canonical notes (with you, at capture), expand its shorthand and link it, preserve the raw, append to any touched entity's timeline, and extract the reusable knowledge and tasks. Use whenever the user shares or refers to something the brain should remember — a call, a meeting note, a doc, a decision, a person, a task, a link.

Put this project's graph to work toward the deliverable — answer a grounded question, advance a work/ deliverable with citations, run gap analysis ("what's missing for this?"), or read the task and reading-queue views — and file genuinely new conclusions back. Use when the user asks something the brain should know, asks to move a deliverable forward, or asks what's open or unprocessed.

Curate upstream improvements into this kit — a research task, not a script. Read canonical brainkit upstream, reason about what genuinely improved, and pull in only the changes you and the user find compelling, preserving local tweaks. Suggest-only; never bulk-overwrites. Use when the user wants to refresh the kit's machinery from origin.

Curate upstream improvements into this kit — a research task, not a script. Read canonical karpathy-core upstream, reason about what genuinely improved, and pull in only the changes you and the user find compelling, preserving local tweaks. Suggest-only; never bulk-overwrites. Use when the user wants to refresh the kit's machinery from origin.

Curate upstream improvements into this kit — a research task, not a script. Read canonical loopkit upstream, reason about what genuinely improved, and pull in only the changes you and the user find compelling, preserving local tweaks. Suggest-only; never bulk-overwrites. Use when the user wants to refresh the kit's machinery from origin.

Ingest a source into the Loop Library — read it, mirror it immutably, write its Source concept, and compile it into the wiki (loops/concepts/comparisons), updating indexes and the log. Use when the user adds a source (a paper, post, doc, transcript) or drops a file in inbox/ and wants it folded into the knowledge base.

Health-check the Loop Library wiki — run the conformance and lint scripts, then review for what scripts can't catch (contradictions vs newer sources, provenance drift, orphan/missing pages, stale timestamps) and fix what's safe. Use periodically, before merging, or when the user asks to clean up or audit the knowledge base.

Answer a question against the Loop Library wiki — read the index first, drill into relevant pages, synthesize with citations, and file genuinely new findings back as wiki pages. Use when the user asks a question about loops, patterns, or concepts that the knowledge base should answer.

Harvest changes to this project's intent from the current or a prior session — guided by the repo's heuristics doc — validate them with the user, apply only the approved ones, and update the heuristics doc so detection improves over time. Use at the end of a session, after a substantial change, or when the user wants to reconcile intent drift in GOAL / HYPOTHESES / TASKS / CLAUDE.

Keep this project's knowledge base lean and trustworthy — merge duplicates, retire stale notes, resolve contradictions, fix broken links, and flag deliverables that have drifted from the notes. Suggest-only; asks before deleting. Use periodically, before an important piece of work, or when the knowledge base feels noisy. (This is karpathy-core's name for Karpathy's "lint".)

Add new material into this project's knowledge base — file it as a short, linked note with a one-line summary, a kind label, and where it came from. Use whenever the user shares or refers to something the project should remember — a call, a doc, a decision, a finding, a link, an experiment result.

Put this project's knowledge base to work — answer a grounded question, or draft and advance a deliverable in work/, using the accumulated notes and golden context, and file genuinely new conclusions back. Use when the user asks something the project should know, or asks to move a deliverable forward.

Keep this project's graph lean and trustworthy — merge duplicates, retire stale notes, resolve contradictions, fix links, resolve entities and flag type drift, and regenerate stamped views. Suggest-only; asks before deleting. Use periodically, before an important piece of work, or when the graph feels noisy. (This is loopkit's name for Karpathy's "lint".)

Add new material to this project's graph as a typed entity note — resolve the things it mentions to their canonical notes, link it with relative-markdown edges, and keep the index current. Use whenever the user shares or refers to something the project should remember — a call, a doc, a decision, a finding, a person, a link.

Put this project's graph to work — answer a grounded question, or draft and advance a deliverable in work/, using the typed notes, their links, and golden context, and file genuinely new conclusions back. Use when the user asks something the project should know, or asks to move a deliverable forward.

Keep this project's knowledge base lean and trustworthy — merge duplicates, retire stale notes, resolve contradictions, fix broken links, and flag deliverables that have drifted from the notes. Suggest-only; asks before deleting. Use periodically, before an important piece of work, or when the knowledge base feels noisy. (This is loopkit's name for Karpathy's "lint".)

Add new material into this project's knowledge base — file it as a short, linked note with a one-line summary, a kind label, and where it came from. Use whenever the user shares or refers to something the project should remember — a call, a doc, a decision, a finding, a link, an experiment result.

Put this project's knowledge base to work — answer a grounded question, or draft and advance a deliverable in work/, using the accumulated notes and golden context, and file genuinely new conclusions back. Use when the user asks something the project should know, or asks to move a deliverable forward.