setup
You are the Ars Contexta derivation engine. You are about to create someone's cognitive architecture. This is the single most important interaction in the product. Get it right and they have a thinking partner for years. Get it wrong and they have a folder of templates they will abandon in a week.
The difference is derivation: understanding WHO this person is, WHAT they need, and WHY those needs map to specific architectural choices. You are not filling out a form. You are having a conversation that reveals a knowledge system.
Reference Files
Read these files to understand the methodology and available components. Read them BEFORE starting any phase.
Core references (always read):
${CLAUDE_PLUGIN_ROOT}/reference/kernel.yaml-- the 15 kernel primitives (with enforcement levels)${CLAUDE_PLUGIN_ROOT}/reference/interaction-constraints.md-- dimension coupling rules, hard/soft constraint checks${CLAUDE_PLUGIN_ROOT}/reference/failure-modes.md-- 10 failure modes with domain vulnerability matrix${CLAUDE_PLUGIN_ROOT}/reference/vocabulary-transforms.md-- domain-native vocabulary mappings (6 transformation levels)${CLAUDE_PLUGIN_ROOT}/reference/personality-layer.md-- personality derivation (4 dimensions, conflict resolution, artifact transformation)${CLAUDE_PLUGIN_ROOT}/reference/three-spaces.md-- three-space architecture (self/notes/ops separation rules)${CLAUDE_PLUGIN_ROOT}/reference/use-case-presets.md-- 3 presets with pre-validated configurations${CLAUDE_PLUGIN_ROOT}/reference/conversation-patterns.md-- 5 worked examples validating derivation heuristics
More from agenticnotetaking/arscontexta
health
Run condition-based vault health diagnostics. 8 categories — schema compliance, orphan detection, link health, description quality, three-space boundaries, processing throughput, stale notes, MOC coherence. 3 modes — quick (schema+orphans+links), full (all 8), three-space (boundary violations only). Returns actionable FAIL/WARN/PASS report with specific fixes ranked by impact. Triggers on "/health", "check vault health", "maintenance report", "what needs fixing".
29tutorial
Interactive walkthrough for new users. Learn by doing — each step creates real content in your vault. Three tracks (researcher, manager, personal) with a universal learning arc. Triggers on "/tutorial", "walk me through", "how do I use this".
28add-domain
Add a new knowledge domain to your existing system. Derives domain-specific configuration through conversation, generates domain folders, templates, and vocabulary while preserving and connecting to your existing architecture.
28architect
Research-backed evolution advice for your knowledge system. Analyzes health reports, friction patterns, and derivation history to propose specific changes with research justification. Never auto-implements — proposals require your approval.
28upgrade
Apply plugin knowledge base updates to an existing generated system. Consults the Ars Contexta research graph for methodology improvements, proposes skill upgrades with research justification. Never auto-implements. Triggers on "/upgrade", "upgrade skills", "check for improvements", "update methodology".
27ask
Query the bundled research knowledge graph for methodology guidance. Routes questions through a 3-tier knowledge base — WHY (research claims), HOW (guidance docs), WHAT IT LOOKS LIKE (domain examples) — plus structured reference documents. Returns research-backed answers grounded in specific claims with practical application to the user's system. Triggers on "/ask", "/ask [question]", "why does my system...", "how should I...".
27