world-model-mcp / rules
Cursor rule50 starsChanged 47 days agoMITView on GitHub
This project utilizes vision-memory-mcp to cache visual states, record layout transitions, provide element grounding, and avoid repetitive LLM vision calls.
6 other projects use a version of this.
Adopted by
Most recently taken up by
- putervision/vision-memory-mcpword for word, first seen Oct 8, 2026
- putervision/state-memory-mcpword for word, first seen Sep 28, 2026
- putervision/behavior-mcpword for word, first seen Sep 26, 2026
- putervision/agent-reasoning-mcpword for word, first seen Sep 26, 2026
- putervision/WebCryptword for word, first seen Aug 21, 2026
- putervision/spcword for word, first seen Aug 20, 2026
Other versions6 projects use a version of this.
Word for word · 6
- putervision/state-memory-mcp★ 114100% same
- putervision/vision-memory-mcp★ 48100% same
- putervision/spc★ 41100% same
- putervision/behavior-mcp★ 24100% same
- putervision/WebCrypt★ 24100% same
- putervision/agent-reasoning-mcp★ 22100% same
Edited · 0
None found.
Wrote their own version · 0
None found.
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
Where files are headingNew Cursor rule files have more rules about planning and tracking tasks, and fewer about code style.
Of the Cursor rule files we read, the 4,183 first seen in the last six months, against the older ones: the kind of rule that gained most share, and the kind that lost most. About files like this in general, not this one, and an estimate, since a kind is a pattern in the words.
In this repository16 other files it gives its agents.
- .agents/AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- .github/copilot-instructions.mdCopilot instructions
- .cursor/rules/agent-reasoning-mcp.mdcCursor rule
- .cursor/rules/behavior-mcp.mdcCursor rule
- .cursor/rules/state-memory-mcp.mdcCursor rule
- .cursor/rules/world-model-mcp.mdcCursor rule
- docs/llms.txtllms.txt
- agent-reasoning-mcpSkill
- behavior-mcpSkill
- state-memory-mcpSkill
- video-ingestSkill
- vision-memory-mcpSkill
- webcrypt-mcpSkill
- world-model-mcp-exercisesSkill
- world-model-mcpSkill
The file
We split this vision-memory-mcp.mdc into the rules it gives an agent
9 rules. About 0 are common, 0 are distinctive, and 9 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
Distinctive · estimate
This author's own choices. Worth a look.
9
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 8
Orient: Call get_session_context to align your visual state context at the start of work.
- Very specific: line 9
Search: Call recall_memory (text/image search) before recreating duplicate UI state paths.
- Very specific: line 10
Ingest/Verify: ALWAYS call analyze_screenshot before querying any front-end vision models.
- Very specific: line 11
Cache Hit (
is_known: true): Do NOT use vision models; read the returned description as context and use grounded_elements (selectors, … - Very specific: line 13
Action Target Execution: Use predict_next_action to retrieve grounded_target handles (target_selector, target_coords) for deterministic UI …
- Very specific: line 14
Transitions: Call record_outcome after every click/type/scroll action to construct navigation paths.
- Very specific: line 15
Privacy & Cleanup: Call forget_state to purge sensitive or secret states from storage.
- Very specific: line 36
Google Antigravity (
~/.gemini/config/config.json): Add these rules to your "globalPermissionGrants" -> "allow" list: - Very specific: line 40
VS Code / Cursor IDE (
settings.json): Ensure the agent has execution permissions for command(vision-memory-mcp) and read/write access to …
≈ “Common” is an estimate: at least 1 in 5 of the 6,668 Cursor rule files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
<!-- vision-memory-mcp:start --> ## Visual Memory (vision-memory-mcp) This project utilizes `vision-memory-mcp` to cache visual states, record layout transitions, provide element grounding, and avoid repetitive LLM vision calls. ### 1. Mandatory Workflow & Priority 1. **Orient**: Call `get_session_context` to align your visual state context at the start of work. 2. **Search**: Call `recall_memory` (text/image search) before recreating duplicate UI state paths. 3. **Ingest/Verify**: ALWAYS call `analyze_screenshot` before querying any front-end vision models. - **Cache Hit (`is_known: true`)**: Do NOT use vision models; read the returned `description` as context and use `grounded_elements` (selectors, coordinates) for action target selection. - **Cache Miss (`is_known: false`)**: Query your vision model, then run `analyze_screenshot` with both the image and description to seed the cache. 4. **Action Target Execution**: Use `predict_next_action` to retrieve `grounded_target` handles (`target_selector`, `target_coords`) for deterministic UI clicks and typing. 5. **Transitions**: Call `record_outcome` after every click/type/scroll action to construct navigation paths. 6. **Privacy & Cleanup**: Call `forget_state` to purge sensitive or secret states from storage. ### 2. Tool Reference Summary (15 Core MCP Tools) * `analyze_screenshot`: Ingest screenshot(s) (single or batch via `items`), lookup cache, return layout description and grounded elements. * `recall_memory`: Search visual memory by description query or base64 image query (read-only). * `record_outcome`: Save UI action execution outcomes, transitions, or log visual blockers (`action_type: 'blocker'`). * `get_navigation_paths`: Find path between states using BFS navigation graph. * `predict_next_action`: Predict best next UI action and target coordinates based on transition success rates and AX tree grounding. * `compare_states`: Compare visual states structurally (`has_layout_change`) or compare video recordings (`video_a_id`/`video_b_id`). * `get_session_context`: Fetch aggregated visual context, recent/frequent states, transitions, cache hit ratios, token savings metrics, and server version info. * `manage_snapshot`: Unified snapshot management (`save`, `diff`, `export`, `restore`) for visual checkpoints and regression detection. * `manage_visual_spec`: Visual SDD design contract baseline registration (`set`), live verification (`verify`), and listing (`list`). * `manage_video`: Unified video memory operations for ingestion (`ingest`), semantic search (`search`), and keyframe timelines (`timeline`). * `create_evidence_pack`: Create cryptographic, multi-modal evidence pack linking video keyframes, state graph tasks, and visual proof. * `export_trajectories`: Export multimodal visual transitions and joint workflow trajectories (`json`, `llava`, `qwen2_vl`, `joint`). * `undo_visual_mutation`: Revert accidental state or transition edge ingestions. * `forget_state`: Purge a specific state and vector embedding from storage for privacy. * `wait_for_visual_state`: Poll for target visual state until present or timeout occurs. #### 3. Agent Permissions & Auto-Run Configuration To allow cache query and ingestion commands to run automatically without prompting: * **Google Antigravity (`~/.gemini/config/config.json`)**: Add these rules to your `"globalPermissionGrants"` -> `"allow"` list: * `"command(vision-memory-mcp)"` (Allow running the CLI without parameters prompts) * `"read_file(.*\\.gemini/antigravity/brain/.*)"` (Allow reading captured screenshots) * `"write_file(.*\\.gemini/antigravity/brain/.*)"` (Allow saving visual states) * **VS Code / Cursor IDE (`settings.json`)**: Ensure the agent has execution permissions for `command(vision-memory-mcp)` and read/write access to the workspace's local `.vision-memory-mcp/` cache directory. <!-- vision-memory-mcp:end -->
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

