deveco-harness 0.1.0

package/skills/arkui-knowledge/references/common-mistakes.md

@@ -0,0 +1,119 @@
+# ArkUI Common Mistakes
+
+Check this file before implementing ArkUI tabs, lists, state decorators, dialogs, navigation, or custom builders.
+
+## Tabs and TabContent
+
+Avoid: passing an object parameter with a builder callback into `TabContent`.
+
+Correct:
+
+```typescript
+TabContent() {
+  Column() {
+    Text('首页')
+  }
+}
+.tabBar('首页')
+```
+
+Rules:
+
+- `Tabs` direct children should be `TabContent`.
+- `TabContent` label content belongs in `.tabBar(...)`.
+- Do not place unrelated components directly under `Tabs`.
+
+## ForEach and LazyForEach
+
+Avoid: a key generator callback that opens a block but does not return the key string.
+
+Correct:
+
+```typescript
+ForEach(this.items, (item: ItemInfo) => {
+  Text(item.title)
+}, (item: ItemInfo) => item.id)
+```
+
+Rules:
+
+- The key generator must return a stable string.
+- Avoid index keys for business data because item order can change.
+- `LazyForEach` requires a real lazy data source and should be placed in supported scroll containers.
+
+## State decorators
+
+Avoid: placing `@State` on top-level variables, local variables, plain classes, or component inputs.
+
+Correct:
+
+```typescript
+@Component
+struct MessagePanel {
+  @State message: string = ''
+
+  build() {
+    Text(this.message)
+  }
+}
+```
+
+Rules:
+
+- State decorators belong on component member declarations.
+- `@State` is for component-local V1 state.
+- `@Prop` is for parent-to-child input.
+- `@Link` is for two-way binding in V1 components.
+- `@Local` and `@Param` belong to V2 components.
+- Do not mix V1 and V2 decorator families in one component.
+
+## Component attributes
+
+Avoid: shorthand modifier names borrowed from other UI systems.
+
+Correct:
+
+```typescript
+Text('标题')
+  .backgroundColor('#FFFFFF')
+  .fontSize(16)
+```
+
+Rules:
+
+- Use real ArkUI modifier names.
+- Match modifiers to the component that owns them.
+- Do not borrow CSS, Android, other UI framework, or web shorthand.
+
+## Dialog buttons
+
+Avoid: alert dialog button entries that use a label field named `text`.
+
+Correct:
+
+```typescript
+AlertDialog.show({
+  message: '确认删除？',
+  primaryButton: { value: '确定', action: () => {} }
+})
+```
+
+Rules:
+
+- Alert dialog button label field is `value`.
+- Keep cancel behavior limited to closing the dialog unless the requirement says otherwise.
+- Follow the current project dialog or toast wrapper when one exists.
+
+## UI visibility and interaction
+
+Common failures:
+
+- Required text is rendered under an overlay.
+- Clickable text is used when the requirement requires `Button`.
+- A tab label exists in code but is not visible on the tab bar.
+- State changes happen in code but the updated text is not rendered.
+- New UI is added outside the current launch page or reachable navigation path.
+
+Guardrail:
+
+- After writing UI, trace the visible path from the launch page to each required element and each required click result.

package/skills/arkui-knowledge/references/component-cookbook.md

