refactor(prompt_gen): standardize templates in English

- What: convert all prompt templates to English
- What: update template content for clarity and consistency
- Why: standardize on English for LLM prompt compatibility

Author: DennySORA

CHANGELOG.md

@@ -18,6 +18,7 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 ### Changed
 - Cloudflare MCP installs now use OAuth interactive login (no API token required).
 - Prompt generator spec now uses `verification_url` (empty allowed) instead of `int_url`.
+- Prompt generator templates now use verification-environment wording and status tokens (`P1_DONE_DEPLOYED`, `P3_REFACTORED_DEPLOYED`) while still accepting legacy INT tokens.
 
 ### Fixed
 - Improved MCP list parsing to detect Gemini CLI entries with checkmarks and ANSI colors.

src/features/prompt_gen/models.rs

@@ -266,7 +266,7 @@ pub struct FeatureSpec {
     /// 驗證 URL（可為空）
     pub verification_url: VerificationUrl,
 
-    /// INT 環境憑證（選填）
+    /// 驗證環境憑證（選填）
     #[serde(default)]
     pub int_credentials: OptionalTextContent,
 

src/features/prompt_gen/progress.rs

@@ -22,11 +22,11 @@ pub enum Step {
     None,
     /// 步驟 1: 需求與交付
     P1,
-    /// 步驟 2: INT E2E 驗證
+    /// 步驟 2: 驗證環境 E2E 驗證
     P2,
     /// 步驟 3: 重構與優化
     P3,
-    /// 步驟 4: INT E2E 回歸
+    /// 步驟 4: 驗證環境 E2E 回歸
     P4,
 }
 
@@ -83,10 +83,10 @@ impl Step {
     pub fn description(&self) -> &'static str {
         match self {
             Step::None => "未開始",
-            Step::P1 => "需求、實作、部署（INT）",
-            Step::P2 => "INT E2E 驗證",
+            Step::P1 => "需求、實作、部署（驗證環境）",
+            Step::P2 => "驗證環境 E2E 驗證",
             Step::P3 => "重構、流程優化、品質提升",
-            Step::P4 => "INT E2E 回歸驗證",
+            Step::P4 => "驗證環境 E2E 回歸驗證",
         }
     }
 
@@ -111,11 +111,11 @@ impl fmt::Display for Step {
 pub enum FeatureStatus {
     /// 未知狀態
     Unknown,
-    /// P1 完成並部署到 INT
+    /// P1 完成並部署
     P1DoneIntDeployed,
     /// P2 E2E 通過
     P2E2EPassed,
-    /// P3 重構完成並部署到 INT
+    /// P3 重構完成並部署
     P3RefactoredIntDeployed,
     /// 就緒
     Ready,
@@ -126,9 +126,11 @@ impl FeatureStatus {
     pub fn from_str(s: &str) -> Self {
         let s = s.trim().to_uppercase();
         match s.as_str() {
-            "P1_DONE_INT_DEPLOYED" => Self::P1DoneIntDeployed,
+            "P1_DONE_DEPLOYED" | "P1_DONE_INT_DEPLOYED" => Self::P1DoneIntDeployed,
             "P2_E2E_PASSED" => Self::P2E2EPassed,
-            "P3_REFACTORED_INT_DEPLOYED" => Self::P3RefactoredIntDeployed,
+            "P3_REFACTORED_DEPLOYED" | "P3_REFACTORED_INT_DEPLOYED" => {
+                Self::P3RefactoredIntDeployed
+            }
             "READY" => Self::Ready,
             _ => Self::Unknown,
         }
@@ -144,9 +146,9 @@ impl fmt::Display for FeatureStatus {
     fn fmt(&self, f: &mut fmt::Formatter<'_>) -> fmt::Result {
         let s = match self {
             Self::Unknown => "UNKNOWN",
-            Self::P1DoneIntDeployed => "P1_DONE_INT_DEPLOYED",
+            Self::P1DoneIntDeployed => "P1_DONE_DEPLOYED",
             Self::P2E2EPassed => "P2_E2E_PASSED",
-            Self::P3RefactoredIntDeployed => "P3_REFACTORED_INT_DEPLOYED",
+            Self::P3RefactoredIntDeployed => "P3_REFACTORED_DEPLOYED",
             Self::Ready => "READY",
         };
         write!(f, "{}", s)
@@ -387,6 +389,10 @@ LAST_DONE="p2"
     #[test]
     fn test_feature_status_parse() {
         assert_eq!(FeatureStatus::from_str("READY"), FeatureStatus::Ready);
+        assert_eq!(
+            FeatureStatus::from_str("P1_DONE_DEPLOYED"),
+            FeatureStatus::P1DoneIntDeployed
+        );
         assert_eq!(
             FeatureStatus::from_str("P1_DONE_INT_DEPLOYED"),
             FeatureStatus::P1DoneIntDeployed

src/features/prompt_gen/renderer.rs

@@ -111,7 +111,7 @@ impl PromptRenderer {
             .replace("{REQUIREMENTS_BLOCK}", requirements_block)
             .replace("{ACCEPTANCE_BLOCK}", acceptance_block)
             .replace("{VERIFICATION_URL}", verification_url)
-            .replace("{INT_CREDENTIALS_BLOCK}", int_credentials_block)
+            .replace("{VERIFICATION_CREDENTIALS_BLOCK}", int_credentials_block)
             .replace("{STATE_REQUIREMENT}", state_requirement)
     }
 
@@ -217,8 +217,7 @@ mod tests {
         let prompts = PromptRenderer::render(&spec);
         let prompt_03 = &prompts.prompts[2].content;
 
-        assert!(prompt_03.contains("frontend-design skill"));
-        assert!(prompt_03.contains("chrome-devtools"));
+        assert!(prompt_03.contains("visual direction"));
     }
 
     #[test]
@@ -227,6 +226,6 @@ mod tests {
         let prompts = PromptRenderer::render(&spec);
         let prompt_03 = &prompts.prompts[2].content;
 
-        assert!(!prompt_03.contains("frontend-design skill"));
+        assert!(!prompt_03.contains("visual direction"));
     }
 }

src/features/prompt_gen/templates/frontend_section.rs

@@ -4,14 +4,13 @@
 ///
 /// 佔位符：
 /// - `{IS_FRONTEND}`: 是否為前端功能
-pub const FRONTEND_SECTION: &str = r#"## （條件式）前端設計強化（只有當 {IS_FRONTEND} = true 才執行）
-若此功能是前端，請額外遵守：
-- 使用 mcp chrome-devtools 輔助開發，必須測試不跑版、無錯誤、UI/UX 優秀
-- Use the frontend-design skill
-- 先詳細分析配色與設計方案（暗色系、有質感、低調專業、舒適配色）
-- 重新設計元件顏色：高辨識度但不花俏；布局合理且簡潔
-- 大量互動與動畫：
-  - hover/focus/active feedback
-  - 送出按鈕必須有明確回饋（loading/success/error）
-- 移除不需要的 code/邏輯，同時 build 必須通過
+pub const FRONTEND_SECTION: &str = r#"## (Conditional) Frontend Design and UX (Only when {IS_FRONTEND} = true)
+If this feature includes frontend work, also follow:
+- Use browser developer tools or available automation to validate; ensure no layout breakage, no errors, and reasonable UX
+- Define a clear visual direction (typography, color, hierarchy, spacing) and keep it consistent and readable
+- Use colors that are easy to distinguish without being harsh; keep layout simple and information hierarchy clear
+- Interactions and motion must provide explicit feedback:
+  - hover/focus/active
+  - primary actions must show loading/success/error states
+- Remove unnecessary code/logic while keeping build green
 "#;

src/features/prompt_gen/templates/state_requirement.rs

@@ -5,21 +5,21 @@
 /// 佔位符：
 /// - `{FEATURE_KEY}`: 功能鍵值
 pub const STATE_REQUIREMENT_BLOCK: &str = r#"
-## 狀態機（必須遵守，供 Runner 強制順序性）
-你必須在 `features/{FEATURE_KEY}/STATE.md` 維護以下欄位（若不存在就建立），並在每個 prompt 結束時更新：
+## State Machine (Required, for enforcing step order)
+You must maintain the following fields in `features/{FEATURE_KEY}/STATE.md` (create if missing) and update them at the end of each prompt:
 
 - FEATURE_KEY: {FEATURE_KEY}
 - STATUS: <one of>
-  - P1_DONE_INT_DEPLOYED
+  - P1_DONE_DEPLOYED
   - P2_E2E_PASSED
-  - P3_REFACTORED_INT_DEPLOYED
+  - P3_REFACTORED_DEPLOYED
   - READY
 
-本 prompt 的結束狀態要求：
-- Prompt #1 結束：STATUS 必須設為 `P1_DONE_INT_DEPLOYED`
-- Prompt #2 結束：STATUS 必須設為 `P2_E2E_PASSED`
-- Prompt #3 結束：STATUS 必須設為 `P3_REFACTORED_INT_DEPLOYED`
-- Prompt #4 結束：STATUS 必須設為 `READY`
+Required end status for each prompt:
+- Prompt #1 end: STATUS must be `P1_DONE_DEPLOYED`
+- Prompt #2 end: STATUS must be `P2_E2E_PASSED`
+- Prompt #3 end: STATUS must be `P3_REFACTORED_DEPLOYED`
+- Prompt #4 end: STATUS must be `READY`
 
-如果你做不到（例如仍有失敗的驗收項），你必須維持原狀態並在 STATE.md 清楚寫出原因與下一步。
+If you cannot meet the requirement (for example, failed acceptance items remain), keep the previous STATUS and clearly record the reason and next steps in STATE.md.
 "#;

src/features/prompt_gen/templates/template_01.rs

@@ -1,4 +1,4 @@
-//! 模板 01 - 需求、實作、部署（INT）
+//! 模板 01 - 需求、實作、部署（驗證環境）
 
 /// 第一階段模板：需求與交付
 ///
@@ -9,17 +9,17 @@
 /// - `{REQUIREMENTS_BLOCK}`: 需求區塊
 /// - `{ACCEPTANCE_BLOCK}`: 驗收條件區塊
 /// - `{VERIFICATION_URL}`: 驗證 URL（可為空）
-/// - `{INT_CREDENTIALS_BLOCK}`: INT 環境憑證
+/// - `{VERIFICATION_CREDENTIALS_BLOCK}`: 驗證環境憑證
 /// - `{STATE_REQUIREMENT}`: 狀態需求區塊
-pub const TEMPLATE_01: &str = r#"# [Feature] {FEATURE_KEY} - 需求、實作、部署（INT）
+pub const TEMPLATE_01: &str = r#"# [Feature] {FEATURE_KEY} - Requirements, Implementation, Deployment (Verification Environment)
 
-你是一位資深全端工程師/Tech Lead，在此 repo 內完成此功能並部署到 INT 環境。
-本輪工作（Prompt #1~#4）需要保持記憶與連貫性；但請同時把關鍵狀態寫進檔案，以便 runner 續跑。
+You are a senior full-stack engineer/Tech Lead. Implement this feature in the codebase and deploy it to the verification environment.
+This round of work (Prompt #1-#4) must remain coherent; also write key state to files so it can be continued later.
 
-## 強制工具要求（必須遵守）
-- 你必須使用 `sequential-thinking` 來做規劃（先規劃再動手）。
+## Planning Requirements (Must Follow)
+- Complete structured planning before implementation (use any planning tool if available).
 
-## 輸入資訊
+## Inputs
 - Feature Key: {FEATURE_KEY}
 - Feature Name: {FEATURE_NAME}
 
@@ -33,44 +33,44 @@ pub const TEMPLATE_01: &str = r#"# [Feature] {FEATURE_KEY} - 需求、實作、
 {ACCEPTANCE_BLOCK}
 
 - Verification URL (optional): {VERIFICATION_URL}
-- INT Credentials / Login Method (if needed):
-{INT_CREDENTIALS_BLOCK}
+- Verification Credentials / Login Method (if needed):
+{VERIFICATION_CREDENTIALS_BLOCK}
 
 {STATE_REQUIREMENT}
 
-## 產出與落檔（必須）
-在 `features/{FEATURE_KEY}/` 產出並維護以下檔案（若不存在就建立）：
-1) `STATE.md`：本輪狀態（本 prompt 的決策、已完成項、待辦、風險、如何在 int 驗證；含 STATUS 欄位）
-2) `E2E_PLAN.md`：可在瀏覽器執行的端到端測試清單（步驟要非常具體）
-3) `ACCEPTANCE.md`：把驗收條件轉成可檢查項（checklist）
-4) `RUNBOOK_INT.md`：如何部署/如何回滾/需要的設定
-5) `CHANGELOG.md`：本功能變更摘要（面向 reviewer）
-
-## 執行流程（請嚴格照順序）
-1) 使用 `sequential-thinking`：
-   - 讀 repo 結構、關聯模組與既有行為
-   - 澄清需求與邊界（缺資訊時：做合理假設並寫入 `STATE.md`，不要卡住）
-   - 設計方案：資料流/模組邊界/錯誤處理/觀測性/測試策略
-   - 拆出可交付的最小步驟（每一步可 build、可測、可回退）
-
-2) 實作：
-   - 實作功能與必要的後端/前端改動（依 repo 慣例）
-   - 補齊必要測試（單元/整合，至少涵蓋主要成功路徑與重要失敗路徑）
-   - 確保 lint/format/typecheck/build 通過
-
-3) 部署到 INT：
-   - 依 repo 的部署方式完成部署
-   - 將部署方式、版本/commit、設定差異寫入 `RUNBOOK_INT.md` 與 `STATE.md`
-
-4) 收尾：
-   - 更新 `E2E_PLAN.md`（讓下一個 Prompt #2 可以直接照做）
-   - 更新 `STATE.md`，並把 STATUS 設為 `P1_DONE_INT_DEPLOYED`
-
-## 重要約束
-- 憑證/金鑰/Token 不得寫進程式碼或 repo。需要時請使用環境變數或既有 secret 機制。
-
-## 最終回覆格式（必須）
-- 本 prompt 完成摘要（含已部署到 INT 的證據：版本/commit/tag、部署位置）
-- STATE.md 狀態（包含 STATUS）
-- 下一步（Prompt #2）執行指引（對應 `E2E_PLAN.md`）
+## Required Artifacts (Must Produce)
+Create and maintain the following files under `features/{FEATURE_KEY}/` (create if missing):
+1) `STATE.md`: Current state (decisions, completed items, TODOs, risks, how to validate in the verification environment; include STATUS field)
+2) `E2E_PLAN.md`: Browser-executable end-to-end checklist (steps must be precise)
+3) `ACCEPTANCE.md`: Convert acceptance criteria into a checklist
+4) `RUNBOOK_VERIFICATION.md`: How to deploy, rollback, and required configuration
+5) `CHANGELOG.md`: Feature change summary (reviewer-facing)
+
+## Execution Flow (Strict Order)
+1) Structured planning:
+   - Review codebase structure, related modules, and current behavior
+   - Clarify requirements and boundaries (if missing info, make reasonable assumptions and record in `STATE.md`)
+   - Design the solution: data flow, module boundaries, error handling, observability, test strategy
+   - Break into minimal deliverable steps (each step should build, test, and be reversible)
+
+2) Implementation:
+   - Implement required backend/frontend changes following codebase conventions
+   - Add necessary tests (unit/integration; cover key success and failure paths)
+   - Ensure lint/format/typecheck/build pass
+
+3) Deploy to the verification environment:
+   - Follow the codebase deployment approach
+   - Record deployment method, version/commit, and config differences in `RUNBOOK_VERIFICATION.md` and `STATE.md`
+
+4) Wrap-up:
+   - Update `E2E_PLAN.md` (so Prompt #2 can follow it directly)
+   - Update `STATE.md` and set STATUS to `P1_DONE_DEPLOYED`
+
+## Important Constraints
+- Credentials/keys/tokens must not be committed to the codebase. Use environment variables or existing secret mechanisms.
+
+## Final Response Format (Required)
+- Summary of work completed (include evidence of verification deployment: version/commit/tag and target location)
+- STATE.md status (including STATUS)
+- Guidance for Prompt #2 (aligned with `E2E_PLAN.md`)
 "#;

src/features/prompt_gen/templates/template_02.rs

@@ -1,39 +1,39 @@
-//! 模板 02 - INT E2E 驗證
+//! 模板 02 - 驗證環境 E2E 驗證
 
-/// 第二階段模板：INT E2E 驗證（直到符合預期）
+/// 第二階段模板：驗證環境 E2E 驗證（直到符合預期）
 ///
 /// 佔位符：
 /// - `{FEATURE_KEY}`: 功能鍵值
 /// - `{STATE_REQUIREMENT}`: 狀態需求區塊
-pub const TEMPLATE_02_FIXED: &str = r#"# [Fixed] INT E2E 驗證（直到符合預期）
+pub const TEMPLATE_02_FIXED: &str = r#"# [Fixed] Verification Environment E2E Validation (Until Passing)
 
-你正在延續同一輪（Feature）的 session，請使用前一個 prompt 的記憶與 repo 產物來做 E2E。
-目標：在 INT 環境用真實瀏覽器把功能完整驗證到符合預期；若不符合，請修復、重新部署、再測到通過。
+You are continuing the same feature context. Use the previous prompt outputs and codebase artifacts to run E2E.
+Goal: validate the feature end-to-end in the verification environment using a real browser. If it fails, fix, redeploy, and retest until it passes.
 
-## 強制工具要求（必須）
-- 你必須使用 `sequential-thinking` 來規劃 E2E 執行與修復策略。
-- 你必須使用 `mcp chrome-devtools` 打開 INT 網站，進行全面端到端測試（包含 console/network/error 等檢查）。
+## Tooling Requirements (Must Follow)
+- Use structured planning to schedule E2E execution and remediation.
+- Use a real browser and developer tools for comprehensive end-to-end testing (including console/network/error checks).
 
 {STATE_REQUIREMENT}
 
-## 操作規範（必須）
-1) 讀取並遵循：
+## Operating Rules (Must Follow)
+1) Read and follow:
    - `features/{FEATURE_KEY}/E2E_PLAN.md`
    - `features/{FEATURE_KEY}/ACCEPTANCE.md`
