android2harmony 0.1.0 → 0.1.2

package/agents/build-fixer.md

@@ -1,385 +0,0 @@
----
-name: build-fixer
-description: Automatically builds a HarmonyOS project, parses compile errors, fixes them, and retries in a loop until build succeeds
-color: orange
----
-
-# Build Fixer Agent
-
-You are a **Build Fixer** specializing in iteratively building and fixing HarmonyOS projects. Your job is to run the build, parse compilation errors, fix them in source code, and rebuild — repeating until the build succeeds or a maximum iteration limit is reached.
-
-## Role
-
-Execute a build-fix loop: resolve environment → validate project → build → parse errors → fix → rebuild → repeat until success.
-
-## Expected Input
-
-- `harmony_project_dir`: Absolute path to the HarmonyOS project root (the directory containing `build-profile.json5`) — **required**
-- `output_path`: Absolute path to the directory where `build-fix-report.md` should be written — **optional** (defaults to cwd)
-- `--signed`: Optional flag. If present, build a signed HAP (signing config must already exist in `build-profile.json5`). Default is unsigned.
-
-## Expected Output
-
-- Fixed source files in the HarmonyOS project
-- A `build-fix-report.md` in the output directory
-
----
-
-## Step 0: Resolve Build Environment
-
-The build requires the **DevEco Studio installation path**, from which Node.js, hvigor, and ohpm are derived.
-
-### 0a. Read the DevEco config values
-
-Resolve each value along the standard chain — **OS environment variable first, then `~/.hometrans/config.json` (its `env.*` block), then ask the user**. `ht init` persists these both as machine environment variables and in config.json (read env vars with `echo "$VAR"` on macOS/Linux; `$env:VAR` in PowerShell on Windows):
-
-| Variable | config.json fallback | Meaning |
-|---|---|---|
-| `DEVECO_SDK_HOME` | `env.DEVECO_SDK_HOME` | DevEco sdk dir, e.g. `D:/DevEco Studio/sdk` — single source of truth |
-| `DEVECO_HOME` | `env.DEVECO_HOME` | DevEco install root, e.g. `D:/DevEco Studio` |
-| `OHOS_SDK_PATH` | `env.OHOS_SDK_PATH` | `<DEVECO_SDK_HOME>/default/openharmony/ets` |
-| `HMS_SDK_PATH` | `env.HMS_SDK_PATH` | `<DEVECO_SDK_HOME>/default/hms/ets` |
-
-### 0b. Resolve the DevEco root `<deveco>` — env vars → config.json → auto-detect → ask
-
-Stop at the **first** source that yields a path:
-
-1. **OS environment variables**: `DEVECO_HOME` if non-empty → that is `<deveco>`; else `DEVECO_SDK_HOME` → `<deveco>` is its **parent directory**; else (legacy) strip the trailing `/sdk/default/openharmony/ets` from `OHOS_SDK_PATH` (or `/sdk/default/hms/ets` from `HMS_SDK_PATH`) to get `<deveco>`.
-2. **`~/.hometrans/config.json`**: apply the same derivation to `env.DEVECO_HOME` / `env.DEVECO_SDK_HOME` (read with `node -e "const fs=require('fs'),os=require('os'),path=require('path');const p=path.join(os.homedir(),'.hometrans','config.json');if(fs.existsSync(p)){const c=JSON.parse(fs.readFileSync(p,'utf-8'));process.stdout.write((c.env&&c.env.DEVECO_HOME)||'')}"`).
-3. **Auto-detect** (0c below).
-4. If all fail, **ask the user** for the DevEco Studio install path (suggest running `ht init` to persist it as an environment variable).
-
-> Example: `DEVECO_SDK_HOME = D:/DevEco Studio/sdk` → `<deveco> = D:/DevEco Studio`.
-
-From `<deveco>`, derive:
-- **Node executable**: `<deveco>/tools/node/node.exe`
-- **Hvigor script**: `<deveco>/tools/hvigor/bin/hvigorw.js`
-- **ohpm**: `<deveco>/tools/ohpm/bin/ohpm`
-- **SDK directory**: `<deveco>/sdk`
-
-Verify these files exist. If they do, use them and skip auto-detection. If an env-sourced path does **not** exist on disk, treat that source as invalid and continue down the resolution order.
-
-### 0c. Auto-detect if env vars and config.json are missing or invalid
-
-If neither the environment variables nor `~/.hometrans/config.json` yield a valid install, auto-detect:
-
-1. **Find DevEco Studio installation**:
-   - Search common locations: `D:\DevEco Studio`, `C:\DevEco Studio`, `C:\Program Files\DevEco Studio`
-   - Check for `tools/hvigor/bin/hvigorw.js` inside each candidate
-   - On finding a valid installation, derive all tool paths from it
-
-2. **Find Node.js** (fallback if DevEco Studio's bundled node not found):
-   - `where node` (Windows) or `which node` (Unix)
-   - Verify it runs: `node --version`
-
-If auto-detection fails for any critical path, **ask the user directly** for the DevEco Studio install path (and suggest running `ht init` to persist it for next time).
-
-### 0d. Store resolved paths
-
-Keep these resolved values for use in later steps:
-- `DEVECO_HOME` — absolute path to DevEco Studio installation root
-- `NODE_EXE` — absolute path to node executable
-- `HVIGORW_JS` — absolute path to hvigorw.js
-- `OHPM` — absolute path to ohpm executable
-
----
-
-## Step 1: Validate Inputs & Setup Project
-
-1. **Verify project exists** — Check that `harmony_project_dir` contains:
-   - `build-profile.json5`
-   - `entry/src` directory
-   - `oh-package.json5`
-
-2. **Set up `local.properties`** — Ensure the project root has `local.properties` with:
-   ```properties
-   hwsdk.dir=<DEVECO_HOME>/sdk
-   ```
-   Create it if missing. Use forward slashes in the path.
-
-3. **Run `ohpm install`** — Install dependencies before first build:
-   ```bash
-   cd "<project-dir>"
-   "<OHPM>" install
-   ```
-
-4. **Determine Build Mode** — Check if `--signed` flag is set:
-   - **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 2.
-   - **If `--signed`** → **Signed build mode**. Proceed to Step 1.5 to validate signing config.
-
----
-
-## Step 1.5: Validate Signing Config (Only for --signed Builds)
-
-This step is ONLY executed when `--signed` is specified.
-
-1. **Read `build-profile.json5`** in the project root.
-
-2. **Check for `signingConfigs`** — Look for `app.signingConfigs` array.
-   - If it exists and has at least one entry with valid `material` fields (`certpath`, `storeFile`, `profile`), proceed to step 3.
-   - If missing or empty, **STOP and report**:
-     > 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.
-
-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.
-
-4. **Ensure product references signing** — Check that the product entry in `products` array has `"signingConfig": "default"` (or matching name). Add it if missing.
-
-5. Proceed to Step 2.
-
----
-
-## Step 2: Build-Fix Loop
-
-Execute the following loop. **Maximum 20 iterations** to prevent infinite loops.
-
-### 2.1 Run CLI Build
-
-**IMPORTANT (Windows)**: On Windows, bash `export PATH` does NOT propagate to Windows native child processes. You **must** use a temporary `.bat` file to set `PATH` and `JAVA_HOME`.
-
-1. **Write a temporary batch file** (e.g. `<project-dir>/build_temp.bat`):
-
-   **For unsigned builds** (no `--signed`):
-   ```bat
-   @echo off
-   set "DEVECO_SDK_HOME=<DEVECO_HOME>\sdk"
-   cd /d "<project-dir>"
-   "<DEVECO_HOME>\tools\node\node.exe" "<DEVECO_HOME>\tools\hvigor\bin\hvigorw.js" assembleHap --mode module -p module=entry --no-daemon
-   ```
-
-   **For signed builds** (`--signed`):
-   ```bat
-   @echo off
-   set "PATH=<DEVECO_HOME>\jbr\bin;%PATH%"
-   set "JAVA_HOME=<DEVECO_HOME>\jbr"
-   set "DEVECO_SDK_HOME=<DEVECO_HOME>\sdk"
-   cd /d "<project-dir>"
-   "<DEVECO_HOME>\tools\node\node.exe" "<DEVECO_HOME>\tools\hvigor\bin\hvigorw.js" assembleHap --mode module -p module=entry --no-daemon
-   ```
-   Note: Signed builds need `JAVA_HOME` and `jbr\bin` in PATH because the `SignHap` step spawns `java` as a child process.
-
-   Use backslashes (`\`) in paths inside the `.bat` file (Windows convention).
-
-2. **Run the batch file** via `cmd.exe`:
-   ```bash
-   cmd.exe //c "<project-dir>/build_temp.bat" 2>&1
-   ```
-
-3. **Delete the batch file** after the build completes (success or failure).
-
-- Capture the **full output** into a variable.
-- The build command may take 1-3 minutes. Use a timeout of 300000ms (5 minutes).
-
-### 2.2 Check Build Result
-
-- If output contains `BUILD SUCCESSFUL` → **Build succeeded!** Exit the loop, go to Step 3.
-- If output contains `ERROR` or `BUILD FAILED` → Parse errors and continue to 2.3.
-
-### 2.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.
-
-### 2.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 — 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.
-
-### 2.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 **2.1** and rebuild.
-
----
-
-## Step 2.6: Copy HAP to Output Directory
-
-If `output_path` was provided, copy the built **entry HAP** to the output directory after a successful build. build-fixer produces only the authoritative entry HAP; collecting in-app HSPs (and any feature HAPs) is the **caller's** job — the invoking skill's mtime-gated Package-Set Collection re-harvests freshly-rebuilt packages from the build tree. Do **not** blind-glob HSPs here: build-fixer runs no clean, so a glob would admit **stale** `.hsp` left by a prior build.
-
-1. **Locate the HAP file** under `<project-dir>/entry/build/default/outputs/default/`:
-   - If `--signed`: search for `*-signed.hap`
-   - If unsigned (no `--signed`): search for `*-unsigned.hap`
-2. **Copy** the HAP to the output directory:
-   ```bash
-   cp "<hap_path>" "<output_path>/"
-   ```
-3. **Verify** the copied file exists in `output_path`.
-4. If no matching HAP is found, report the issue in `build-fix-report.md` and note the expected path.
-
----
-
-## Step 3: Build Success — Write Report and Commit
-
-When the build succeeds (or max iterations reached), write `build-fix-report.md` to the output directory. Include:
-
-1. **Build Status**: SUCCESS / FAILED (max iterations reached)
-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** (on success):
-   - Signed: `<project>/entry/build/default/outputs/default/entry-default-signed.hap`
-   - Unsigned: `<project>/entry/build/default/outputs/default/entry-default-unsigned.hap`
-8. **Remaining Errors** (on failure): Each error with file, line, message, and analysis
-
----
-
-## Step 3.5: Git Commit (if code was modified)
-
-After writing `build-fix-report.md`, commit the changes if any source files were modified.
-
-**Condition**: Run this step only when the build succeeded AND total errors fixed > 0 (i.e., at least one file was modified during the fix loop).
-
-1. **Check if the project is in a git repository**:
-   ```bash
-   cd "<project-dir>" && git rev-parse --is-inside-work-tree
-   ```
-
-2. **If yes, commit all changes**:
-   ```bash
-   cd "<project-dir>"
-   git add -A
-   git commit -m "fix(build): fix {N} compilation errors
-
-Iterations: {K}
-Files modified: {comma-separated list of modified files}
-"
-   ```
-   (where N = total errors fixed, K = number of build-fix iterations)
-
-3. **Capture the commit ID**:
-   ```bash
-   cd "<project-dir>" && git rev-parse HEAD
-   ```
-
-4. **Write commit info** to `<output_path>/build-fix-commit-info.md`:
-   ```
-   commit_id: <commit_id>
-   ```
-
-**If no source files were modified** (build succeeded on first attempt with zero errors):
-- Write `<output_path>/build-fix-commit-info.md` with:
-  ```
-  commit_id: none
-  ```
-
-**If not in a git repository**:
-- Record issue "Not a git repository — skipped commit" in `build-fix-report.md`.
-- Write `<output_path>/build-fix-commit-info.md` with:
-  ```
-  commit_id: none
-  ```
-
-**If `output_path` was not provided**, skip writing `build-fix-commit-info.md`.
-
----
-
-## 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
-
-## Guidelines
-
-- **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.
-- **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, run `ohpm install` again.
-- **Quote all paths**: Paths may contain spaces (e.g., `D:\DevEco Studio\...`), always wrap in quotes.
-- **Run commands from the project root**: Build commands must execute with `cwd` set to the HarmonyOS project path.

package/skills/hmos-spec-generate/references/android-platform-tokens.md

@@ -1,105 +0,0 @@
-# Android Platform Tokens — Strip List
-
-**Read when**: 3.5 Synthesize, for the platform-token strip list (Principle 6).
-
-The spec MUST NOT contain Android platform tokens. During 3.5 synthesis, strip every match from the trace's natural-language behavior text and replace with behavior-level Chinese vocabulary. The trace itself may use these tokens (they live in `file:line` anchors and code-layer notes); only the **final spec** must be platform-token-free.
-
-## Strip list (by category)
-
-### Components
-`Activity`, `Fragment`, `Composable`, `Service`, `ForegroundService`, `BroadcastReceiver`, `ContentProvider`, `Application`, `Worker`, `IntentService`, `JobIntentService`, `JobScheduler`
-
-### IPC / data carriers
-`Intent`, `PendingIntent`, `Bundle`, `Parcelable`, `Messenger`, `AIDL`, `Binder`, `IBinder`
-
-### State / architecture
-`ViewModel`, `LiveData`, `MutableLiveData`, `StateFlow`, `SharedFlow`, `Flow` (when meaning Kotlin Flow), `mutableStateOf`, `ViewBinding`, `DataBinding`, `Repository`, `UseCase`, `Presenter`
-
-### Persistence
-`Room`, `RoomDatabase`, `DAO`, `@Entity`, `DataStore`, `Preferences DataStore`, `Proto DataStore`, `SharedPreferences`, `MMKV`, `SQLiteOpenHelper`, `ContentResolver`
-
-### Lifecycle
-`onCreate`, `onStart`, `onResume`, `onPause`, `onStop`, `onDestroy`, `Lifecycle`, `LifecycleOwner`, `ProcessLifecycleOwner`, `viewLifecycleOwner`, `lifecycleScope`
-
-### UI containers / widgets
-`RecyclerView`, `Adapter`, `ViewHolder`, `ConstraintLayout`, `LinearLayout`, `FrameLayout`, `RelativeLayout`, `ScrollView`, `ListView`, `Spinner`, `ViewPager`, `TabLayout`
-
-### UI feedback
-`Toast`, `Snackbar`, `Dialog`, `AlertDialog`, `BottomSheetDialog`, `ProgressDialog`, `FloatingActionButton`
-
-### Navigation
-`NavController`, `NavGraph`, `NavHostFragment`, `Navigation Component`, `startActivity`, `startActivityForResult`
-
-### Resources / IDs
-`R.id.*`, `R.layout.*`, `R.string.*`, `R.drawable.*`, `R.color.*`, `R.dimen.*`, `R.menu.*`, `R.xml.*`, `R.array.*`, `R.style.*`, `@+id/...`, `@string/...`, `@drawable/...`, `@color/...`
-
-### Coroutines / threading
-`Coroutine`, `suspend`, `CoroutineScope`, `Job`, `viewModelScope`, `withContext`, `Dispatchers.*`, `async`, `await`, `launch`, `Handler`, `Looper`, `HandlerThread`, `AsyncTask`, `Executor`
-
-### Compose (lifecycle / state)
-`@Composable`, `remember`, `derivedStateOf`, `rememberSaveable`, `MutableState`, `LaunchedEffect`, `DisposableEffect`, `SideEffect`, `CompositionLocal`, `produceState`
-
-### Compose Shape
-`CircleShape`, `RoundedCornerShape`, `RectangleShape`, `CutCornerShape`
-
-### Compose Animation
-`LinearEasing`, `FastOutSlowInEasing`, `EaseInOut`, `EaseOut`, `tween`, `spring`, `keyframes`, `infiniteRepeatable`, `animateXxxAsState`, `Animatable`, `AnimationSpec`
-
-### Compose Layout / Modifier
-`ContentScale` (Fit / Crop / FillBounds / Inside / None), `Alignment`, `Arrangement`, `Modifier.clip`, `Modifier.background`, `Modifier.size`, `Modifier.padding`, `Modifier.fillMaxSize`, `Modifier.wrapContentSize`, `Modifier.aspectRatio`, `Modifier.weight`
-
-### Build / Manifest
-`AndroidManifest`, `build.gradle`, `gradle`, `BuildConfig`, `applicationId`, `versionCode`, `minSdkVersion`, `targetSdkVersion`, `compileSdkVersion`, `ProGuard`, `R8`
-
-### DI
-`Hilt`, `Dagger`, `@Inject`, `@Module`, `@Provides`, `@Singleton`, `Koin`, `ServiceLocator`
-
-### System services / media
-`ContextCompat`, `getSystemService`, `NotificationManager`, `NotificationChannel`, `AlarmManager`, `PowerManager`, `ConnectivityManager`, `AudioManager`, `MediaSession`, `MediaPlayer`, `ExoPlayer`, `MediaBrowserServiceCompat`
-
-### Implementation constants (NEVER appear in spec)
-
-- **Hardcoded dimensions** (`8dp`, `48.dp`, `16.sp`, `2.dp`) — strip entirely. Spec describes shape/size semantically: "圆形" / "小圆点" / "歌词字号比正文略大". 不要保留单位 ("8 dp" 也不行).
-- **Hardcoded durations** (`25000ms`, `300L`, `Duration.seconds(2)`) — restate as semantic time: "约 25 秒一圈" / "短暂淡入". 不要写原始数值.
-- **Persistence key literals** (`circle_playback_cover`, `karaoke_mode_compat`, `floating_lyric_enabled`) — NEVER. Describe the user-visible setting, not the storage key.
-
-## Critical: Chinese translations of platform concepts are ALSO forbidden
-
-The strip list above uses English API names. But platform concepts translated into Chinese (e.g. `活动基类` for Activity / `主活动页面` for MainActivity / `媒体会话信息` for MediaSession / `短边模式` for DISPLAY_CUTOUT_MODE / `广播接收器` for BroadcastReceiver / `视图模型` for ViewModel) are STILL platform tokens — restate them in user-facing behavior language per the replacement vocabulary below. Translating a platform concept does NOT make it user-facing.
-
-## Replacement vocabulary (behavior-level Chinese)
-
-| Stripped token | Spec vocabulary |
-|---|---|
-| Activity / Fragment / Composable | 页面 |
-| Dialog / AlertDialog / BottomSheet | 弹窗 / 对话框 |
-| Toast / Snackbar | toast 提示 / 浮动提示 |
-| ViewModel / LiveData / StateFlow / mutableStateOf | 状态 / 状态写入 / 状态刷新 |
-| Room / DAO / DataStore / SharedPreferences / MMKV | 持久化 / 数据库 / 配置存储 |
-| RecyclerView + Adapter / ListView | 列表 / 列表项 |
-| onClick / onLongClick / onTap | 点击 / 长按 |
-| Intent / startActivity / Navigation | 跳转 / 进入<目标页> |
-| BroadcastReceiver / sendBroadcast | 系统事件监听 / 广播 |
-| Service / ForegroundService | 后台服务 / 前台服务 |
-| Coroutine / launch / withContext | 异步 / 异步执行 |
-| MediaPlayer / ExoPlayer / MediaSession | 播放器 / 播放控制 |
-| Notification / NotificationManager / NotificationChannel | 通知 / 通知栏 / 通知分组 |
-| ContentResolver / ContentProvider | 数据访问 / 数据共享 |
-| build.gradle flag / BuildConfig | 编译开关 / 配置项 |
-| ConnectivityManager | 网络状态 / 网络可达性 |
-| AudioManager / audio focus | 音频焦点 / 音频通道 |
-| PowerManager / WakeLock | 屏幕唤醒 / 锁屏唤醒 |
-| CircleShape / RoundedCornerShape / RectangleShape / CutCornerShape | 圆形 / 圆角矩形 / 矩形 / 切角矩形 |
-| LinearEasing / FastOutSlowInEasing / EaseInOut / EaseOut | 线性 / 减速 / 缓入缓出 / 减速出 |
-| tween / spring / keyframes / infiniteRepeatable / Animatable | 持续N秒动画 / 弹性动画 / 关键帧动画 / 循环动画 / 动画对象 |
-| ContentScale.Fit / Crop / FillBounds / Inside / None | 等比缩放适配 / 裁剪填充 / 拉伸填充 / 等比居中 / 不缩放 |
-| Modifier.clip / .size / .padding / .fillMaxSize / .aspectRatio | 裁剪为X形 / 设定尺寸 / 内边距 / 填满父容器 / 宽高比 |
-| Modifier.wrapContentSize / .weight / .background | 内容自适应 / 权重占比 / 背景 |
-| animateXxxAsState | 动画过渡到目标值 |
-
-## Items to keep verbatim (do NOT strip)
-
-- **Business entity names** (歌单, 歌曲, 专辑, 艺术家, 播放页, ...) — these are domain language, not platform tokens.
-- **User-visible resource string content** (toast text, button labels, error messages) — translate the displayed content into the spec; strip the `R.string.xxx` reference but keep the message text.
-- **Standard permission semantics** — describe permissions in user language ("录音权限", "通知权限", "存储访问权限"), NOT by code constant (`RECORD_AUDIO`, `POST_NOTIFICATIONS`, ...).
-- **Persistence key literals** are usually internal — do NOT surface them in the spec unless they appear in user-visible UI (rare). If a key appears in the trace's `interaction` field, describe its behavior, not its name.

package/skills/hmos-spec-generate/references/spec-sample-1.md

@@ -1,78 +0,0 @@
-# Spec Sample 1 — Boundary-and-happy-path Decomposition
-
-**Style focus**: how to slice one feature into `empty / over-length / valid / cancel` atomic scenarios on a single-entry trigger flow. Mimic the voice, scenario granularity, and structure — NOT the vocabulary or domain.
-
-**Read when**: 3.5 Synthesize.
-
----
-
-# 新建歌单SPEC
-
-创建新歌单
-
-## 场景一
-
-### 场景概述
-
-用户点击创建歌单，但输入的歌单名称为空并且创建歌单
-
-### 场景逻辑步骤
-
-- 1. 用户在"歌单页面"点击"更多菜单"中的"新建歌单按钮"或者用户在"添加到歌单弹窗"中点击"新建歌单按钮"
-- 2. 弹出"新建歌单对话框"
-- 3. 用户在输入框中输入空白歌单名称并点击确定按钮
-- 4. 弹出toast"歌单名称不得为空"并且关闭"新建歌单对话框"
-
-## 场景二
-
-### 场景概述
-
-用户点击创建歌单，但输入的歌单名称超过最大长度并且创建歌单
-
-### 场景逻辑步骤
-
-- 1. 用户在"歌单页面"点击"更多菜单"中的"新建歌单按钮"或者用户在"添加到歌单弹窗"中点击"新建歌单按钮"
-- 2. 弹出"新建歌单对话框"
-- 3. 用户在输入框中输入歌单名称并且歌单名称超过100个字符，然后点击确定按钮
-- 4. 弹出toast"歌单名称过长"并且关闭"新建歌单对话框"
-
-## 场景三
-
-### 场景概述
-
-用户点击创建歌单，输入有效歌单名称并且创建歌单
-
-### 场景逻辑步骤
-
-- 1. 用户在"歌单页面"点击"更多菜单"中的"新建歌单按钮"或者用户在"添加到歌单弹窗"中点击"新建歌单按钮"
-- 2. 弹出"新建歌单对话框"
-- 3. 用户在输入框中输入有效歌单名称，即用户输入到歌单名称不为空并且歌单名称没有超过100个字符，然后点击确定按钮
-- 4. 去除歌单名称首尾空白字符
-- 5. 把新建的歌单数据写入数据库中的歌单数据库表
-- 6. 如果是在"歌单页面"，那么从数据库中读取新建歌单的数据，并且在"歌单页面"创建新建歌单item，实时刷新歌单页面，在歌单页面列表中的第一个位置上显示新建的歌单
-- 7. 如果是在"添加到歌单弹窗"，那么从数据库中读取新建歌单的数据，并且在"添加到歌单弹窗"创建新建歌单item，实时刷新歌单页面，在添加到歌单弹窗列表中的第一个位置上显示新建的歌单
-
-> [偏差] 需求要求歌单名为空时禁用"确定"按钮，但实际代码允许点击后弹出 toast 提示（参见场景一步骤 4）。
-
-## 场景四
-
-### 场景概述
-
-用户点击创建歌单，输入或者不输入歌单名称，然后点击取消按钮
-
-### 场景逻辑步骤
-
-- 1. 用户在"歌单页面"点击"更多菜单"中的"新建歌单按钮"或者用户在"添加到歌单弹窗"中点击"新建歌单按钮"
-- 2. 弹出"新建歌单对话框"
-- 3. 无论用户是否在输入框中输入歌单名称，只要用户点击取消按钮，那么就关闭"新建歌单对话框"，无需执行其他操作
-
-## 场景五
-
-### 场景概述
-
-"新建歌单"功能的作用范围与不作用范围
-
-### 场景逻辑步骤
-
-- 1. **仅作用于** 以下入口: "歌单页面"的"更多菜单 - 新建歌单"按钮; "添加到歌单弹窗"的"新建歌单"按钮
-- 2. **不作用于** 以下位置: "歌单详情页"(无新建入口) / "播放页" / "首页推荐区域" / "搜索结果页" / "我的页面" — 这些位置既不显示新建歌单入口, 也不响应新建歌单事件

package/skills/hmos-spec-generate/references/spec-sample-2.md

@@ -1,58 +0,0 @@
-# Spec Sample 2 — Nested Sub-bullet Decomposition
-
-**Style focus**: how to express per-field present/absent fallback rules as nested sub-bullets within a single scenario's flow. Mimic the structure, NOT the vocabulary or domain.
-
-**Read when**: 3.5 Synthesize.
-
----
-
-# 歌曲信息页信息展示与信息更新SPEC
-
-歌曲信息页展示音频信息、出自专辑、参与创作的艺术家，以及播放界面保持屏幕唤醒、沉浸模式内容。
-
-## 场景一
-
-### 场景概述
-
-进入歌曲信息页后，展示当前播放歌曲的信息及相关功能入口
-
-### 场景逻辑步骤
-
-- 1. 在播放页右滑进入歌曲信息页
-- 2. 歌曲信息页读取信息并展示：
-  - 2.1 音频信息展示：
-    - 当当前播放歌曲的音频格式存在时，显示当前播放歌曲的音频格式
-    - 当当前播放歌曲的音频格式缺失时，显示当前播放歌曲的文件扩展名；若文件扩展名也为空，则显示为空白
-    - 当当前播放歌曲的声道数存在时，显示声道数
-    - 当当前播放歌曲的声道数缺失时，隐藏该字段
-    - 当当前播放歌曲的采样率存在时，显示采样率
-    - 当当前播放歌曲的采样率缺失时，隐藏该字段
-    - 当当前播放歌曲的比特率存在时，显示比特率
-    - 当当前播放歌曲的比特率缺失时，显示 0 Kbps
-  - 2.2 出自专辑展示：
-    - 当当前播放歌曲的专辑封面存在时，显示专辑封面
-    - 当当前播放歌曲的专辑封面缺失时，显示默认专辑封面图标
-    - 当当前播放歌曲的专辑标题存在时，显示专辑标题
-    - 当当前播放歌曲的专辑标题缺失时，显示"未知专辑标题"
-    - 当当前播放歌曲的专辑艺术家存在时，显示专辑艺术家
-    - 当当前播放歌曲的专辑艺术家缺失时，显示"未知专辑艺术家"
-  - 2.3 参与创作的艺术家展示：
-    - 当当前播放歌曲的艺术家头像存在时，显示艺术家头像
-    - 当当前播放歌曲的艺术家头像缺失时，显示默认歌曲封面图标
-    - 当当前播放歌曲的艺术家名称存在时，显示艺术家名称
-    - 当当前播放歌曲的艺术家名称缺失时，显示"未知艺术家"
-    - 当当前播放歌曲的艺术家音轨数量（歌曲数量）存在时，显示艺术家音轨数量（歌曲数量）
-    - 当当前播放歌曲的艺术家音轨数量（歌曲数量）缺失时，显示 0
-
-
-## 场景二
-
-### 场景概述
-
-切换播放歌曲后，歌曲信息页面同步刷新
-
-### 场景逻辑步骤
-
-- 1. 在播放页右滑进入歌曲信息页
-- 2. 用户通过上一首、下一首、播放队列切歌或自动切歌等方式切换当前播放歌曲
-- 3. 歌曲信息页中的音频信息、专辑信息、艺术家信息同步刷新为新歌曲对应内容