You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: package.json
+6Lines changed: 6 additions & 0 deletions
Original file line number
Diff line number
Diff line change
@@ -578,6 +578,12 @@
578
578
"default": false,
579
579
"markdownDescription": "Enable filesystem tools (list_directory, read_file, write_file) in the MCP server. These tools allow reading and writing files within the workspace. Restart VSCode to apply changes. It is unlikely that you will want to enable this, because VSCode and Cursor already provide filesystem operations."
580
580
},
581
+
"tlaplus.mcp.enableKnowledgeBaseTools": {
582
+
"type": "boolean",
583
+
"scope": "window",
584
+
"default": false,
585
+
"markdownDescription": "Enable the knowledge-base *tools* in the MCP server in addition to the knowledge-base *resources*. The two tools tlaplus_mcp_knowledge_list and tlaplus_mcp_knowledge_get allow you to search and read TLA+ knowledge-base articles as MCP tools. Restart VSCode to apply the changes. You’ll rarely need to enable this option, since both VSCode and Cursor already support MCP resources."
@@ -625,6 +634,32 @@ When creating TLA+ animations composed of multiple SVG frames, **it is essential
625
634
626
635
If the `viewBox` cannot be determined in advance, perform an initial pass to measure the maximum extents across all frames, then use those dimensions consistently for the final rendering.
627
636
637
+
### 6. Always Display Step Numbers
638
+
639
+
**Every animation frame must include a step number** to help track progression through the state space. The step number should appear in a consistent location across all frames, similar to how page numbers appear in documents.
0 commit comments