android2harmony 0.1.7 → 0.1.8

package/skills/hmos-fix-build-errors/SKILL.md

@@ -1,266 +0,0 @@
----
-name: hmos-fix-build-errors
-description: Build a HarmonyOS project via CLI and automatically fix compile errors in a loop until the build succeeds. Default unsigned HAP; pass --signed to build a signed HAP (signing config must already exist in the project's build-profile.json5). Allowed to be called only in Android-to-HarmonyOS migration scenarios.
-argument-hint: <harmony_project_dir> [deveco-studio-path] [--signed]
-allowed-tools: Agent, Read, Write, Edit, Glob, Grep, Bash
-type: tool
-domain: engineering
----
-
-# HarmonyOS Auto Build & Fix
-
-Automatically build a HarmonyOS NEXT project from the command line, parse compile errors, fix them, and retry — repeating until the build succeeds.
-
-## Inputs
-
-Declare all inputs up front as explicit `snake_case` variables, bound to the positional `$ARGUMENTS`:
-
-| Variable | Positional | Required | Meaning |
-|---|---|---|---|
-| `harmony_project_dir` | `$ARGUMENTS[0]` | yes | HarmonyOS project root, e.g. `D:/MyHmosApp` |
-| `deveco_studio_path` | `$ARGUMENTS[1]` | no | DevEco Studio installation root, e.g. `D:/DevEco Studio`. When omitted, resolved automatically (see Step 0.2) |
-| `signed` | `--signed` flag | no | If any argument equals `--signed`, build a **signed HAP**; otherwise build an **unsigned HAP** (default) |
-
-Note: `--signed` is a positional-order-independent flag — when `deveco_studio_path` is omitted it may appear as `$ARGUMENTS[1]`, and when provided it appears as `$ARGUMENTS[2]`.
-
----
-
-## Step 0: Validate Inputs & Setup Environment
-
-1. **Verify project exists** — Check that `harmony_project_dir` contains a valid HarmonyOS project (look for `build-profile.json5`, `entry/src` directory, `oh-package.json5`).
-
-2. **Resolve `<deveco-path>`** — follow the resolution chain, stopping at the first source that yields a valid path (environment variable only, else ask):
-   1. `deveco_studio_path` if provided (and not `--signed`).
-   2. **OS environment variable** `DEVECO_SDK_HOME` (`echo "$DEVECO_SDK_HOME"` on macOS/Linux; `$env:DEVECO_SDK_HOME` in PowerShell on Windows) — the DevEco SDK root (e.g. `D:/DevEco Studio/sdk`); derive `<deveco-path>` as its parent directory (the DevEco Studio install root).
-   3. **Ask the user** for the DevEco Studio install path (suggest setting `DEVECO_SDK_HOME` as a machine environment variable).
-
-   **Verify the resolved `<deveco-path>`** contains:
-   - `tools/node/node.exe`
-   - `tools/hvigor/bin/hvigorw.js`
-   - `tools/ohpm/bin/ohpm`
-   - `sdk/` directory
-
-   If verification fails for an env-sourced path, treat that source as invalid and continue down the list; if it fails for a user-supplied path, report what is missing and ask again.
-
-3. **Set up `local.properties`** — Ensure the project root has `local.properties` with:
-   ```properties
-   hwsdk.dir=<deveco-path>/sdk
-   ```
-   Create it if missing. Use forward slashes in the path.
-
-4. **Use `npx --yes devecocli build` as the build entrypoint** — The build-fix loop should call `npx --yes devecocli build` rather than invoking `ohpm` or `hvigorw.js` directly. `npx --yes devecocli build` wraps dependency install (`ohpm install`) and the underlying hvigor build.
-
-5. **Determine Build Mode** — Check if any argument equals `--signed` (it may be `$ARGUMENTS[1]` when the DevEco path is omitted, or `$ARGUMENTS[2]` when it is provided):
-   - **If NOT `--signed`** → **Unsigned build mode**. Ensure `build-profile.json5` does NOT have `signingConfigs` or `signingConfig` references in products (remove them if present). Go to Step 1.
-   - **If `--signed`** → **Signed build mode**. Proceed to Step 0.5 to validate signing config before the Step 1 build loop invokes `npx --yes devecocli build`.
-
----
-
-## Step 0.5: Validate Signing Config (Only for --signed Builds)
-
-This step is ONLY executed when `--signed` is specified.
-
-Signing information is read directly from the project's own `build-profile.json5`. The user must have already configured signing in DevEco Studio before running this skill.
-
-### Steps:
-
-1. **Read `build-profile.json5`** in the project root.
-
-2. **Check for `signingConfigs`** — Look for `app.signingConfigs` array in the file.
-   - If `signingConfigs` exists and has at least one entry with valid `material` fields (`certpath`, `storeFile`, `profile`), proceed to step 3.
-   - If `signingConfigs` is missing or empty, **STOP and report to the user**:
-     > Signing configuration not found in `build-profile.json5`.
-     > Please open the project in DevEco Studio, go to **File → Project Structure → Signing Configs**, enable **Automatically generate signature**, then re-run this skill with `--signed`.
-
-3. **Validate signing material files exist** — For the first entry in `signingConfigs`, check that the files referenced by `material.certpath`, `material.storeFile`, and `material.profile` actually exist on disk.
-   - If any file is missing, **STOP and report** which files are missing. Suggest the user re-open DevEco Studio and re-generate the signing config.
-
-4. **Ensure product references signing** — Check that the product entry in `products` array has `"signingConfig": "default"` (or matching the signing config name). Add it if missing.
-
-5. Proceed to Step 1.
-
----
-
-## Step 1: Build-Fix Loop
-
-Execute the following loop. **Maximum 20 iterations** to prevent infinite loops.
-
-### 1.1 Run CLI Build
-
-Use `npx --yes devecocli build` as the build command inside the fix loop. It is the supported wrapper for dependency install and hvigor execution, so the skill should not instruct raw `hvigorw.js` calls.
-
-1. **Invoke `npx --yes devecocli build` from the project root**:
-
-   **For unsigned builds** (no `--signed`):
-   ```bash
-   cd "<project-dir>"
-   npx --yes devecocli build
-   ```
-   If the project needs an explicit module target, prefer:
-   ```bash
-   cd "<project-dir>"
-   npx --yes devecocli build --modules entry
-   ```
-
-   **For signed builds** (`--signed`):
-   ```bash
-   cd "<project-dir>"
-   npx --yes devecocli build
-   ```
-   Run this only after Step 0.5 verifies the signing config in `build-profile.json5`. Preserve any required signed-build environment setup (for example `JAVA_HOME` on Windows) before invoking `npx --yes devecocli build`, but do not bypass the CLI wrapper.
-
-2. **Capture the full output** into a variable.
-
-- The build command may take 1-3 minutes. Use a timeout of 300000ms (5 minutes).
-
-### 1.2 Check Build Result
-
-- If output contains `BUILD SUCCESSFUL` → **Build succeeded!** Exit the loop, go to Step 2.
-- If output contains `ERROR` or `BUILD FAILED` → Parse errors and continue to 1.3.
-
-### 1.3 Parse Errors
-
-Extract error information from the build output. Errors typically appear in these formats:
-
-```
-ERROR: <file-path>:<line>:<col> - <error-code>: <message>
-```
-
-or
-
-```
-ArkTS:ERROR File: <file-path>:<line>:<col>
-  <error message>
-```
-
-Group errors by file. Focus on **actual errors**, not warnings.
-
-### 1.4 Fix Errors
-
-Read each file that has errors and apply fixes. Use the error reference table below to identify and fix common issues:
-
-| Error Code / Pattern | Message | Fix |
-|---|---|---|
-| `arkts-limited-throw` | "throw statements cannot accept values of arbitrary types" | Change `throw err` to `throw (err instanceof Error) ? err : new Error(String(err))` |
-| `arkts-no-obj-literals-as-types` | "Object literals cannot be used as type declarations" | Define a named `interface` instead of inline `{ key: Type }` |
-| `arkts-no-untyped-obj-literals` | "Object literal must correspond to some explicitly declared class or interface" | Assign to typed variable: `const r: MyInterface = {...}; return r;` |
-| `arkts-no-any-type` / `any` type usage | "Use explicit types instead of any" | Replace `any` with the correct concrete type or `object` |
-| `arkts-no-var` | "Use 'let' or 'const' instead of 'var'" | Replace `var` with `let` or `const` |
-| `10903329` | "Unknown resource name 'xxx'" | Verify resource exists in `resources/base/media/` or `element/*.json`. Use `layered_image` as fallback for missing images. **Special case**: `$r('sys.media.ohos_ic_public_xxx')` references system icons by SDK-specific names that may not exist in the build SDK — replace with `$r('app.media.ic_public_xxx')` and add the icon file to `resources/base/media/` |
-| `10505001` | "Resource[] is not assignable to ResourceColor" | Remove array brackets: `.fontColor($r('app.color.x'))` not `.fontColor([$r('app.color.x')])` |
-| `00303221` | "permission must be a value that is predefined within the SDK" | Remove invalid permission from `module.json5`. See valid permissions list below |
-| Missing import | "Cannot find name 'xxx'" | Add the correct import (see import reference below) |
-| Missing `async` | "await expression requires async function" | Add `async` to the enclosing function |
-| Missing `build()` | "@Component must have build() method" | Add a `build() {}` method to the @Component struct |
-| Type mismatch | Various type errors | Fix the type annotation or cast appropriately |
-| Duplicate identifier | "Duplicate identifier 'xxx'" | Remove or rename the duplicate declaration |
-
-**For errors NOT in the table above**: Read the error message carefully, read the relevant source file, understand the context, and apply an appropriate fix. Use your knowledge of ArkTS/HarmonyOS to determine the correct solution.
-
-### 1.5 Log Progress
-
-After each fix iteration, briefly report:
-- Iteration number
-- Number of errors found
-- Summary of fixes applied
-- Whether re-building
-
-Then go back to **1.1** and rebuild.
-
----
-
-## Step 2: Build Success Report
-
-When the build succeeds, present a summary:
-
-1. **Build Status**: SUCCESS
-2. **Build Type**: Signed HAP or Unsigned HAP
-3. **Signing** (if signed): Confirm signing config from `build-profile.json5` was used
-4. **Iterations**: How many build-fix cycles were needed
-5. **Total Errors Fixed**: Count of errors fixed across all iterations
-6. **Summary of Changes**: List of files modified and what was fixed in each
-7. **Output HAP Path**:
-   - Signed: `<project>/entry/build/default/outputs/default/entry-default-signed.hap`
-   - Unsigned: `<project>/entry/build/default/outputs/default/entry-default-unsigned.hap`
-
----
-
-## Reference: Common HarmonyOS Imports
-
-```typescript
-// Network
-import { http } from '@kit.NetworkKit';
-
-// Data persistence
-import { preferences } from '@kit.ArkData';
-import { relationalStore } from '@kit.ArkData';
-
-// UI utilities
-import { router } from '@kit.ArkUI';
-import { promptAction } from '@kit.ArkUI';
-
-// Ability & Context
-import { UIAbility, AbilityConstant, Want } from '@kit.AbilityKit';
-import { common } from '@kit.AbilityKit';
-
-// File I/O
-import { fileIo } from '@kit.CoreFileKit';
-
-// Logging
-import { hilog } from '@kit.PerformanceAnalysisKit';
-
-// JSON parsing — built-in, no import needed
-// ArkUI built-in components (Text, Column, Row, List, Button, Image, etc.) — NO import needed
-```
-
-## Reference: Valid Permission Names
-
-Commonly used SDK-validated permissions for `module.json5`:
-
-- `ohos.permission.INTERNET`
-- `ohos.permission.GET_NETWORK_INFO`
-- `ohos.permission.GET_WIFI_INFO`
-- `ohos.permission.KEEP_BACKGROUND_RUNNING`
-- `ohos.permission.PUBLISH_AGENT_REMINDER`
-- `ohos.permission.CAMERA`
-- `ohos.permission.MICROPHONE`
-- `ohos.permission.APPROXIMATELY_LOCATION`
-- `ohos.permission.LOCATION`
-- `ohos.permission.READ_MEDIA`
-- `ohos.permission.WRITE_MEDIA`
-- `ohos.permission.USE_BLUETOOTH`
-- `ohos.permission.VIBRATE`
-
-**Note**: `ohos.permission.NOTIFICATION` does NOT exist. When in doubt, omit the permission.
-
-## Reference: ArkTS Strict Mode Rules
-
-All code must comply with ArkTS strict mode:
-
-1. **No `any` type** — Use explicit types or `object`
-2. **No `var`** — Only `let` and `const`
-3. **No dynamic property access** — Use typed interfaces instead of `obj['key']` on typed objects
-4. **`throw` must throw Error instances** — Never `throw 'string'` or `throw unknownVar`
-5. **All object literals must match declared interfaces** — No anonymous `{ key: val }` returns without a matching interface
-6. **No inline object literal types** — `function(): { a: string }` is forbidden; define a named `interface`
-7. **All `@Component` structs must have `build()`** — Missing build method is a compile error
-8. **`$r()` resource references validated at compile time** — All referenced resources must exist
-9. **`fontColor()` expects `ResourceColor`**, not `Resource[]` — Don't wrap in array brackets (exception: `SymbolGlyph`)
-10. **Permission names in `module.json5`** — Must be SDK-predefined values
-
-## Important Notes
-
-- **Timeout**: Individual build commands may take up to 5 minutes. Use a 300000ms timeout.
-- **Max iterations**: Stop after 20 iterations to prevent infinite loops. If build still fails after 20 attempts, report the remaining errors to the user.
-- **Don't over-fix**: Only fix errors reported by the compiler. Don't proactively refactor unrelated code.
-- **Read before edit**: Always read a file before modifying it. Understand the surrounding context.
-- **One error can cause many**: A single root-cause fix (like adding a missing interface) may resolve multiple reported errors. After fixing root causes, rebuild to see remaining issues.
-- **ohpm errors**: If the build fails because of missing packages, rerun `npx --yes devecocli build` so it can retry dependency install before you investigate deeper.
-
----
-
-## References
-
-- `references/arkts-strict-patterns.md` — ArkTS 严格模式编译错误的确定性修复 Pattern（throw/any/var/interface 等）
-- `references/known-patterns.md` — 已知常见编译错误 Pattern 及修复方案
-- `references/rdb-entity-pattern.md` — RDB 实体类编译错误 Pattern（数据库实体相关）

package/skills/hmos-fix-build-errors/references/arkts-strict-patterns.md

@@ -1,219 +0,0 @@
-# ArkTS 严格模式确定性修复 Pattern
-# 适用于: ArkTS 严格模式编译错误
-# 触发场景: 编译报错 arkts-no-xxx 系列
-# 经验来源: EinkBro 迁移 (2026-03-26)
-
----
-
-## Pattern 1: throw 语句
-
-### 错误写法
-```typescript
-throw err;                    // ERROR: arkts-limited-throw
-throw 'error string';         // ERROR: arkts-limited-throw
-throw unknownVariable;        // ERROR: arkts-limited-throw
-```
-
-### 正确写法
-```typescript
-throw new Error(String(error));
-```
-
-### 不需要修改的情况
-```typescript
-throw new Error('specific message');  // OK - 已经是 Error 实例
-```
-
----
-
-## Pattern 2: 对象字面量作为参数 (arkts-no-untyped-obj-literals)
-
-### 错误写法
-```typescript
-// ERROR: Object literal must correspond to some explicitly declared class or interface
-const response = await this.sendRequest(url, { contents });
-```
-
-### 正确写法 — 先声明变量
-```typescript
-interface GeminiRequestBody {
-  contents: GeminiContent[];
-}
-
-const requestBody: GeminiRequestBody = { contents };
-const response = await this.sendRequest(url, requestBody);
-```
-
-### 内联参数场景
-```typescript
-// 方法参数也是对象字面量，同样需要处理
-httpRequest.request(url, {
-  method: http.RequestMethod.POST,
-  header: { 'Content-Type': 'application/json' },
-  extraData: JSON.stringify(body),
-  connectTimeout: 30000,
-  readTimeout: 30000
-});
-// ^ 这种场景 SDK 方法签名本身接受 object 类型，通常 OK
-// 但自定义方法调用时必须用已声明接口的变量
-```
-
----
-
-## Pattern 3: Margin vertical 简写不支持
-
-### 错误写法
-```typescript
-.margin({ vertical: 8 });     // ERROR: 'vertical' does not exist in type
-```
-
-### 正确写法
-```typescript
-.margin({ top: 8, bottom: 8 });
-```
-
-### 常见场景
-| 错误 | 正确 |
-|------|------|
-| `.margin({ vertical: 8 })` | `.margin({ top: 8, bottom: 8 })` |
-| `.margin({ horizontal: 16 })` | `.margin({ left: 16, right: 16 })` |
-
----
-
-## Pattern 4: List 内不能直接放 Divider
-
-### 错误写法
-```typescript
-List() {
-  ForEach(items, (item) => {
-    ListItem() { /* ... */ }
-  })
-  Divider()  // ERROR: List children must be ListItem only
-}
-```
-
-### 正确写法 — 用 ListItem + border
-```typescript
-List() {
-  ForEach(items, (item) => {
-    ListItem() {
-      Column() {
-        Text(item.name)
-      }
-      .width('100%')
-      .padding(12)
-      .border({ width: { bottom: 1 }, color: '#E0E0E0' })  // 替代 Divider 分隔线
-    }
-  })
-}
-```
-
-### 另一种方案 — border 直接在 ListItem 上
-```typescript
-ListItem() {
-  // content
-}
-.border({ width: { bottom: 1 }, color: '#E0E0E0' })
-```
-
----
-
-## Pattern 5: 数组字面量类型推断 (arkts-no-noninferrable-arr-literals)
-
-### 错误写法
-```typescript
-const arr = [1, 2, 3].map(x => ({ val: x }));
-// ERROR: Array literals must contain elements of only inferrable types
-```
-
-### 正确写法 — 显式类型
-```typescript
-interface Item { val: number; }
-const arr: Item[] = [1, 2, 3].map((x): Item => ({ val: x }));
-```
-
----
-
-## Pattern 6: TextDecoder 不存在
-
-### 错误写法
-```typescript
-const decoder = new TextDecoder();  // ERROR: Cannot find name 'TextDecoder'
-const str = decoder.decode(data);
-```
-
-### 正确写法
-```typescript
-const bytes = new Uint8Array(data);
-let chunk = '';
-for (let i = 0; i < bytes.length; i++) {
-  chunk += String.fromCharCode(bytes[i]);
-}
-```
-
----
-
-## Pattern 7: HTTP 组件事件名
-
-| 错误事件 | 正确事件 | 说明 |
-|---------|---------|------|
-| `request.on('requestEnd', ...)` | `request.on('dataEnd', ...)` | 请求结束事件 |
-| `request.on('error', ...)` | 改用 Promise 的 catch | HTTP 组件 error 事件签名不标准 |
-
----
-
-## Pattern 8: GeminiService 等自定义类缺少成员
-
-### 错误场景
-```typescript
-class GeminiService {
-  private async sendRequest(url: string, body: object): Promise<Object> {
-    httpRequest.request(url, { extraData: JSON.stringify(body),
-      connectTimeout: this.timeout,  // ERROR: Property 'timeout' does not exist
-      readTimeout: this.timeout
-    });
-  }
-  // timeout 属性忘记声明
-}
-```
-
-### 正确 — 确保所有成员都在类体内声明
-```typescript
-class GeminiService {
-  private timeout: number = 30000;  // 在类体内声明
-  private async sendRequest(...) { ... }
-}
-```
-
----
-
-## Pattern 9: Button 不支持 emoji
-
-### 错误写法
-```typescript
-Button('X')  // 有时 emoji 渲染异常
-Button('🗑')
-```
-
-### 正确写法
-```typescript
-Button('Del')   // 纯文本
-Button('Copy')
-Button('Back')
-```
-
----
-
-## 快速检查清单
-
-遇到 ArkTS 编译错误时，按序检查：
-
-1. throw → `throw new Error(String(x))`
-2. 对象字面量作为参数 → 先赋值给显式类型变量
-3. any / unknown → `Object` + `as Function` / `as SomeType`
-4. // @ts-ignore → 禁止，必须用类型操作替代
-5. ValuesBucket → 普通对象字面量 `{}`
-6. margin { vertical } → `{ top, bottom }`
-7. List 内 Divider → ListItem + border
-8. TextDecoder → Uint8Array 遍历
-9. `new SomeType()` 报错 → 检查是否是 type alias 而非 class

package/skills/hmos-fix-build-errors/references/known-patterns.md

@@ -1,157 +0,0 @@
-# Known Compile Error Patterns
-
-> **This file is auto-maintained by `a2h-retrospect`.**
-> Manual edits are allowed but may be overwritten when retrospect detects updated patterns.
-> Last updated: 2026-03-27
-
----
-
-## Pattern Index
-
-| # | Error Code / Type | Frequency | Short Description |
-|---|-------------------|-----------|-------------------|
-| 1 | arkts-identifiers-as-prop-names | 85 | ValuesBucket computed property name |
-| 2 | type mismatch (EventData) | 16 | EventData double type cast |
-| 3 | arkts-no-untyped-obj-literals | 9 | Untyped object literal |
-| 4 | type mismatch (promptAction) | 8 | promptAction button color type |
-| 5 | type error (@Prop) | 3 | @Prop naming conflict |
-
----
-
-## 1. ValuesBucket Computed Property Name
-
-- **Date**: 2026-03-27
-- **Error code**: `arkts-identifiers-as-prop-names`
-- **Frequency**: 85 occurrences
-- **Source**: AntennaPod V1 migration (a2h-retrospect-report-2026-03-27)
-
-**Error code**:
-```typescript
-const bucket: ValuesBucket = {
-  [ColumnName.TITLE]: title,   // ERROR: computed property name not allowed
-  [ColumnName.URL]: url,
-};
-```
-
-**Correct code**:
-```typescript
-const bucket: ValuesBucket = {};
-bucket[ColumnName.TITLE] = title;
-bucket[ColumnName.URL] = url;
-```
-
-**Rule**: ArkTS forbids computed property names (`[expr]: value`) in object literals. Build the object first, then assign properties via bracket notation.
-
----
-
-## 2. EventData Double Type Cast
-
-- **Date**: 2026-03-27
-- **Error code**: type mismatch
-- **Frequency**: 16 occurrences
-- **Source**: AntennaPod V1 migration (a2h-retrospect-report-2026-03-27)
-
-**Error code**:
-```typescript
-emitter.on({ eventId: 1 }, (data: emitter.EventData) => {
-  const value = data.data?.['key'] as string;  // ERROR: data.data is optional Record, direct cast fails
-});
-```
-
-**Correct code**:
-```typescript
-emitter.on({ eventId: 1 }, (data: emitter.EventData) => {
-  const raw = data.data as Record<string, Object>;
-  const value = raw['key'] as string;
-});
-```
-
-**Rule**: `EventData.data` is typed `Record<string, Object> | undefined`. Access requires two steps: (1) cast to `Record<string, Object>`, (2) cast the extracted value to the target type.
-
----
-
-## 3. Untyped Object Literal
-
-- **Date**: 2026-03-27
-- **Error code**: `arkts-no-untyped-obj-literals`
-- **Frequency**: 9 occurrences
-- **Source**: AntennaPod V1 migration (a2h-retrospect-report-2026-03-27)
-
-**Error code**:
-```typescript
-const options = {
-  title: 'Hello',
-  message: 'World',
-};  // ERROR: object literal without explicit type annotation
-```
-
-**Correct code**:
-```typescript
-interface DialogOptions {
-  title: string;
-  message: string;
-}
-const options: DialogOptions = {
-  title: 'Hello',
-  message: 'World',
-};
-```
-
-**Rule**: ArkTS requires all object literals to have an explicit type. Define an `interface` or `class` and annotate the variable.
-
----
-
-## 4. promptAction Button Color Type
-
-- **Date**: 2026-03-27
-- **Error code**: type mismatch
-- **Frequency**: 8 occurrences
-- **Source**: AntennaPod V1 migration (a2h-retrospect-report-2026-03-27)
-
-**Error code**:
-```typescript
-promptAction.showDialog({
-  buttons: [
-    { text: 'OK', color: '#ff0000' }   // ERROR: color expects ResourceColor, not string
-  ]
-});
-```
-
-**Correct code**:
-```typescript
-promptAction.showDialog({
-  buttons: [
-    { text: 'OK', color: Color.Red }
-  ]
-});
-// Or use $r('app.color.xxx') for resource reference
-```
-
-**Rule**: `promptAction.showDialog` button `color` property expects `ResourceColor` type (Color enum or `$r()` resource reference), not a raw hex string.
-
----
-
-## 5. @Prop Naming Conflict
-
-- **Date**: 2026-03-27
-- **Error code**: type error
-- **Frequency**: 3 occurrences
-- **Source**: AntennaPod V1 migration (a2h-retrospect-report-2026-03-27)
-
-**Error code**:
-```typescript
-@Component
-struct MyComponent {
-  @Prop title: string = '';   // ERROR: 'title' conflicts with built-in component property
-}
-```
-
-**Correct code**:
-```typescript
-@Component
-struct MyComponent {
-  @Prop itemTitle: string = '';   // Renamed to avoid conflict
-}
-```
-
-**Rule**: Certain property names (`title`, `content`, `action`, etc.) conflict with built-in component attributes. Prefix with a domain-specific qualifier (e.g., `itemTitle`, `feedTitle`).