-   - `features/{FEATURE_KEY}/RUNBOOK_INT.md`
+   - `features/{FEATURE_KEY}/RUNBOOK_VERIFICATION.md`
    - `features/{FEATURE_KEY}/STATE.md`
 
-2) 用 `mcp chrome-devtools` 在 INT 執行測試（逐步檢查畫面、互動、console/network）
-3) 若失敗：修復 → 測試 → 部署 INT → 再驗證（直到通過）
-4) 通過後：
-   - 更新 `E2E_RUN_REPORT.md`
-   - 更新 `STATE.md`，並把 STATUS 設為 `P2_E2E_PASSED`
+2) Execute tests in the verification environment with a real browser (step-by-step UI/interaction/console/network checks)
+3) If failing: fix -> test -> deploy to the verification environment -> re-validate (until passing)
+4) When passing:
+   - Update `E2E_RUN_REPORT.md`
+   - Update `STATE.md` and set STATUS to `P2_E2E_PASSED`
 
-## 停止條件
-- 只有在 `ACCEPTANCE.md` 全部打勾、且 E2E 核心流程與重要失敗情境皆通過，才能宣告完成此 prompt。
+## Stop Condition
+- You may only complete this prompt when all items in `ACCEPTANCE.md` are checked off and the core E2E flows plus key failure scenarios pass.
 
-## 最終回覆格式（必須）
-- E2E 通過摘要（對應 `ACCEPTANCE.md`）
-- STATE.md 狀態（包含 STATUS）
-- 下一步（Prompt #3）建議的重構/優化方向
+## Final Response Format (Required)
+- E2E pass summary (aligned with `ACCEPTANCE.md`)
+- STATE.md status (including STATUS)
+- Guidance for Prompt #3 refactoring/optimization
 "#;