@@ -0,0 +1,135 @@
+# ArkUI Component Cookbook
+
+This file keeps high-frequency ArkUI patterns close to the `arkui-knowledge` skill. Prefer project-local code style, but use these shapes to avoid common API mistakes.
+
+## Tabs and TabContent
+
+Use `Tabs` for tabbed pages. Direct children should be `TabContent`.
+
+```typescript
+Tabs({ barPosition: BarPosition.End }) {
+  TabContent() {
+    Column() {
+      Text('首页')
+    }
+  }
+  .tabBar('首页')
+
+  TabContent() {
+    Column() {
+      Text('发现')
+    }
+  }
+  .tabBar('发现')
+}
+```
+
+Key rules:
+
+- `TabContent()` has no object parameter.
+- Put tab label content in `.tabBar(...)`.
+- Keep each tab body inside the `TabContent` block.
+- Use `.onChange((index: number) => { ... })` when selected tab state must refresh other UI.
+
+## List, Grid, and ForEach
+
+Use `ForEach` for ordinary in-memory arrays and small lists.
+
+```typescript
+interface CardItem {
+  id: string
+  title: string
+}
+
+@State cards: CardItem[] = [
+  { id: 'card-1', title: '卡片 1' },
+  { id: 'card-2', title: '卡片 2' }
+]
+
+Grid() {
+  ForEach(this.cards, (item: CardItem) => {
+    GridItem() {
+      Text(item.title)
+    }
+  }, (item: CardItem) => item.id)
+}
+```
+
+Key rules:
+
+- The key function returns a stable string.
+- Do not use a key callback that returns no value.
+- Use `ListItem` inside `List`.
+- Use `GridItem` inside `Grid`.
+- Use `LazyForEach` only with a proper data source when lazy rendering is needed.
+
+## TextInput, Button, and state refresh
+
+Use state variables for user input and validation messages.
+
+```typescript
+@State userName: string = ''
+@State errorText: string = ''
+
+Column({ space: 12 }) {
+  TextInput({ placeholder: '请输入用户名', text: this.userName })
+    .onChange((value: string) => {
+      this.userName = value
+    })
+
+  Button('注册')
+    .onClick(() => {
+      this.errorText = this.userName.length === 0 ? '请填写完整信息' : '注册成功'
+    })
+
+  Text(this.errorText)
+    .fontColor(this.errorText === '注册成功' ? Color.Green : Color.Red)
+}
+```
+
+Key rules:
+
+- State that drives visible UI should use the existing component decorator family.
+- `TextInput` changes should update state in `.onChange(...)`.
+- Required validation messages must be rendered in the page, not only logged.
+
+## Dialog and Toast
+
+For simple confirmation, use alert dialog APIs already used by the project. Button entries use `value` for the visible label.
+
+```typescript
+this.getUIContext().showAlertDialog({
+  title: '确认进入订座？',
+  message: '确认进入订座？',
+  primaryButton: {
+    value: '去订座',
+    action: () => {
+      this.getUIContext().getPromptAction().showToast({ message: '已打开订座' })
+    }
+  },
+  secondaryButton: {
+    value: '再想想',
+    action: () => {}
+  }
+})
+```
+
+Key rules:
+
+- Use `value` for alert dialog button text.
+- Do not invent `text` fields for alert dialog buttons.
+- Prefer the project's current dialog/toast pattern when it already exists.
+- Keep cancel actions side-effect free when the requirement says cancel only closes the dialog.
+
+## Navigation and NavDestination
+
+Follow the existing navigation architecture. Do not replace project routing only to add one page.
+
+For projects already using `Navigation`, register or route to `NavDestination` through the existing `NavPathStack` or project router wrapper. For projects using a custom app router, follow that wrapper and existing page registration pattern.
+
+Key rules:
+
+- Preserve the existing navigation mechanism.
+- Keep page names and builder exports consistent with nearby pages.
+- Pass only the parameters required by the target page.
+- Verify the first visible screen and the new navigation path.

package/skills/arkui-knowledge/references/ui-quality-checklist.md

@@ -0,0 +1,36 @@
+# ArkUI UI Quality Checklist
+
+Use this checklist before finalizing ArkUI UI changes.
+
+## Requirement visibility
+
+- Required labels, button text, tab labels, card titles, and dialog text appear on the target screen.
+- Text is not hidden by overlays, zero-size containers, off-screen placement, or low contrast.
+- The first screen remains reachable from the app launch path.
+
+## Interaction
+
+- Required buttons use `Button` when the requirement asks for `Button`.
+- Click handlers update visible state, switch tabs, open dialogs, navigate, or show the requested response.
+- Cancel and close actions do not perform extra business actions.
+- Required click targets remain large enough and visually clear.
+
+## Layout quality
+
+- New UI follows nearby spacing, color, typography, density, and component style.
+- Layout nesting is only deep enough to express the UI.
+- Dynamic text, lists, and tab content have stable width/height constraints where needed.
+- New elements do not overlap existing banners, cards, bottom bars, or system safe areas.
+
+## State and rendering
+
+- UI-driving state uses the current component's decorator family.
+- Lists and grids render stable keys.
+- Conditional UI still leaves required content reachable.
+- Dialog, toast, and navigation code follows existing project patterns.
+
+## Change scope
+
+- Only files required by the UI task are modified.
+- Existing business flow, page registration, resource naming, and navigation architecture are preserved.
+- No state-management migration, navigation rewrite, or broad refactor is introduced without an explicit request.

package/skills/deveco-create-project/SKILL.md

