arscontexta README

The project's README from github.com/agenticnotetaking/arscontexta. As one markdown file: README.md.

Ars Contexta

A second brain for your agent.

A Claude Code plugin that generates complete knowledge systems from conversation. You describe how you think and work. The engine derives a cognitive architecture -- folder structure, context files, processing pipeline, hooks, navigation maps, and note templates -- tailored to your domain and backed by 249 research claims.

No templates. No configuration. Just conversation.

v0.8.0 · Claude Code plugin · MIT


Installation

  1. Add the marketplace to Claude Code:

    /plugin marketplace add agenticnotetaking/arscontexta
    
  2. Install the plugin:

    /plugin install arscontexta@agenticnotetaking
    
  3. Restart Claude Code, then run:

    /arscontexta:setup
    
  4. Answer 2-4 questions about your domain (~20 minutes -- token-intensive but one-time)

  5. The engine generates your complete knowledge system

  6. Restart Claude Code again to activate generated hooks and skills

  7. Run /arscontexta:help to see everything available


What It Does

Most AI tools start every session blank. Ars Contexta changes that by generating a persistent thinking system derived from how you actually work.

What you get:

The key differentiator: derivation, not templating. Every choice traces to specific research claims. The engine reasons from principles about what your domain needs and why.


The Setup Flow

/arscontexta:setup runs a 6-phase process:

Phase What Happens
Detection Detects Claude Code environment and capabilities
Understanding 2-4 conversation turns where you describe your domain
Derivation Maps signals to eight configuration dimensions with confidence scoring
Proposal Shows what will be generated and why, in your vocabulary
Generation Produces all files: context file, folders, templates, skills, hooks, manual
Validation Checks all 15 kernel primitives, runs pipeline smoke test

The whole process takes about 20 minutes. It's token-intensive because the engine reads research claims, reasons about your domain, and generates substantial output. This is a one-time investment -- after setup, your agent remembers.

For advanced users: /arscontexta:setup --advanced to configure dimensions directly.


Three-Space Architecture

Every generated system separates content into three spaces:

Space Purpose Growth
self/ Agent persistent mind -- identity, methodology, goals Slow (tens of files)
notes/ Knowledge graph -- the reason the system exists Steady (10-50/week)
ops/ Operational coordination -- queue state, sessions Fluctuating

Names adapt to your domain (notes/ might become reflections/, claims/, or decisions/), but the separation is invariant.


Commands

Plugin-Level (always available)

Command What It Does
/arscontexta:setup Conversational onboarding -- generates your full system
/arscontexta:help Contextual guidance and command discovery
/arscontexta:tutorial Interactive walkthrough (learn by doing)
/arscontexta:ask Query the research graph for methodology answers
/arscontexta:health Run diagnostic checks on your vault
/arscontexta:recommend Get architecture advice for your use case
/arscontexta:architect Research-backed evolution guidance
/arscontexta:add-domain Add a new knowledge domain to an existing system
/arscontexta:reseed Re-derive from first principles when drift accumulates
/arscontexta:upgrade Apply plugin knowledge base updates to your system

Generated (available after setup)

Command What It Does
/reduce Extract insights from sources
/reflect Find connections, update MOCs
/reweave Update older notes with new connections
/verify Combined quality check: description + schema + health
/validate Schema compliance checking
/seed Create extraction task with duplicate detection
/ralph Queue-based orchestration with fresh context per phase
/pipeline End-to-end source processing
/tasks Queue management
/stats Vault metrics
/graph Graph analysis
/next Next-action recommendation
/learn Research and grow
/remember Mine session learnings
/rethink Challenge system assumptions
/refactor Structural improvements

Processing Pipeline

The vault implements the 6 Rs, extending Cornell Note-Taking's 5 Rs with a meta-cognitive layer:

Phase What Happens Command
Record Zero-friction capture into inbox/ Manual
Reduce Extract insights with domain-native categories /reduce
Reflect Find connections, update MOCs /reflect
Reweave Update older notes with new context /reweave
Verify Description + schema + health checks /verify
Rethink Challenge system assumptions /rethink

Fresh Context Per Phase

Each phase runs in its own context window via subagent spawning. LLM attention degrades as context fills. By spawning a fresh subagent per phase, every phase operates in the "smart zone."

