원클릭으로 Manus에서 모든 스킬 실행

update-multilingual-docs

스타40

포크4

업데이트2026년 6월 10일 07:30

同步本專案多語系文件：.github/i18n/{lang}/{README,CONTRIBUTING}.md（根目錄為 symlink 指向 en/）與 docs/chrome-web-store/store_description_*.md (14 種語言)。當使用者提到「多語系、i18n 文件、翻譯文件、更新 README 多語、store description、Chrome Web Store 描述」時觸發。

설치

Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.

Manus에서 실행

출처

Tai-ch0802

Tai-ch0802/arc-like-chrome-extension

GitHub 저장소 열기 Creator 저장소 보기

다운로드

Manus에서 실행

Update Multilingual Documentation

This skill updates the project's documentation when new features are added or existing features are modified.

Files to Update

Documentation Structure (.github/i18n/):
- En (Source): .github/i18n/en/{README,CONTRIBUTING,etc}.md
- Translations: .github/i18n/{lang_code}/{filename}.md
- Root: Files in root should be Symlinks to i18n/en/.
Store Descriptions (docs/chrome-web-store/):
- store_description_*.md (14 languages)

Procedure

1. Analyze the Change

Identify the source content (usually in English from a Spec file).
Determine the insertion point.

2. Update English Source

Edit .github/i18n/en/README.md (or other target file).
Insert the new content.

3. Sync Root (Symlinks)

Only root README.md is a symlink pointing to .github/i18n/en/README.md. Ensure it stays a valid symlink.
There is no root CONTRIBUTING.md (nor CODE_OF_CONDUCT.md / SECURITY.md); those live per-language under .github/i18n/{lang}/, not as root symlinks.
(No content copy needed for the README symlink)

4. Update Multilingual Docs

Iterate: For each language folder in .github/i18n/ (excluding en):
1. Translate the new content into the target language.
2. Insert at the corresponding location.

5. Update Store Descriptions

Source: Use docs/chrome-web-store/store_description_en.md as the baseline.
Iterate: For each language file in docs/chrome-web-store/:
1. Translate and insert the new content.
2. Verification: ensure emojis headers (like ⌨️) are consistent.

6. Verification

Check that all files have been modified.
Run a grep check to ensure headers are present in all files.

이 저장소의 다른 Skills

같은 저장소

pull-request

Tai-ch0802/arc-like-chrome-extension

建立本專案的 Pull Request：雙語描述 (zh-TW/en)、gh CLI、.agent/skills/pull-request/scripts/check-pr.sh 預驗證、references/pr_template.md 與 checklist.md。當使用者提到「開 PR、建 PR、create PR、pull request、提交變更、發 PR、新建 PR」時觸發。

2026-07-0340

debugging

Tai-ch0802/arc-like-chrome-extension

本專案 (MV3 Chrome extension) 的除錯紀律與 playbook：先重現再修、證據優先於模式匹配、單變因修改、跨 context 時序問題、service worker 終止、storage 問題、flaky E2E 分流。當使用者提到「除錯、debug、壞掉、不會動、修不好、查原因、root cause、flaky、時好時壞」時觸發。

2026-07-0340

harness-maintenance

Tai-ch0802/arc-like-chrome-extension

維護本專案 AI agent harness（AGENTS.md / CLAUDE.md / GEMINI.md / .agent/{rules,skills,workflows} / docs/wiki）的 SOP：單一事實來源對照表、drift 稽核步驟、新增/刪除 skill 的判準、wiki 同步機制。當使用者提到「更新 harness、同步 AGENTS、文件過時、drift、稽核設定檔、整理 skills、維護 wiki」時觸發。

2026-07-0340

verification

Tai-ch0802/arc-like-chrome-extension

交付前驗證紀律：依變更類型選擇最小充分驗證組合（unit / 目標 E2E / happy-path CI / make build）、Makefile 打包檢查、i18n 連動、GEMINI.md key_files 同步、誠實回報。當使用者提到「驗證、收尾、完成了嗎、可以交付嗎、送 PR 前、檢查一下」或任何實作即將收尾時觸發。

2026-07-0340

cleanup-merged-branches

Tai-ch0802/arc-like-chrome-extension

清理已合併進 main 的本地與遠端 git 分支。本專案採 squash merge，PR 合併後特性分支可直接刪除。當使用者提到「清理分支、cleanup branches、刪除舊分支、清掉已合併分支、整理 branch」時觸發。

2026-06-1040

commit-message-helper

Tai-ch0802/arc-like-chrome-extension

本專案 (Manifest V3 Chrome extension) 的 commit 規範與範例：subject 使用英文 Conventional Commits、body 使用繁中說明背景與原因。當使用者提到「commit、提交訊息、commit message、寫 commit、commit 規範」時觸發。

2026-06-1040

name	update-multilingual-docs
description	同步本專案多語系文件：.github/i18n/{lang}/{README,CONTRIBUTING}.md（根目錄為 symlink 指向 en/）與 docs/chrome-web-store/store_description_*.md (14 種語言)。當使用者提到「多語系、i18n 文件、翻譯文件、更新 README 多語、store description、Chrome Web Store 描述」時觸發。

Update Multilingual Documentation

This skill updates the project's documentation when new features are added or existing features are modified.

Files to Update

Documentation Structure (.github/i18n/):
- En (Source): .github/i18n/en/{README,CONTRIBUTING,etc}.md
- Translations: .github/i18n/{lang_code}/{filename}.md
- Root: Files in root should be Symlinks to i18n/en/.
Store Descriptions (docs/chrome-web-store/):
- store_description_*.md (14 languages)

Procedure

1. Analyze the Change

Identify the source content (usually in English from a Spec file).
Determine the insertion point.

2. Update English Source

Edit .github/i18n/en/README.md (or other target file).
Insert the new content.

3. Sync Root (Symlinks)

Only root README.md is a symlink pointing to .github/i18n/en/README.md. Ensure it stays a valid symlink.
There is no root CONTRIBUTING.md (nor CODE_OF_CONDUCT.md / SECURITY.md); those live per-language under .github/i18n/{lang}/, not as root symlinks.
(No content copy needed for the README symlink)

4. Update Multilingual Docs

Iterate: For each language folder in .github/i18n/ (excluding en):
1. Translate the new content into the target language.
2. Insert at the corresponding location.

5. Update Store Descriptions

Source: Use docs/chrome-web-store/store_description_en.md as the baseline.
Iterate: For each language file in docs/chrome-web-store/:
1. Translate and insert the new content.
2. Verification: ensure emojis headers (like ⌨️) are consistent.

6. Verification

Check that all files have been modified.
Run a grep check to ensure headers are present in all files.