@@ -0,0 +1,144 @@
+---
+name: deveco-create-project
+description: Load this skill when creating, initializing, or scaffolding an ArkTS project, including "0-1", "from scratch", "new ArkTS project", "新建工程", "创建项目", and empty directory initialization tasks. Load this skill even if the target directory already exists — never assume an existing same-named directory is the user's intended project and skip to build_project/start_app. If the user provides a Chinese or other non-ASCII project name (e.g. 购物车, 天气预报), you MUST propose 2-3 UpperCamelCase ASCII candidates (e.g. 购物车 → ShoppingCart / ShopCart / Cart) and let the user choose via AskUserQuestion BEFORE invoking the script — never pass non-ASCII names through to the script, and never pick a single translation on the user's behalf. Use the skill's private TypeScript script to create ArkTS projects reliably.
+---
+
+# deveco-create-project
+
+Use the skill's private script to create an ArkTS project, instead of relying on the model to copy template files one by one.
+
+## Required Parameters
+
+Confirm the following parameters before execution. Ask the user if any required value is missing:
+
+| Parameter | Required | Default | Example |
+|------|---------|--------|------|
+| `projectPath` | Required | — | `/Users/yellow/Desktop/projects` |
+| `appName` | Required | — | `HelloWorld` |
+| `bundleName` | Auto-derived, no need to ask | `com.example.{appName lowercase}` | `com.example.helloworld` |
+| `apiLevel` | Optional | Auto-detect from DevEco SDK metadata, fallback to `22` | `21` |
+
+### appName rules
+
+`appName` must match `^[A-Za-z][A-Za-z0-9_]{0,127}$`. Chinese / non-ASCII names are NOT allowed — the script will reject them (exit code `4`, `APP_NAME_INVALID`).
+
+When the user provides a Chinese or other non-ASCII name, you MUST:
+1. Propose 2-3 UpperCamelCase ASCII candidates based on meaning (e.g. `购物车` → `ShoppingCart` / `ShopCart` / `Cart`; `天气预报` → `WeatherForecast` / `Weather` / `Forecast`). Fall back to pinyin only when meaning is unclear.
+2. Let the user pick one via `AskUserQuestion` before invoking the script — do NOT pick on the user's behalf, even if one option seems obviously best.
+3. Never pass the original non-ASCII name to the script.
+
+### Target directory conflict
+
+If `{projectPath}/{appName}` already exists and is not empty, the script will exit with code `2` and emit a `PROJECT_EXISTS` JSON payload. When you see it, ask the user via `AskUserQuestion` whether to overwrite, rename, or cancel — do NOT silently re-run or delete the directory yourself.
+
+If the user explicitly specifies an SDK/API level, pass it through directly.
+If the user does not specify one, do not let the model invent a version. Let the script detect it using this fixed priority:
+
+1. `DEVECO_HOME/sdk/default/sdk-pkg.json` → `data` → `apiVersion`
+2. fallback to `22`
+
+The script's stdout JSON (`apiLevel`, `source`, `detectedFrom`) is authoritative — do not re-read files under `{DEVECO_HOME}/sdk/**` to verify it.
+
+### Optional: Brief Requirement Checklist for Complex App Requests
+
+If the current session is already executing an approved Plan Mode plan or an existing plan file is referenced, do not create another plan, do not call `plan_enter` or `plan_write`, and do not ask for plan approval again. Treat the existing plan as the source of truth.
+
+If there is no existing approved plan and the user asks to create a new project with a complex app requirement, make a brief requirement checklist before copying or editing files.
+
+The checklist must list:
+- pages to implement
+- the first screen / entry page
+- navigation between pages
+- key feature points for each page
+- verification points for pages and navigation
+
+Keep this checklist concise and continue automatically unless required project parameters are missing or the requirement is contradictory.
+Do not expand this skill into ArkUI design guidance; load `arkui-knowledge` before implementing UI code.
+
+## Execution Steps
+
+> `copy-template.mjs` reads the sibling skill directory `deveco-create-project/application/` as the template source by default.
+> This script runs with Node.js. If `node` is not available in the environment, stop immediately and explain that to the user.
+> Default skills are extracted to a local user skill directory before execution. Keep all scripts in this skill self-contained and do not import repo-only source files.
+
+### Step 1: Run the Private Script
+
+Run the following with Shell:
+
+```bash
+node "{SKILL_DIR}/scripts/copy-template.mjs" --project-path "{projectPath}" --app-name "{appName}" --bundle-name "{bundleName}" --api-level "{apiLevel}"
+```
+
+If `apiLevel` is not explicitly provided by the user, omit `--api-level` and let the script detect it from DevEco metadata.
+
+Execution requirements:
+
+- Do not manually copy template files one by one.
+- Let the script handle recursive copying, binary asset copying, placeholder replacement, and basic validation.
+- The script is responsible for SDK detection. Do not decide the SDK version in the prompt by guesswork.
+- If the script exits with a non-zero code, report the error to the user and stop.
+
+### Step 2: Verify the Result
+
+At minimum, verify that the following file exists:
+
+- `{projectPath}/{appName}/build-profile.json5`
+
+If the file is missing, treat the creation as failed and do not proceed to later compile or page-generation steps.
+
+If the script reports `source: "fallback"`, the local SDK metadata is incomplete — deliver the project path, warn the user (e.g. "Find no sdk-pkg.json, can not probe sdk version").
+
+### Step 3: Switch Session Project Context (Required)
+
+After project creation succeeds, call `switch_cwd` and set the target path to the generated project root (`{projectPath}/{appName}`).
+
+Reason:
+
+- `build_project` and `start_app` only work correctly when the current session context directory is the actual project root.
+- This skill creates a full project under the current path; without switching context to that generated path, subsequent build/run actions may fail or target the wrong directory.
+
+If `switch_cwd` fails, report the context switch failure and stop. Do not continue to feature implementation, `build_project`, or `start_app`.
+
+### Step 4: Continue Feature Work in the Generated Project
+
+If the user's request includes app behavior, UI, pages, or business requirements in addition to project creation, continue only after `switch_cwd` succeeds.
+
+Before implementing the feature:
+
+- Read `entry/src/main/resources/base/profile/main_pages.json` to identify the launch page list.
+- Read the launch page file, usually `entry/src/main/ets/pages/Index.ets` and `entry/src/main/ets/entryability/EntryAbility.ets`.
+- Modify the actual launch page or its navigation path so the requested feature is reachable from the first screen.
+
+> **CRITICAL: `EntryAbility.ets` and `main_pages.json` must stay in sync.**
+>
+> `EntryAbility.ets` calls `windowStage.loadContent('pages/SomePage', ...)` to load the first screen.
+> That page path **must** appear in `main_pages.json`'s `src` array — otherwise the framework silently fails to load the page, resulting in a **white screen**.
+>
+> When you create custom pages and update `main_pages.json`, you **must** also update `EntryAbility.ets`:
+> - If you **rename or replace** the first entry in `main_pages.json`, update `loadContent()` to match the new first page.
+> - If you **prepend** a new splash/landing page to `main_pages.json`, update `loadContent()` to point to that page.
+>
+> Always re-read both files after editing to confirm they are consistent.
+
+- Do not finish by only creating a new named page/component unless the launch page routes to it.
+
+> **CRITICAL: Desktop app name — both `app_name` and `EntryAbility_label` must be updated.**
+>
+> The desktop icon label is controlled by `EntryAbility_label`, not `app_name`:
+> - `AppScope/resources/base/element/string.json` → `app_name` — used as the **application-level** label (settings, etc.).
+> - `entry/src/main/resources/base/element/string.json` → `EntryAbility_label` — used as the **Ability-level** label (**this is what appears on the desktop icon**).
+
+- After changes, run `build_project`; if it succeeds, run `start_app`.
+
+### Step 5: Report Back to the User
+
+Report after all requested creation, implementation, build, run, and verification work is complete, or immediately when a blocking failure stops the flow.
+
+Output:
+
+- The absolute project path
+- App name / bundle name / API Level
+- `source` of the selected API level: `user_input` / `sdk_pkg` / `fallback`
+- Whether the template integrity check passed
+- Whether `switch_cwd` succeeded
+- Build/run/verification status when feature work was requested

