Cache a rule extraction back onto a container
devvault_write_rulesDistill DevVault containers with no cached rules into reusable imperatives so future sessions avoid re-derivation; keep links/examples, don't overwrite hand-written rules.
Instructions
After reading a container whose result said it has no cached rules, distil it and save the result here so no future session has to re-derive it. IMPORTANT: extract EVERY actionable rule in the container, not only the ones relevant to what you are building right now — these rules are reused for unrelated tasks, and a narrow extraction is worse than none. One imperative rule per line. Drop background and explanation; keep code examples and links. Rules a user wrote by hand are never overwritten.
Tool call template
Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {
"container_id": "<container_id>",
"rules": "<rules>"
},
"name": "devvault_write_rules"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| rules | Yes | One imperative rule per line, task-agnostic. | |
| container_id | Yes |