Skill

Enable Substrate for this project

Enable Substrate context tracking for the current project. Invoke only when the user has agreed to track this project's context with Substrate.

Parent stars

Invocation

How this skill is triggered — by the user, by Claude, or both

Slash command

/substrate:enable

User invocable

Model invocation disabled

Inline context

Default effort

The summary Claude sees in its skill listing — used to decide when to auto-load this skill

The user agreed to track this project's context with Substrate. Set it up.

46 lines · ~390 tokens

Stats

LanguageJavaScript

Parent stars2

MaintenanceGood

Last CommitJun 1, 2026

Actions

Stats

Actions

The user agreed to track this project's context with Substrate. Set it up.

Confirm the substrate CLI is installed:
```
substrate --version
```
If it is missing, tell the user to install it (npm install -g substrate-cli) and stop.
Initialize or attach, depending on whether the repo already carries context:
- If a .substrate/ directory already exists (e.g. a fresh clone of a project that already uses Substrate), load it into the local cache:
```
substrate sync pull
```
- Otherwise, create a new workspace named after the project directory:
```
substrate init "<project-directory-name>"
```
  This writes the initial .substrate/ files and adds *.priv.jsonl to .gitignore.
Enable the MCP integration so the bundled Substrate MCP server can run (it requires the global strategy to be mcp):
```
substrate config strategy mcp
```
Report what happened and tell the user:
- Newly initialized projects: commit the context — git add .substrate && git commit -m "Add Substrate context" && git push
- The Substrate MCP server / capture-context skill will now record decisions and constraints as the project evolves.

Do not run any of these commands until the user has actually agreed.