package/skills/deveco-create-project/application/AppScope/app.json5

@@ -0,0 +1,10 @@
+{
+  "app": {
+    "bundleName": "com.example.myapplication",
+    "vendor": "example",
+    "versionCode": 1000000,
+    "versionName": "1.0.0",
+    "icon": "$media:layered_image",
+    "label": "$string:app_name"
+  }
+}

package/skills/deveco-create-project/application/AppScope/resources/base/element/string.json

@@ -0,0 +1,8 @@
+{
+  "string": [
+    {
+      "name": "app_name",
+      "value": "MyApplication"
+    }
+  ]
+}

package/skills/deveco-create-project/application/AppScope/resources/base/media/layered_image.json

@@ -0,0 +1,7 @@
+{
+  "layered-image":
+  {
+    "background" : "$media:background",
+    "foreground" : "$media:foreground"
+  }
+}

package/skills/deveco-create-project/application/build-profile.json5

@@ -0,0 +1,42 @@
+{
+  "app": {
+    "signingConfigs": [],
+    "products": [
+      {
+        "name": "default",
+        "signingConfig": "default",
+        "targetSdkVersion": "6.0.2(22)",
+        "compatibleSdkVersion": "6.0.2(22)",
+        "runtimeOS": "HarmonyOS",
+        "buildOption": {
+          "strictMode": {
+            "caseSensitiveCheck": true,
+            "useNormalizedOHMUrl": true
+          }
+        }
+      }
+    ],
+    "buildModeSet": [
+      {
+        "name": "debug",
+      },
+      {
+        "name": "release"
+      }
+    ]
+  },
+  "modules": [
+    {
+      "name": "entry",
+      "srcPath": "./entry",
+      "targets": [
+        {
+          "name": "default",
+          "applyToProducts": [
+            "default"
+          ]
+        }
+      ]
+    }
+  ]
+}

