agentleFS
KonHKonH/GlobalStrategy/.cursor/rules/unity-plugins-before-work.mdc

GlobalStrategy / rules

Cursor rule3 starsChanged 2 months agoMITView on GitHub

Run the unity-plugins skill before any Unity Editor or MCP work

The file

Files
unity-plugins-before-work.mdc
---
description: Run the unity-plugins skill before any Unity Editor or MCP work
alwaysApply: true
---

# Unity plugin DLLs before Editor work

`Assets/Plugins/Core/*.dll` are gitignored and must be regenerated locally.

**Before the first Unity action in a session** (Unity MCP, `Assets/Scripts/`,
scenes, prefabs, UXML/USS, play mode, or `unity-e2e-run`), read and follow
`.claude/skills/unity-plugins/SKILL.md`.

That means running `python scripts/unity/ensure_plugin_dlls.py` from the
project root and stopping if it fails. Before the first Unity MCP call,
pin the connected Editor to this checkout (see that skill). Do not commit
plugin DLLs.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.