资源整理，开始开发

.agents/skills/vision-project-rules/SKILL.md

@@ -0,0 +1,35 @@
+---
+name: vision-project-rules
+description: Use for any development or maintenance task in the Vision Unity project. Enforce strict request scope by allowing only work the user explicitly requested and preventing unrequested edits, cleanup, testing, UI actions, or external side effects.
+---
+
+# Vision Project Rules
+
+## Strict Request Scope
+
+The user's latest explicit request defines the entire authorized scope. Previous context may explain the request but does not authorize additional work.
+
+- Do only what is necessary to complete and verify the requested task.
+- Do not infer permission from available tools, prior tasks, similar requests, repository state, or the ability to make another change.
+- Do not add unrequested features, refactors, formatting changes, dependency changes, file moves, cleanup, tests, UI actions, logs, or external side effects.
+- Do not fix unrelated problems discovered during the task. Report them only when they directly affect the requested result.
+- If an extra action would materially change files, project state, Unity state, or external systems, stop before taking it and ask.
+
+## Minimal Verification
+
+- Verification is allowed only when it directly proves the requested task succeeded.
+- For a plugin installation, import the requested files, refresh and compile Unity, check installation errors, and verify the registered entry exists when applicable.
+- Do not open the plugin window, run its features, inspect screenshots, or exercise unrelated workflows unless the user explicitly asks for that verification.
+- Stop once the requested task is complete; do not continue into optimization, cleanup, or follow-up work.
+
+## Inspect Only What Is Needed
+
+- Use read-only inspection only to understand the exact files, commands, or state required for the request.
+- Do not browse broad areas of the project merely because they may be useful later.
+- Preserve existing user changes and never overwrite or delete unrelated work.
+
+## Conflict Handling
+
+- A new explicit instruction replaces the previous scope.
+- When the boundary is genuinely unclear and the next action is consequential, ask one concise question before acting.
+- Never treat silence, approval of a previous task, or a general request for help as permission for a related unrequested action.