package/skills/deveco-create-project/application/code-linter.json5

@@ -0,0 +1,32 @@
+{
+  "files": [
+    "**/*.ets"
+  ],
+  "ignore": [
+    "**/src/ohosTest/**/*",
+    "**/src/test/**/*",
+    "**/src/mock/**/*",
+    "**/node_modules/**/*",
+    "**/oh_modules/**/*",
+    "**/build/**/*",
+    "**/.preview/**/*"
+  ],
+  "ruleSet": [
+    "plugin:@performance/recommended",
+    "plugin:@typescript-eslint/recommended"
+  ],
+  "rules": {
+    "@security/no-unsafe-aes": "error",
+    "@security/no-unsafe-hash": "error",
+    "@security/no-unsafe-mac": "warn",
+    "@security/no-unsafe-dh": "error",
+    "@security/no-unsafe-dsa": "error",
+    "@security/no-unsafe-ecdsa": "error",
+    "@security/no-unsafe-rsa-encrypt": "error",
+    "@security/no-unsafe-rsa-sign": "error",
+    "@security/no-unsafe-rsa-key": "error",
+    "@security/no-unsafe-dsa-key": "error",
+    "@security/no-unsafe-dh-key": "error",
+    "@security/no-unsafe-3des": "error"
+  }
+}

package/skills/deveco-create-project/application/entry/build-profile.json5

@@ -0,0 +1,33 @@
+{
+  "apiType": "stageMode",
+  "buildOption": {
+    "resOptions": {
+      "copyCodeResource": {
+        "enable": false
+      }
+    }
+  },
+  "buildOptionSet": [
+    {
+      "name": "release",
+      "arkOptions": {
+        "obfuscation": {
+          "ruleOptions": {
+            "enable": false,
+            "files": [
+              "./obfuscation-rules.txt"
+            ]
+          }
+        }
+      }
+    },
+  ],
+  "targets": [
+    {
+      "name": "default"
+    },
+    {
+      "name": "ohosTest",
+    }
+  ]
+}

package/skills/deveco-create-project/application/entry/hvigorfile.ts

@@ -0,0 +1,7 @@
+// @ts-nocheck – HarmonyOS template file, only used when copied into a DevEco project
+import { hapTasks } from '@ohos/hvigor-ohos-plugin';
+
+export default {
+  system: hapTasks, /* Built-in plugin of Hvigor. It cannot be modified. */
+  plugins: []       /* Custom plugin to extend the functionality of Hvigor. */
+}

package/skills/deveco-create-project/application/entry/obfuscation-rules.txt

@@ -0,0 +1,23 @@
+# Define project specific obfuscation rules here.
+# You can include the obfuscation configuration files in the current module's build-profile.json5.
+#
+# For more details, see
+#   https://developer.huawei.com/consumer/cn/doc/harmonyos-guides/source-obfuscation
+
+# Obfuscation options:
+# -disable-obfuscation: disable all obfuscations
+# -enable-property-obfuscation: obfuscate the property names
+# -enable-toplevel-obfuscation: obfuscate the names in the global scope
+# -compact: remove unnecessary blank spaces and all line feeds
+# -remove-log: remove all console.* statements
+# -print-namecache: print the name cache that contains the mapping from the old names to new names
+# -apply-namecache: reuse the given cache file
+
+# Keep options:
+# -keep-property-name: specifies property names that you want to keep
+# -keep-global-name: specifies names that you want to keep in the global scope
+
+-enable-property-obfuscation
+-enable-toplevel-obfuscation
+-enable-filename-obfuscation
+-enable-export-obfuscation

package/skills/deveco-create-project/application/entry/oh-package.json5

@@ -0,0 +1,10 @@
+{
+  "name": "entry",
+  "version": "1.0.0",
+  "description": "Please describe the basic information.",
+  "main": "",
+  "author": "",
+  "license": "",
+  "dependencies": {}
+}
+