/ralph 5
  |-- Read queue, find next unblocked task
  |-- Spawn subagent (fresh context)
  |   +-- Runs skill, updates task file, returns handoff
  |-- Parse handoff, capture learnings
  |-- Advance phase in queue
  +-- Repeat for 5 tasks

Hooks

Four hooks automate quality enforcement:

Hook Event What It Does
Session Orient SessionStart Injects workspace tree, loads identity, surfaces maintenance signals
Write Validate PostToolUse (Write) Schema enforcement on every note write
Auto Commit PostToolUse (Write, async) Git auto-commit, non-blocking
Session Capture Stop Persists session state to ops/sessions/

The Research Graph

The methodology/ directory contains 249 interconnected research claims about tools for thought, knowledge management, and agent-native cognitive architecture. These claims back every configuration decision.

Synthesizes

Zettelkasten -- Cornell Note-Taking -- Evergreen Notes -- PARA -- GTD -- Memory Palaces -- Cognitive Science (extended mind, spreading activation, generation effect) -- Network Theory (small-world topology, betweenness centrality) -- Agent Architecture (context windows, session boundaries, multi-agent patterns)

How Claims Back Decisions

Every kernel primitive includes cognitive_grounding linking to specific research:

Query directly: /arscontexta:ask "Why does my system use atomic notes?"


Semantic Search (optional)

qmd adds concept matching across vocabularies. Not required -- the system works fully with ripgrep + MOC traversal.

/setup should perform this configuration automatically when semantic search is active. The commands below are manual fallback/setup verification.

# Install qmd
npm install -g @tobilu/qmd
# or
bun install -g @tobilu/qmd

cd your-vault/
qmd init
qmd collection add . --name <notes_directory_name> --mask "<notes_directory_name>/**/*.md"
qmd embed

Create or merge .mcp.json in the vault root:

{
  "mcpServers": {
    "qmd": {
      "command": "qmd",
      "args": ["mcp"],
      "autoapprove": [
        "mcp__qmd__search",
        "mcp__qmd__vector_search",
        "mcp__qmd__deep_search",
        "mcp__qmd__get",
        "mcp__qmd__multi_get",
        "mcp__qmd__status"
      ]
    }
  }
}

Keep qmd MCP configuration and tool preapproval in .mcp.json.


Prerequisites

Dependency Required Purpose
Claude Code v1.0.33+ Yes Plugin host
tree Yes Workspace structure injection
ripgrep (rg) Yes YAML queries, schema validation
qmd Optional Semantic search

Project Structure

arscontexta/
|-- .claude-plugin/
|   |-- plugin.json              # Plugin manifest
|   +-- marketplace.json         # Marketplace listing
|-- skills/                      # 10 plugin-level commands
|   |-- setup/                   # Conversational onboarding
|   |-- help/                    # Contextual guidance
|   |-- tutorial/                # Interactive walkthrough
|   |-- ask/                     # Query the research graph
|   |-- health/                  # Diagnostic checks
|   |-- recommend/               # Architecture advice
|   |-- architect/               # Evolution guidance
|   |-- reseed/                  # Re-derive from first principles
|   |-- upgrade/                 # Apply knowledge base updates
|   +-- add-domain/              # Multi-domain extension
|-- skill-sources/               # 16 generated command templates
|   |-- reduce/                  # Extract insights
|   |-- reflect/                 # Find connections
|   |-- reweave/                 # Backward pass
|   |-- verify/                  # Combined quality check
|   +-- ...                      # 12 more processing commands
|-- agents/
|   +-- knowledge-guide.md       # Pipeline subagent
|-- hooks/
|   |-- hooks.json               # Hook configuration
|   +-- scripts/                 # Hook implementations
|-- generators/
|   |-- claude-md.md             # CLAUDE.md template
|   +-- features/                # 17 composable feature blocks
|-- methodology/                 # 249 research claims
|-- reference/                   # Core reference documents
|   |-- kernel.yaml              # 15 kernel primitives
|   |-- three-spaces.md          # Architecture spec
|   +-- use-case-presets.md      # Pre-validated configs
|-- platforms/                   # Platform-specific adapters
|   |-- claude-code/
|   +-- shared/
|-- presets/                     # Pre-validated configurations
|-- scripts/                     # Utility scripts
+-- README.md

Development

Clone this repo and add the marketplace to Claude Code:

/plugin marketplace add ~/path-to-arscontexta

