@quicktvui/ai 1.1.14 → 1.1.16
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/package.json +1 -1
- package/rules/.claude/commands/create-component.md +1 -1
- package/rules/.claude/commands/create-page.md +1 -1
- package/rules/.claude/commands/create-project.md +1 -1
- package/rules/.claude/commands/lookup-api.md +1 -1
- package/rules/.claude/commands/lookup-css.md +1 -1
- package/rules/.clinerules +20 -1
- package/rules/.cursorrules +20 -1
- package/rules/.github/copilot-instructions.md +20 -1
- package/rules/.windsurfrules +20 -1
- package/rules/AGENTS.md +27 -1
- package/rules/AI_HANDOFF.md +25 -1
- package/rules/CLAUDE.md +26 -1
- package/rules/GEMINI.md +26 -1
package/package.json
CHANGED
package/rules/.clinerules
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
---
|
|
2
2
|
name: .clinerules
|
|
3
|
-
version:
|
|
3
|
+
version: 1.1.14
|
|
4
4
|
---
|
|
5
5
|
|
|
6
6
|
# .clinerules - QuickTVUI AI Development Guide
|
|
@@ -83,6 +83,25 @@ Hard requirements:
|
|
|
83
83
|
- If user asks to launch a specific ES app/version/source, run:
|
|
84
84
|
`quicktvui-ai run-esapp --project <project-path> --pkg <es-package> [options]`
|
|
85
85
|
|
|
86
|
+
## Runtime Debug Data Workflow (CRITICAL)
|
|
87
|
+
|
|
88
|
+
When the user asks AI to inspect runtime logs, native logs, screenshots, or target state:
|
|
89
|
+
|
|
90
|
+
1. Prefer connected `@quicktvui/ai-debug-mcp`
|
|
91
|
+
2. Otherwise use `quicktvui-ai debug-*`
|
|
92
|
+
3. Only ask the user to paste logs manually when neither path is available
|
|
93
|
+
|
|
94
|
+
Required CLI order:
|
|
95
|
+
|
|
96
|
+
1. `quicktvui-ai debug-targets --base-url http://127.0.0.1:38989`
|
|
97
|
+
2. resolve `clientId`
|
|
98
|
+
3. `quicktvui-ai debug-context --client-id <clientId>`
|
|
99
|
+
4. `quicktvui-ai debug-events --client-id <clientId> --limit 100`
|
|
100
|
+
5. `quicktvui-ai debug-native-logs --client-id <clientId> --limit 100`
|
|
101
|
+
6. `quicktvui-ai debug-screenshot --client-id <clientId> --project <project-path>`
|
|
102
|
+
|
|
103
|
+
AI MUST NOT claim it inspected runtime data unless MCP or `quicktvui-ai debug-*` actually returned it.
|
|
104
|
+
|
|
86
105
|
|
|
87
106
|
## Game Loop & Timer Constraints (CRITICAL)
|
|
88
107
|
|
package/rules/.cursorrules
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
---
|
|
2
2
|
name: .cursorrules
|
|
3
|
-
version:
|
|
3
|
+
version: 1.1.14
|
|
4
4
|
---
|
|
5
5
|
|
|
6
6
|
# .cursorrules - QuickTVUI AI Development Guide
|
|
@@ -83,6 +83,25 @@ Hard requirements:
|
|
|
83
83
|
- If user asks to launch a specific ES app/version/source, run:
|
|
84
84
|
`quicktvui-ai run-esapp --project <project-path> --pkg <es-package> [options]`
|
|
85
85
|
|
|
86
|
+
## Runtime Debug Data Workflow (CRITICAL)
|
|
87
|
+
|
|
88
|
+
When the user asks AI to inspect runtime logs, native logs, screenshots, or target state:
|
|
89
|
+
|
|
90
|
+
1. Prefer connected `@quicktvui/ai-debug-mcp`
|
|
91
|
+
2. Otherwise use `quicktvui-ai debug-*`
|
|
92
|
+
3. Only ask the user to paste logs manually when neither path is available
|
|
93
|
+
|
|
94
|
+
Required CLI order:
|
|
95
|
+
|
|
96
|
+
1. `quicktvui-ai debug-targets --base-url http://127.0.0.1:38989`
|
|
97
|
+
2. resolve `clientId`
|
|
98
|
+
3. `quicktvui-ai debug-context --client-id <clientId>`
|
|
99
|
+
4. `quicktvui-ai debug-events --client-id <clientId> --limit 100`
|
|
100
|
+
5. `quicktvui-ai debug-native-logs --client-id <clientId> --limit 100`
|
|
101
|
+
6. `quicktvui-ai debug-screenshot --client-id <clientId> --project <project-path>`
|
|
102
|
+
|
|
103
|
+
AI MUST NOT claim it inspected runtime data unless MCP or `quicktvui-ai debug-*` actually returned it.
|
|
104
|
+
|
|
86
105
|
|
|
87
106
|
## Game Loop & Timer Constraints (CRITICAL)
|
|
88
107
|
|
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
---
|
|
2
2
|
name: copilot-instructions.md
|
|
3
|
-
version: 1.1.
|
|
3
|
+
version: 1.1.16
|
|
4
4
|
---
|
|
5
5
|
|
|
6
6
|
# copilot-instructions.md - QuickTVUI AI Development Guide
|
|
@@ -49,6 +49,25 @@ When asked to create a new QuickTVUI project, you MUST NOT generate a generic Vu
|
|
|
49
49
|
4. **Install Deps**: `yarn install`
|
|
50
50
|
5. **Setup Reminder**: Remind the user to run `npm install -g @quicktvui/cli@latest` and `qui setup` if they haven't configured the environment (see https://quicktvui.com/zh-CN/guide/basic/quick-start.html).
|
|
51
51
|
|
|
52
|
+
## Runtime Debug Data Workflow (CRITICAL)
|
|
53
|
+
|
|
54
|
+
When the task is to inspect a running QuickTVUI app, AI MUST use this priority:
|
|
55
|
+
|
|
56
|
+
1. MCP first, if `@quicktvui/ai-debug-mcp` is connected.
|
|
57
|
+
2. Otherwise use `quicktvui-ai debug-*` commands against `ESDebugServer`.
|
|
58
|
+
3. Only ask the user to paste logs manually if neither tool path is available.
|
|
59
|
+
|
|
60
|
+
Required CLI sequence:
|
|
61
|
+
|
|
62
|
+
- `quicktvui-ai debug-targets --base-url http://127.0.0.1:38989`
|
|
63
|
+
- select `clientId`
|
|
64
|
+
- `quicktvui-ai debug-context --client-id <clientId>`
|
|
65
|
+
- `quicktvui-ai debug-events --client-id <clientId> --limit 100`
|
|
66
|
+
- `quicktvui-ai debug-native-logs --client-id <clientId> --limit 100`
|
|
67
|
+
- `quicktvui-ai debug-screenshot --client-id <clientId> --project <project-path>`
|
|
68
|
+
|
|
69
|
+
AI MUST NOT say it has checked logs/screenshots unless one of those MCP/CLI reads actually succeeded.
|
|
70
|
+
|
|
52
71
|
|
|
53
72
|
## Game Loop & Timer Constraints (CRITICAL)
|
|
54
73
|
|
package/rules/.windsurfrules
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
---
|
|
2
2
|
name: .windsurfrules
|
|
3
|
-
version:
|
|
3
|
+
version: 1.1.14
|
|
4
4
|
---
|
|
5
5
|
|
|
6
6
|
# .windsurfrules - QuickTVUI AI Development Guide
|
|
@@ -83,6 +83,25 @@ Hard requirements:
|
|
|
83
83
|
- If user asks to launch a specific ES app/version/source, run:
|
|
84
84
|
`quicktvui-ai run-esapp --project <project-path> --pkg <es-package> [options]`
|
|
85
85
|
|
|
86
|
+
## Runtime Debug Data Workflow (CRITICAL)
|
|
87
|
+
|
|
88
|
+
When the user asks AI to inspect runtime logs, native logs, screenshots, or target state:
|
|
89
|
+
|
|
90
|
+
1. Prefer connected `@quicktvui/ai-debug-mcp`
|
|
91
|
+
2. Otherwise use `quicktvui-ai debug-*`
|
|
92
|
+
3. Only ask the user to paste logs manually when neither path is available
|
|
93
|
+
|
|
94
|
+
Required CLI order:
|
|
95
|
+
|
|
96
|
+
1. `quicktvui-ai debug-targets --base-url http://127.0.0.1:38989`
|
|
97
|
+
2. resolve `clientId`
|
|
98
|
+
3. `quicktvui-ai debug-context --client-id <clientId>`
|
|
99
|
+
4. `quicktvui-ai debug-events --client-id <clientId> --limit 100`
|
|
100
|
+
5. `quicktvui-ai debug-native-logs --client-id <clientId> --limit 100`
|
|
101
|
+
6. `quicktvui-ai debug-screenshot --client-id <clientId> --project <project-path>`
|
|
102
|
+
|
|
103
|
+
AI MUST NOT claim it inspected runtime data unless MCP or `quicktvui-ai debug-*` actually returned it.
|
|
104
|
+
|
|
86
105
|
|
|
87
106
|
## Game Loop & Timer Constraints (CRITICAL)
|
|
88
107
|
|
package/rules/AGENTS.md
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
---
|
|
2
2
|
name: AGENTS.md
|
|
3
|
-
version: 1.1.
|
|
3
|
+
version: 1.1.16
|
|
4
4
|
---
|
|
5
5
|
|
|
6
6
|
# AGENTS.md - QuickTVUI AI Development Guide
|
|
@@ -115,6 +115,32 @@ Hard requirements:
|
|
|
115
115
|
- If user asks to launch a specific ES app/version/source, run:
|
|
116
116
|
`quicktvui-ai run-esapp --project <project-path> --pkg <es-package> [options]`
|
|
117
117
|
|
|
118
|
+
## Runtime Debug Data Workflow (CRITICAL)
|
|
119
|
+
|
|
120
|
+
When the user asks AI to inspect runtime logs, native logs, screenshots, recent errors, or current target state for a running QuickTVUI app, AI MUST use this priority:
|
|
121
|
+
|
|
122
|
+
1. Prefer MCP resources/tools when `@quicktvui/ai-debug-mcp` is connected.
|
|
123
|
+
2. If MCP is unavailable but shell/CLI execution is available, AI MUST use `quicktvui-ai debug-*` commands against the running `ESDebugServer`.
|
|
124
|
+
3. Only if neither MCP nor CLI execution is available may AI ask the user to paste logs manually.
|
|
125
|
+
|
|
126
|
+
Required non-MCP command order:
|
|
127
|
+
|
|
128
|
+
1. `quicktvui-ai debug-targets --base-url http://127.0.0.1:38989`
|
|
129
|
+
2. Choose `clientId`
|
|
130
|
+
- If only one target exists, AI MAY use it directly.
|
|
131
|
+
- If multiple targets exist, AI MUST ask user to confirm the right `clientId`.
|
|
132
|
+
3. `quicktvui-ai debug-context --client-id <clientId>`
|
|
133
|
+
4. `quicktvui-ai debug-events --client-id <clientId> --limit 100`
|
|
134
|
+
5. `quicktvui-ai debug-native-logs --client-id <clientId> --limit 100`
|
|
135
|
+
6. `quicktvui-ai debug-screenshot --client-id <clientId> --project <project-path>`
|
|
136
|
+
|
|
137
|
+
Hard requirements:
|
|
138
|
+
|
|
139
|
+
- AI MUST NOT claim it has inspected Chrome logs, Android native logs, target context, or screenshots unless MCP or `quicktvui-ai debug-*` actually returned data.
|
|
140
|
+
- If `debug-targets` returns an empty list, AI MUST clearly state that no active `ESDebugServer /ai/targets` are available yet.
|
|
141
|
+
- If `debug-native-logs` or `debug-screenshot` fails, AI MUST report the concrete command/error instead of fabricating fallback observations.
|
|
142
|
+
- When user asks for a screenshot and CLI mode is used, AI SHOULD prefer the file path returned by `quicktvui-ai debug-screenshot` rather than asking the user to locate the image manually.
|
|
143
|
+
|
|
118
144
|
## 🔥 ARCHITECTURAL GOTCHAS (CRITICAL)
|
|
119
145
|
|
|
120
146
|
AI assistants frequently fail by applying traditional Web paradigms to QuickTVUI. **You MUST memorize these constraints**:
|
package/rules/AI_HANDOFF.md
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
---
|
|
2
2
|
name: AI_HANDOFF.md
|
|
3
|
-
version: 1.1.
|
|
3
|
+
version: 1.1.16
|
|
4
4
|
---
|
|
5
5
|
|
|
6
6
|
# QuickTVUI AI 集成 - 工作交接文档
|
|
@@ -61,6 +61,30 @@ AI 在编写业务逻辑时,极易带入传统 Web 开发习惯导致严重报
|
|
|
61
61
|
- 不得在未检查 CLI 能力前直接进入 `yarn dev` / 手写 `adb` 流程。
|
|
62
62
|
- 若某一步骤在 `quicktvui-ai-cli` 中不存在对应命令,AI 必须先明确说明“CLI 暂不支持该步骤”,再走手工兜底流程。
|
|
63
63
|
|
|
64
|
+
## Runtime Debug Data Workflow (CRITICAL)
|
|
65
|
+
|
|
66
|
+
对于“读取运行中应用调试数据”的任务,后续 AI 必须统一遵循以下优先级:
|
|
67
|
+
|
|
68
|
+
1. 优先使用 `@quicktvui/ai-debug-mcp`
|
|
69
|
+
2. 没有 MCP 时,使用 `quicktvui-ai debug-*`
|
|
70
|
+
3. 两者都不可用时,才要求用户手工提供日志或截图
|
|
71
|
+
|
|
72
|
+
当前约定的非 MCP 命令链路:
|
|
73
|
+
|
|
74
|
+
1. `quicktvui-ai debug-targets --base-url http://127.0.0.1:38989`
|
|
75
|
+
2. 选择或确认 `clientId`
|
|
76
|
+
3. `quicktvui-ai debug-context --client-id <clientId>`
|
|
77
|
+
4. `quicktvui-ai debug-events --client-id <clientId> --limit 100`
|
|
78
|
+
5. `quicktvui-ai debug-native-logs --client-id <clientId> --limit 100`
|
|
79
|
+
6. `quicktvui-ai debug-screenshot --client-id <clientId> --project <project-path>`
|
|
80
|
+
|
|
81
|
+
接手注意事项:
|
|
82
|
+
|
|
83
|
+
- 未通过 MCP 或 `quicktvui-ai debug-*` 真正读取到数据前,不得宣称“已检查运行时日志/截图”
|
|
84
|
+
- `debug-targets` 返回空数组时,应先回到 run/dev 链路,确认 `ESDebugServer /ai/targets` 已建立
|
|
85
|
+
- `debug-screenshot` 默认会把图片写到 `<project>/.quicktvui-ai/debug-screenshots/`,后续 AI 应优先使用命令返回的 `savedTo` 路径
|
|
86
|
+
- `debug-native-logs` 与 `debug-screenshot` 的失败信息应直接向用户透明披露,不要二次包装成模糊描述
|
|
87
|
+
|
|
64
88
|
---
|
|
65
89
|
|
|
66
90
|
## 一、项目背景
|
package/rules/CLAUDE.md
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
---
|
|
2
2
|
name: CLAUDE.md
|
|
3
|
-
version: 1.1.
|
|
3
|
+
version: 1.1.16
|
|
4
4
|
---
|
|
5
5
|
|
|
6
6
|
# QuickTVUI - AI 开发指南
|
|
@@ -115,6 +115,31 @@ Hard requirements:
|
|
|
115
115
|
- If user asks to launch a specific ES app/version/source, run:
|
|
116
116
|
`quicktvui-ai run-esapp --project <project-path> --pkg <es-package> [options]`
|
|
117
117
|
|
|
118
|
+
## Runtime Debug Data Workflow (CRITICAL)
|
|
119
|
+
|
|
120
|
+
当用户要求 AI 检查运行中应用的 console/network/exception、Android native logs、截图或当前 target 状态时,AI 必须使用以下优先级:
|
|
121
|
+
|
|
122
|
+
1. 优先使用已连接的 `@quicktvui/ai-debug-mcp`
|
|
123
|
+
2. 如果没有 MCP,但具备 shell/CLI 能力,则必须使用 `quicktvui-ai debug-*`
|
|
124
|
+
3. 只有 MCP 和 CLI 都不可用时,才允许要求用户手工粘贴日志
|
|
125
|
+
|
|
126
|
+
非 MCP 场景下,必须按以下顺序执行:
|
|
127
|
+
|
|
128
|
+
1. `quicktvui-ai debug-targets --base-url http://127.0.0.1:38989`
|
|
129
|
+
2. 选择 `clientId`
|
|
130
|
+
- 仅有一个 target 时可直接使用
|
|
131
|
+
- 多个 target 时必须让用户确认正确的 `clientId`
|
|
132
|
+
3. `quicktvui-ai debug-context --client-id <clientId>`
|
|
133
|
+
4. `quicktvui-ai debug-events --client-id <clientId> --limit 100`
|
|
134
|
+
5. `quicktvui-ai debug-native-logs --client-id <clientId> --limit 100`
|
|
135
|
+
6. `quicktvui-ai debug-screenshot --client-id <clientId> --project <project-path>`
|
|
136
|
+
|
|
137
|
+
硬约束:
|
|
138
|
+
|
|
139
|
+
- AI 未通过 MCP 或 `quicktvui-ai debug-*` 实际读取到数据前,不得声称自己已经检查过运行时日志、native logs 或截图
|
|
140
|
+
- `debug-targets` 为空时,必须明确说明当前 `ESDebugServer /ai/targets` 还没有可读 target
|
|
141
|
+
- `debug-native-logs` 或 `debug-screenshot` 失败时,必须原样报告命令和错误,不得编造兜底结论
|
|
142
|
+
|
|
118
143
|
## 🔥 核心架构避坑指南 (ARCHITECTURAL GOTCHAS)
|
|
119
144
|
|
|
120
145
|
AI 在编写业务逻辑时,极易带入传统 Web 开发习惯导致严重报错,**必须牢记以下框架特性**:
|
package/rules/GEMINI.md
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
---
|
|
2
2
|
name: GEMINI.md
|
|
3
|
-
version: 1.1.
|
|
3
|
+
version: 1.1.16
|
|
4
4
|
---
|
|
5
5
|
|
|
6
6
|
# GEMINI.md - QuickTVUI AI 开发指南
|
|
@@ -106,6 +106,31 @@ Hard requirements:
|
|
|
106
106
|
- If user asks to launch a specific ES app/version/source, run:
|
|
107
107
|
`quicktvui-ai run-esapp --project <project-path> --pkg <es-package> [options]`
|
|
108
108
|
|
|
109
|
+
## Runtime Debug Data Workflow (CRITICAL)
|
|
110
|
+
|
|
111
|
+
When the user asks AI to inspect runtime console logs, network/exception events, Android native logs, screenshots, or current target state, AI MUST use this priority:
|
|
112
|
+
|
|
113
|
+
1. Prefer connected `@quicktvui/ai-debug-mcp`
|
|
114
|
+
2. If MCP is unavailable but shell/CLI is available, use `quicktvui-ai debug-*`
|
|
115
|
+
3. Only ask the user to paste logs manually when both MCP and CLI paths are unavailable
|
|
116
|
+
|
|
117
|
+
Required non-MCP order:
|
|
118
|
+
|
|
119
|
+
1. `quicktvui-ai debug-targets --base-url http://127.0.0.1:38989`
|
|
120
|
+
2. Resolve `clientId`
|
|
121
|
+
- use directly when only one target exists
|
|
122
|
+
- ask the user to confirm when multiple targets exist
|
|
123
|
+
3. `quicktvui-ai debug-context --client-id <clientId>`
|
|
124
|
+
4. `quicktvui-ai debug-events --client-id <clientId> --limit 100`
|
|
125
|
+
5. `quicktvui-ai debug-native-logs --client-id <clientId> --limit 100`
|
|
126
|
+
6. `quicktvui-ai debug-screenshot --client-id <clientId> --project <project-path>`
|
|
127
|
+
|
|
128
|
+
Hard requirements:
|
|
129
|
+
|
|
130
|
+
- AI MUST NOT claim it inspected runtime data unless MCP or `quicktvui-ai debug-*` actually returned that data
|
|
131
|
+
- If `debug-targets` is empty, AI MUST say that `ESDebugServer /ai/targets` is still empty
|
|
132
|
+
- If `debug-native-logs` or `debug-screenshot` fails, AI MUST report the real command/error instead of inventing fallback observations
|
|
133
|
+
|
|
109
134
|
---
|
|
110
135
|
|
|
111
136
|
## 🔥 核心架构避坑指南 (ARCHITECTURAL GOTCHAS)
|