From scholialang
Use when the user wants Claude Code to capture, inspect, summarize, search, compact, export, lint, or reason from explicit local Scholialang DAG traces. Also use when the user asks about Scholialang atoms, relations, operators, examples, validator rules, or local graph history.
How this skill is triggered — by the user, by Claude, or both
Slash command
/scholialang:scholialangThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Use the `scholialang` MCP server to record, retrieve, import, export, and
Use the scholialang MCP server to record, retrieve, import, export, and
validate explicit work traces as local SQLite-backed DAGs. Atoms are nodes;
references, evidence, implications, contradictions, and retractions are edges.
These traces are user-facing work artifacts, not hidden chain-of-thought.
The packaged server exposes Scholialang MCP tools with underscore names, such as
scholia_dag_start. Dotted names such as scholia.dag_start are legacy aliases
for hosts that allow dots in tool names.
This plugin auto-emits by default, per project. On Claude Code the SessionStart
hook calls scholia_dag_ensure_session (host claude-code) to open or resume a
per-project session DAG and injects its dag_id into context; the SessionEnd
hook appends a closing Summary. Your job in between is to append semantic atoms
at meaningful boundaries with scholia_dag_add_atom (using that dag_id):
Observation for command/file/query results that matter.Deciding at branch points, naming the chosen path.Finding for conclusions; Action for durable external changes.Contradiction / Retract when something invalidates a prior atom.Concluding atom at the end, linked back to the trace Goal.Link atoms with links (derived_from, supports, refutes, depends_on).
Each session is its own DAG, tagged host:<host> and session:<id>, so the same
project used from both Claude Code and Codex yields distinct, tool-labeled traces
in one project bucket. scholia_dag_ensure_session is idempotent — calling it
again returns the same session DAG rather than creating a duplicate.
Opt-out (one switch, honored by every host): set SCHOLIA_AUTOEMIT=0
(or false/off) to disable globally, or create a .scholia-off file in the
project root to disable for that repo. Explicit, user-requested tracing still
works when auto-emit is off.
scholia_dag_start for the current project if there is no active DAG. scholia_dag_start creates the trace-level Goal atom from the objective.scholia_dag_add_atom with links whenever the new atom depends on, supports, refutes, implies, contradicts, or retracts prior atoms.Concluding for final or checkpoint conclusions, especially when closing a Goal; link it back to the goal with derived_from or refers and include the goal status in the summary/content.scholia_lint_snippet when the user pastes a Scholia trace and asks if it's valid, or before storing a fragment that will be referenced elsewhere. The default mode='full' runs the complete v0.6 grammar — closed-set atom kinds, canonical_id well-formedness, reference completeness, decision closure, action recording, hypothesis evaluation, retract consistency, constraint respect, goal declaration, operator vocabulary, v0.3.1 optional field shapes, and Concluding closure rules with warnings.mode='tag_balance' for fast syntactic-only checks when full grammar isn't needed.scholia_lint_trace when you need a per-rule breakdown for CI gates, dashboards, or "which rule failed" questions — the response includes errors_by_rule and counts_by_rule keyed on the canonical RULE_NAMES.scholia_dag_summary, scholia_dag_frontier, scholia_dag_neighbors, scholia_dag_search, and scholia_dag_list before reading full graph content.scholia_dag_read with bounded limit and avoid include_nodes=true unless exact atoms are needed.scholia_dag_compact before carrying old work across threads or long-running sessions.~/.scholialang/scholialang.sqlite3; only mention or inspect it when the user asks about storage/debugging.When a tool accepts project_path, pass the current repository or workspace
root. If unavailable, omit it and the MCP server will use its global store.
scholia_dag_start with the project path, title, objective, and tags; use the returned goal_atom as the trace goal.scholia_dag_add_atom after important observations, decisions, and actions.scholia_dag_add_atom with kind Concluding when a goal or checkpoint is closed.scholia_dag_link when a relationship becomes clear after both nodes exist.scholia_lint_snippet (mode='full') before persisting a trace fragment the user authored.scholia_dag_frontier and scholia_dag_summary when resuming work.scholia_dag_neighbors for focused recall around one atom.scholia_dag_search to locate prior decisions or findings.scholia_dag_export only when the user asks for a sharable artifact.Provides UI/UX resources: 50+ styles, color palettes, font pairings, guidelines, charts for web/mobile across React, Next.js, Vue, Svelte, Tailwind, React Native, Flutter. Aids planning, building, reviewing interfaces.
Fetches up-to-date documentation from Context7 for libraries and frameworks like React, Next.js, Prisma. Use for setup questions, API references, and code examples.
npx claudepluginhub dougfirlabs/scholialang-mcp --plugin scholialang