Install the plugin:

/plugin install arscontexta@agenticnotetaking

Every time you make changes, re-install the plugin:

/plugin uninstall arscontexta@agenticnotetaking
/plugin install arscontexta@agenticnotetaking

Key Files for Contributors


Presets

Three pre-validated configurations for common use cases:

Preset For What You Get
Research Academic work, literature reviews, synthesis Atomic claims, citation tracking, methodology MOCs
Personal Life management, journaling, relationships Reflective notes, goal tracking, relationship MOCs
Experimental Testing, iteration, rapid prototyping Lightweight structure, fast capture, minimal ceremony

Presets provide starting defaults. The derivation engine adapts from there based on your conversation.


Roadmap

Feature Status
Claude Code plugin Available
Marketplace listing Available
Multi-agent processing In progress

Philosophy

The name connects to a tradition. Ars Combinatoria, Ars Memoria, Ars Contexta: the art of context.

Llull's rotating wheels generated truth through combination. Bruno's memory wheels created millions of image combinations. They were external thinking systems -- tools to think with rather than just store in. The missing piece: they required a human mind to do the traversing. Now LLMs can traverse. The wheels can spin again.

Built on Tools for Thought for Agents research.


License

MIT

arscontexta (agenticnotetaking/arscontexta)

Searching Database…

这是什么?Ars Contexta 是一个 Claude Code 插件:它通过一场关于你如何思考和工作的对话,生成个性化的知识系统(“第二大脑”),产出为你的领域量身定制的 markdown 文件、文件夹结构、技能和自动化。
这是一个笔记应用,还是完全不同的东西?它不是带独立界面的应用——它是一个 Claude Code 插件,会生成一个由 wiki 链接连接的纯 markdown 文件库(vault),外加在 Claude Code 内部运行、负责维护这个库的技能和钩子。
怎么让它跑起来?把 marketplace 添加到 Claude Code,安装插件,重启 Claude Code,然后运行 /arscontexta:setup,回答 2-4 个关于你领域的问题,引擎就会生成完整的知识系统;再重启一次以激活钩子和技能。
除了 Claude Code,我还需要装什么?需要 Claude Code v1.0.33 以上版本,外加用于工作区注入和 schema 校验的 CLI 工具 'tree' 和 'ripgrep (rg)';'qmd' 工具可选,用于语义搜索。
配置很快吗,还是有什么坑?配置大约要 20 分钟,而且相当消耗 token,因为引擎在生成输出前要读取 249 条研究论断并对你的领域进行推理,不过这被称为一次性投入。
这是做给谁用的?任何想在 Claude Code 里拥有持久的、领域专属知识库的人;它提供三套现成预设,分别面向学术研究、个人日志和快速实验原型。
这是 Mac 专属插件,还是别处也能用?它是一个用 shell 脚本构建的 Claude Code 插件,没有提到任何操作系统专属代码,所以只要 Claude Code 及其 CLI 依赖(tree、ripgrep)能运行的地方它就能运行,包括 Linux、macOS 和 Windows。
我的知识库会被传到云端吗?不会——一切都以本地纯 markdown 文件存储,没有数据库或云端依赖,你的笔记就留在自己的机器上。
这和我自己做笔记模板有什么不同?引擎从研究原则出发推导出整个结构,而不是套用固定模板——每个文件夹、每个 schema、每项技能都能追溯到 249 条关于认知架构的研究论断之一,而不是样板套路。
什么是“三空间架构”?生成的系统把内容拆分为 self/(智能体的身份和方法论,增长缓慢)、notes/(真正的知识图谱,稳定增长)和 ops/(会话、队列数据等运行状态,不断波动),名称会随你的领域调整。
生成的钩子究竟自动化了什么?四个钩子自动运行:一个在会话开始时注入工作区上下文,一个在每次写入笔记时强制执行 schema,一个异步地把更改自动提交到 git,还有一个在 Claude Code 停止时捕获会话状态。
“6R”处理流水线有哪几步?Record、Reduce、Reflect、Reweave、Verify 和 Rethink——它是对康奈尔笔记法 5R 的扩展,增加了元认知的“Rethink(再思考)”阶段,每一步都通过各自生成的斜杠命令运行。
Size
1.1 MB
Stars
3.5K
Updated
CommitFeb 19
Age
8mo
Commits · 90 Days