feat: 实现用户画像、占卜历史与后端用户管理模块
This commit is contained in:
@@ -0,0 +1,24 @@
|
||||
---
|
||||
description: Run an Android automation test through Midscene Skills
|
||||
---
|
||||
|
||||
You are running an Android mobile UI automation task for this project.
|
||||
|
||||
Interpret the user arguments as the exact natural-language test goal:
|
||||
|
||||
$ARGUMENTS
|
||||
|
||||
Execution requirements:
|
||||
|
||||
1. Verify that adb is available and that at least one Android device or emulator is connected.
|
||||
2. If no Android target is available, stop and report that the Android automation prerequisite is missing.
|
||||
3. Use the installed Midscene Android skill workflow to execute the requested UI actions on the Android emulator or device.
|
||||
4. Prefer acting on the current development build of the app when applicable.
|
||||
5. Capture visible evidence during the run when useful, especially the final screen state.
|
||||
6. At the end, report:
|
||||
- whether the flow succeeded
|
||||
- the exact failing step if any
|
||||
- what was observed on screen
|
||||
- what should be fixed next if this looked like a product bug
|
||||
|
||||
Do not only describe a test plan. Actually perform the automation when prerequisites are available.
|
||||
@@ -0,0 +1,24 @@
|
||||
---
|
||||
description: Run an iOS automation test through Midscene Skills
|
||||
---
|
||||
|
||||
You are running an iOS mobile UI automation task for this project.
|
||||
|
||||
Interpret the user arguments as the exact natural-language test goal:
|
||||
|
||||
$ARGUMENTS
|
||||
|
||||
Execution requirements:
|
||||
|
||||
1. Verify that WebDriverAgent is reachable at http://localhost:8100/status before doing any iOS action.
|
||||
2. If WebDriverAgent is not ready, stop and report that the iOS automation prerequisite is missing.
|
||||
3. Use the installed Midscene iOS skill workflow to execute the requested UI actions on the iOS simulator or device.
|
||||
4. Prefer acting on the current development build of the app when applicable.
|
||||
5. Capture visible evidence during the run when useful, especially the final screen state.
|
||||
6. At the end, report:
|
||||
- whether the flow succeeded
|
||||
- the exact failing step if any
|
||||
- what was observed on screen
|
||||
- what should be fixed next if this looked like a product bug
|
||||
|
||||
Do not only describe a test plan. Actually perform the automation when prerequisites are available.
|
||||
@@ -0,0 +1,10 @@
|
||||
{
|
||||
"$schema": "https://opencode.ai/config.json",
|
||||
"mcp": {
|
||||
"supabase": {
|
||||
"type": "remote",
|
||||
"enabled": true,
|
||||
"url": "http://localhost:8001/mcp"
|
||||
}
|
||||
}
|
||||
}
|
||||
Reference in New Issue
Block a user