@quicktvui/ai 1.1.5 → 1.1.6

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.
Files changed (7) hide show
  1. package/package.json +1 -1
  2. package/rules/.clinerules +7 -0
  3. package/rules/.cursorrules +7 -0
  4. package/rules/.windsurfrules +7 -0
  5. package/rules/AGENTS.md +7 -0
  6. package/rules/CLAUDE.md +7 -0
  7. package/rules/GEMINI.md +7 -0
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@quicktvui/ai",
3
- "version": "1.1.5",
3
+ "version": "1.1.6",
4
4
  "description": "QuickTVUI AI 开发规范与脚手架注入工具",
5
5
  "main": "index.js",
6
6
  "scripts": {
package/rules/.clinerules CHANGED
@@ -65,6 +65,13 @@ Hard requirements:
65
65
  and fallback:
66
66
  `adb -s <serial> shell dumpsys package <runtime-package> | rg 'eskit\\.sdk\\.core\\.ui\\.BrowserProxyActivity|android.intent.action.VIEW|scheme=esapp|ES_ACTION_LAUNCH'`
67
67
  - If the package/activity capability check fails, AI MUST stop run flow and ask user to reinstall runtime or provide the correct runtime package.
68
+ - For runtime capability inventory tasks (e.g. "列出所有支持 esapp:// 拉起的 APK"), AI MUST query intent handlers first and MUST NOT use package-name keyword grep as primary evidence.
69
+ - Preferred inventory command:
70
+ `adb -s <serial> shell "pm query-activities --brief --components -a android.intent.action.VIEW -d 'esapp://action/start?from=cmd&pkg=es.test' -c android.intent.category.BROWSABLE"`
71
+ - If `cmd package query-intent-activities` is unavailable (`Unknown command`), AI MUST fallback to `pm query-activities` immediately and continue.
72
+ - Inventory fallback command:
73
+ `adb -s <serial> shell "pm query-activities --brief --components -a android.intent.action.VIEW -d 'esapp://' -c android.intent.category.BROWSABLE"`
74
+ - For each resolved package, AI MUST output: component, package path (`pm path <pkg>`), and version (`dumpsys package <pkg> | grep -m 1 versionName`).
68
75
  - After `quicktvui-ai run-dev --project <project-path>` reaches runtime launcher page, AI MUST send a confirm action (`adb shell input keyevent 23` or `66`, or equivalent click) on the runtime start button so runtime pulls/loads the dev bundle.
69
76
  - AI MUST NOT stop at launcher page before triggering that confirm action, and MUST verify launch/bundle load result from logs or foreground activity status.
70
77
  - If user asks to launch a specific ES app/version/source, run:
package/rules/.cursorrules CHANGED
@@ -65,6 +65,13 @@ Hard requirements:
65
65
  and fallback:
66
66
  `adb -s <serial> shell dumpsys package <runtime-package> | rg 'eskit\\.sdk\\.core\\.ui\\.BrowserProxyActivity|android.intent.action.VIEW|scheme=esapp|ES_ACTION_LAUNCH'`
67
67
  - If the package/activity capability check fails, AI MUST stop run flow and ask user to reinstall runtime or provide the correct runtime package.
68
+ - For runtime capability inventory tasks (e.g. "列出所有支持 esapp:// 拉起的 APK"), AI MUST query intent handlers first and MUST NOT use package-name keyword grep as primary evidence.
69
+ - Preferred inventory command:
70
+ `adb -s <serial> shell "pm query-activities --brief --components -a android.intent.action.VIEW -d 'esapp://action/start?from=cmd&pkg=es.test' -c android.intent.category.BROWSABLE"`
71
+ - If `cmd package query-intent-activities` is unavailable (`Unknown command`), AI MUST fallback to `pm query-activities` immediately and continue.
72
+ - Inventory fallback command:
73
+ `adb -s <serial> shell "pm query-activities --brief --components -a android.intent.action.VIEW -d 'esapp://' -c android.intent.category.BROWSABLE"`
74
+ - For each resolved package, AI MUST output: component, package path (`pm path <pkg>`), and version (`dumpsys package <pkg> | grep -m 1 versionName`).
68
75
  - After `quicktvui-ai run-dev --project <project-path>` reaches runtime launcher page, AI MUST send a confirm action (`adb shell input keyevent 23` or `66`, or equivalent click) on the runtime start button so runtime pulls/loads the dev bundle.
69
76
  - AI MUST NOT stop at launcher page before triggering that confirm action, and MUST verify launch/bundle load result from logs or foreground activity status.
70
77
  - If user asks to launch a specific ES app/version/source, run:
package/rules/.windsurfrules CHANGED
@@ -65,6 +65,13 @@ Hard requirements:
65
65
  and fallback:
66
66
  `adb -s <serial> shell dumpsys package <runtime-package> | rg 'eskit\\.sdk\\.core\\.ui\\.BrowserProxyActivity|android.intent.action.VIEW|scheme=esapp|ES_ACTION_LAUNCH'`
67
67
  - If the package/activity capability check fails, AI MUST stop run flow and ask user to reinstall runtime or provide the correct runtime package.
68
+ - For runtime capability inventory tasks (e.g. "列出所有支持 esapp:// 拉起的 APK"), AI MUST query intent handlers first and MUST NOT use package-name keyword grep as primary evidence.
69
+ - Preferred inventory command:
70
+ `adb -s <serial> shell "pm query-activities --brief --components -a android.intent.action.VIEW -d 'esapp://action/start?from=cmd&pkg=es.test' -c android.intent.category.BROWSABLE"`
71
+ - If `cmd package query-intent-activities` is unavailable (`Unknown command`), AI MUST fallback to `pm query-activities` immediately and continue.
72
+ - Inventory fallback command:
73
+ `adb -s <serial> shell "pm query-activities --brief --components -a android.intent.action.VIEW -d 'esapp://' -c android.intent.category.BROWSABLE"`
74
+ - For each resolved package, AI MUST output: component, package path (`pm path <pkg>`), and version (`dumpsys package <pkg> | grep -m 1 versionName`).
68
75
  - After `quicktvui-ai run-dev --project <project-path>` reaches runtime launcher page, AI MUST send a confirm action (`adb shell input keyevent 23` or `66`, or equivalent click) on the runtime start button so runtime pulls/loads the dev bundle.
69
76
  - AI MUST NOT stop at launcher page before triggering that confirm action, and MUST verify launch/bundle load result from logs or foreground activity status.
70
77
  - If user asks to launch a specific ES app/version/source, run:
package/rules/AGENTS.md CHANGED
@@ -67,6 +67,13 @@ Hard requirements:
67
67
  and fallback:
68
68
  `adb -s <serial> shell dumpsys package <runtime-package> | rg 'eskit\\.sdk\\.core\\.ui\\.BrowserProxyActivity|android.intent.action.VIEW|scheme=esapp|ES_ACTION_LAUNCH'`
69
69
  - If the package/activity capability check fails, AI MUST stop run flow and ask user to reinstall runtime or provide the correct runtime package.
70
+ - For runtime capability inventory tasks (e.g. "列出所有支持 esapp:// 拉起的 APK"), AI MUST query intent handlers first and MUST NOT use package-name keyword grep as primary evidence.
71
+ - Preferred inventory command:
72
+ `adb -s <serial> shell "pm query-activities --brief --components -a android.intent.action.VIEW -d 'esapp://action/start?from=cmd&pkg=es.test' -c android.intent.category.BROWSABLE"`
73
+ - If `cmd package query-intent-activities` is unavailable (`Unknown command`), AI MUST fallback to `pm query-activities` immediately and continue.
74
+ - Inventory fallback command:
75
+ `adb -s <serial> shell "pm query-activities --brief --components -a android.intent.action.VIEW -d 'esapp://' -c android.intent.category.BROWSABLE"`
76
+ - For each resolved package, AI MUST output: component, package path (`pm path <pkg>`), and version (`dumpsys package <pkg> | grep -m 1 versionName`).
70
77
  - After `quicktvui-ai run-dev --project <project-path>` reaches runtime launcher page, AI MUST send a confirm action (`adb shell input keyevent 23` or `66`, or equivalent click) on the runtime start button so runtime pulls/loads the dev bundle.
71
78
  - AI MUST NOT stop at launcher page before triggering that confirm action, and MUST verify launch/bundle load result from logs or foreground activity status.
72
79
  - If user asks to launch a specific ES app/version/source, run:
package/rules/CLAUDE.md CHANGED
@@ -67,6 +67,13 @@ Hard requirements:
67
67
  and fallback:
68
68
  `adb -s <serial> shell dumpsys package <runtime-package> | rg 'eskit\\.sdk\\.core\\.ui\\.BrowserProxyActivity|android.intent.action.VIEW|scheme=esapp|ES_ACTION_LAUNCH'`
69
69
  - If the package/activity capability check fails, AI MUST stop run flow and ask user to reinstall runtime or provide the correct runtime package.
70
+ - For runtime capability inventory tasks (e.g. "列出所有支持 esapp:// 拉起的 APK"), AI MUST query intent handlers first and MUST NOT use package-name keyword grep as primary evidence.
71
+ - Preferred inventory command:
72
+ `adb -s <serial> shell "pm query-activities --brief --components -a android.intent.action.VIEW -d 'esapp://action/start?from=cmd&pkg=es.test' -c android.intent.category.BROWSABLE"`
73
+ - If `cmd package query-intent-activities` is unavailable (`Unknown command`), AI MUST fallback to `pm query-activities` immediately and continue.
74
+ - Inventory fallback command:
75
+ `adb -s <serial> shell "pm query-activities --brief --components -a android.intent.action.VIEW -d 'esapp://' -c android.intent.category.BROWSABLE"`
76
+ - For each resolved package, AI MUST output: component, package path (`pm path <pkg>`), and version (`dumpsys package <pkg> | grep -m 1 versionName`).
70
77
  - After `quicktvui-ai run-dev --project <project-path>` reaches runtime launcher page, AI MUST send a confirm action (`adb shell input keyevent 23` or `66`, or equivalent click) on the runtime start button so runtime pulls/loads the dev bundle.
71
78
  - AI MUST NOT stop at launcher page before triggering that confirm action, and MUST verify launch/bundle load result from logs or foreground activity status.
72
79
  - If user asks to launch a specific ES app/version/source, run:
package/rules/GEMINI.md CHANGED
@@ -59,6 +59,13 @@ Hard requirements:
59
59
  and fallback:
60
60
  `adb -s <serial> shell dumpsys package <runtime-package> | rg 'eskit\\.sdk\\.core\\.ui\\.BrowserProxyActivity|android.intent.action.VIEW|scheme=esapp|ES_ACTION_LAUNCH'`
61
61
  - If the package/activity capability check fails, AI MUST stop run flow and ask user to reinstall runtime or provide the correct runtime package.
62
+ - For runtime capability inventory tasks (e.g. "列出所有支持 esapp:// 拉起的 APK"), AI MUST query intent handlers first and MUST NOT use package-name keyword grep as primary evidence.
63
+ - Preferred inventory command:
64
+ `adb -s <serial> shell "pm query-activities --brief --components -a android.intent.action.VIEW -d 'esapp://action/start?from=cmd&pkg=es.test' -c android.intent.category.BROWSABLE"`
65
+ - If `cmd package query-intent-activities` is unavailable (`Unknown command`), AI MUST fallback to `pm query-activities` immediately and continue.
66
+ - Inventory fallback command:
67
+ `adb -s <serial> shell "pm query-activities --brief --components -a android.intent.action.VIEW -d 'esapp://' -c android.intent.category.BROWSABLE"`
68
+ - For each resolved package, AI MUST output: component, package path (`pm path <pkg>`), and version (`dumpsys package <pkg> | grep -m 1 versionName`).
62
69
  - After `quicktvui-ai run-dev --project <project-path>` reaches runtime launcher page, AI MUST send a confirm action (`adb shell input keyevent 23` or `66`, or equivalent click) on the runtime start button so runtime pulls/loads the dev bundle.
63
70
  - AI MUST NOT stop at launcher page before triggering that confirm action, and MUST verify launch/bundle load result from logs or foreground activity status.
64
71
  - If user asks to launch a specific ES app/version/source, run: