fix(prefab): 修复预制体编辑模式的保存与退出,使用原生 scene://edit-mode 接口替代无效的 IPC 广播,更新相关使用文档与安全规定

This commit is contained in:
火焰库拉
2026-03-08 11:33:28 +08:00
parent fb4025e50b
commit 2573c0f478
15 changed files with 443 additions and 13 deletions

View File

@@ -0,0 +1,18 @@
---
description: Create a unified implementation plan.
---
## User Input
$ARGUMENTS
## Instructions
1. **Read**: Load the `spec.md` provided by the user.
2. **Draft Plan**:
* Create/Update **ONE file**: `specs/[feature_name]/plan.md`.
* **Section 1: Architecture**: Briefly list changed files and data models.
* **Section 2: Step-by-Step**: List the implementation steps (Todo list) directly in this file.
3. **Format**:
* Use checkboxes `- [ ]` for the steps so they are clickable.
* Mark steps as `[Frontend]` or `[Backend]`.
4. **Constraint**: Do NOT create `tasks.md`. Keep it all in `plan.md`.

View File

@@ -0,0 +1,19 @@
---
description: Create a single, rigorous feature spec.
---
## User Input
$ARGUMENTS
## Instructions
1. **Context**: Read `memory/constitution.md` and any attached images.
2. **Draft Spec**:
* Create/Update **ONE file only**: `specs/[feature_name]/spec.md`.
* **Do NOT** create a checklist file.
* **Do NOT** create a separate analysis file.
3. **Content**:
* Include "Visual Requirements" (from images).
* Include "Functional Requirements".
* Include "Edge Cases" directly in the spec as a section.
4. **Output**: Show the `spec.md` artifact.

View File

@@ -0,0 +1,13 @@
---
description: Build the feature from the plan.
---
## Instructions
1. **Read**: Open `specs/[feature_name]/plan.md`.
2. **Execute**:
* Look for the **Step-by-Step** section with checkboxes.
* Execute the unchecked items `- [ ]`.
3. **Vibe Check**:
* After every 2-3 steps, verify the code visually.
* Mark steps as `- [x]` in `plan.md` as you finish them.

View File

@@ -0,0 +1,14 @@
---
description: Clean up legacy code before feature work.
---
## User Input
$ARGUMENTS
## Instructions
1. **Audit**: Scan the target directory `$ARGUMENTS`.
2. **Constitution Check**: Compare against `/memory/constitution.md`.
3. **Refactor**: Apply modern patterns (e.g., "Convert Promises to Async/Await") WITHOUT changing business logic.
4. **Verify**: Run existing tests to ensure no regression.

View File

@@ -0,0 +1,17 @@
---
description: Visual and logic verification of the feature.
---
## Antigravity QA Instructions
1. **Environment**: Spin up the app in the Integrated Terminal/Browser.
2. **Visual Audit**:
- Navigate to the new feature.
- **TAKE SCREENSHOT**.
- Compare screenshot to the `spec.md` requirements.
- Report: "Match" or "Discrepancy".
3. **Logic Audit**:
- Run the "Happy Path" user journey.
- Check console logs for errors.
4. **Report**:
- Generate a **Release Readiness Artifact**.