pi-maestro-flow 0.2.0

package/skills/quality-test/SKILL.md

@@ -0,0 +1,183 @@
+---
+name: quality-test
+description: "Use when implementation needs user acceptance testing with interactive verification and gap closure Arguments: [phase] [--smoke] [--auto-fix] [--frontend-verify]"
+allowed-tools: Read Write Edit Bash Glob Grep Agent AskUserQuestion
+---
+
+<purpose>
+UAT-style conversational testing for a completed phase. Interactive scenario walk-through with severity inference. Issues trigger parallel debug agents and optional gap-fix loop (--auto-fix).
+</purpose>
+
+<required_reading>
+@~/.maestro/workflows/test.md
+</required_reading>
+
+<context>
+Phase or task: $ARGUMENTS (optional)
+
+Flags, artifact context resolution, and output directory format defined in workflow test.md.
+
+**Output boundary**: ALL file writes MUST target `.workflow/scratch/{YYYYMMDD}-test-P{N}-{slug}/`, `.workflow/state.json`, or `.workflow/issues.jsonl` only. NEVER modify source code or execution artifacts outside these paths. `--frontend-verify` additionally writes `e2e-results.json` to the same scratch directory.
+</context>
+
+<invariants>
+1. **UAT is observational** — test execution observes behavior and records results. NEVER modify source code during testing. Source fixes belong to debug→plan→execute cycle.
+2. **Severity is inferred, not asked** — severity MUST be inferred from user's natural language description of issues. NEVER explicitly ask the user to assign severity levels.
+3. **One scenario at a time** — tests MUST be presented individually for user verification. NEVER batch-present multiple scenarios or assume outcomes.
+4. **Evidence before verdict** — UAT confidence MUST be scored with the 4-dimension factor model from actual test results. NEVER emit a verdict without running the readiness gate.
+5. **Existing UAT is resumable** — when uat.md exists for the target phase, offer resume. NEVER silently overwrite prior test progress.
+6. **Frontend-verify is deterministic** — `--frontend-verify` mode uses browser assertions with concrete pass/fail per criterion. NEVER treat "no response" or timeout as pass.
+7. **Auto-fix has bounds** — `--auto-fix` gap-fix loop MUST NOT exceed 2 iterations. Persistent failures escalate to debug, not infinite retry.
+</invariants>
+
+<execution>
+**Mode select:** `--frontend-verify` → 走下方 **Frontend Verify Mode**（确定性浏览器 smoke，**不是**对话式 UAT）；否则 Follow '~/.maestro/workflows/test.md' completely.
+
+### Frontend Verify Mode (`--frontend-verify`)
+
+1. **Resolve targets**: 读 phase 的 `plan.json` / `.task/TASK-*.json`，提取所有 `[UI-observable]` convergence.criteria（plan 阶段产出）；缺失则枚举后端写端点（POST/PUT/PATCH/DELETE）作为待验证清单。
+2. **Start app**: `next start`（或从 dashboard/package.json 解析的既有启动脚本）；启动失败 → E003。
+3. **Drive browser**: 用 chrome-devtools MCP（`mcp__claude_dms3-chrome-devtools__*`：navigate / click / fill / take_snapshot / list_network_requests）逐条执行每个 `[UI-observable]` 流程，断言：UI 入口存在且可触发 → 对应写请求返回 2xx → DOM 出现预期结果。
+4. **Write evidence**: 产出 `e2e-results.json`（结构见下），逐条记 pass/fail + 证据（网络状态码、快照引用）。**确定性断言，禁止"无人应答=全过"**。
+5. **Verdict**: 任一 `[UI-observable]` fail 或写端点无 UI 入口 → STATUS=NEEDS_RETRY（ralph 经 post-frontend-verify 触发 Fix-Loop）；全过 → DONE。
+
+```json
+// e2e-results.json
+{ "phase": "{phase}", "app_url": "http://localhost:3000",
+  "checks": [ { "criterion": "[UI-observable] ...", "ui_entry": "<selector/route>",
+    "request": "POST /api/notes", "status": 201, "dom_assert": "list shows new item",
+    "passed": true } ],
+  "summary": { "total": 0, "passed": 0, "failed": 0 }, "verdict": "pass|fail" }
+```
+
+Ralph-invoked 完成：`maestro ralph complete <idx> --status {STATUS} --evidence e2e-results.json`。
+
+---
+
+Follow '~/.maestro/workflows/test.md' completely.
+
+### Phase Gates (MANDATORY, BLOCKING)
+
+**GATE 1: Setup → Test Design**
+- REQUIRED: Target resolved (phase or scratch task). E001 if missing.
+- REQUIRED: Smoke tests pass (if --smoke). E003 if fail.
+- BLOCKED if missing: cannot design tests without resolved target.
+
+**GATE 2: Test Design → Execution**
+- REQUIRED: test-plan.json generated with categorized tests mapped to requirements.
+- REQUIRED: uat.md created or resumed.
+- BLOCKED if plan missing: do not start interactive testing without plan.
+
+**GATE 3: Execution → Completion**
+- REQUIRED: All tests presented and responses processed.
+- REQUIRED: UAT confidence scored with 4-dimension factor model.
+- REQUIRED: Pressure pass completed if > 80% pass rate.
+- BLOCKED if incomplete: finish all scenarios before reporting.
+
+**Command-specific extensions (not in workflow):**
+
+**Knowledge context loading** (before test design):
+- Wiki search: `maestro search "<phase/feature keywords>" --json` → prior test strategies, recipes, decisions
+- Role knowledge: `maestro search --category test` → select relevant → `maestro load --type knowhow --id <id>`
+- Specs + tools: `maestro load --type spec --category test` → test conventions + discoverable knowhow tools
+
+**Test tool discovery** (knowhow tools as scenario source):
+- Load registered test tools: `maestro load --type spec --category test --keyword <feature>`
+- If tools found, extract their steps as additional test scenarios marked `source: "tool"`
+- Each numbered step in a tool becomes a UAT test with its assertion as `expected` behavior
+
+**Review findings integration** (from related review artifacts):
+- Extract critical/high findings as additional test scenarios, marked `source: "review_finding"`
+- When review verdict is "BLOCK" and review-finding tests fail, auto-enter gap-fix loop
+
+**Debug root cause integration** (from related debug artifacts):
+- Generate regression test scenarios from confirmed root causes, marked `source: "debug_root_cause"`
+
+**Register artifact on completion:**
+
+Confirm before writing:
+```
+AskUserQuestion("Register test artifact TST-{NNN} in state.json? (yes/no)")
+→ yes: proceed with write
+→ no: skip registration, continue to completion
+```
+
+```
+Append to state.json.artifacts[]:
+{
+  id: nextArtifactId(artifacts, "test"),  // TST-001
+  type: "test",
+  milestone: current_milestone,
+  phase: target_phase,
+  scope: "phase",
+  path: "scratch/{YYYYMMDD}-test-P{N}-{slug}",
+  status: issues == 0 ? "completed" : "failed",
+  depends_on: exec_art.id,
+  harvested: false,
+  created_at: start_time,
+  completed_at: now()
+}
+```
+
+</execution>
+
+<completion>
+### Standalone report
+
+```
+--- COMPLETION STATUS ---
+STATUS: DONE|DONE_WITH_CONCERNS|NEEDS_RETRY
+CONCERNS: {description if applicable}
+--- END STATUS ---
+```
+
+### Ralph-invoked completion
+
+End the step by calling the CLI (no text block output):
+```
+maestro ralph complete <idx> --status {STATUS} [--evidence {path}]
+```
+
+### Next-step routing
+
+| Condition | Suggestion |
+|-----------|-----------|
+| All tests pass | `/maestro-milestone-audit` |
+| --auto-fix succeeded | `/maestro-execute {phase}` |
+| --auto-fix gaps remain | `/quality-debug --from-uat {phase}` |
+| Manual fix needed | `/quality-debug --from-uat {phase}` |
+| Coverage below threshold | `/quality-auto-test {phase}` |
+</completion>
+
+<error_codes>
+| Code | Severity | Condition | Recovery |
+|------|----------|-----------|----------|
+| E001 | error | Phase or task target required (no active sessions) | Prompt user for phase number |
+| E002 | error | Phase not verified yet (no verification.json) | Suggest `/maestro-execute` first (verification is built-in) |
+| E003 | error | Smoke test failed (app won't start) | Suggest `/quality-debug` |
+| W001 | warning | One or more test scenarios failed | Auto-diagnose, suggest fix options |
+| W002 | warning | Coverage below threshold | Suggest `/quality-auto-test` |
+</error_codes>
+
+<success_criteria>
+- [ ] Target resolved (phase or scratch task)
+- [ ] Active sessions checked, resume offered if applicable
+- [ ] Smoke tests run if --smoke flag set
+- [ ] test-plan.json generated with categorized tests mapped to requirements
+- [ ] uat.md created/resumed with all tests
+- [ ] Tests presented one at a time with expected behavior
+- [ ] User responses processed as pass/issue/skip
+- [ ] Severity inferred from natural language (never asked)
+- [ ] Batched writes: on issue, every 5 passes, or completion
+- [ ] test-results.json and coverage-report.json written
+- [ ] UAT confidence scored with 4-dimension factor model
+- [ ] Readiness gate checked before final report
+- [ ] Pressure pass completed if > 80% pass rate
+- [ ] Confidence summary appended to uat.md
+- [ ] index.json uat fields updated
+- [ ] If issues: confirm with user before spawning parallel debug agents per gap cluster
+- [ ] Gaps updated with root_cause, fix_direction, affected_files
+- [ ] Gap-fix loop triggered if --auto-fix (max 2 iterations)
+- [ ] Next step routed (phase-transition if pass, verify if auto-fix success, debug --from-uat if issues, test-gen if low coverage)
+- [ ] `--frontend-verify`: 每条 [UI-observable] criterion 经真实浏览器断言，产出 e2e-results.json；任一 fail → NEEDS_RETRY（不放行）
+</success_criteria>

package/skills/scholar-anti-ai-writing/SKILL.md

@@ -0,0 +1,173 @@
+---
+name: scholar-anti-ai-writing
+description: "Remove AI writing patterns from academic prose. Detects and fixes inflated symbolism, promotional language, superficial analyses, vague attributions, AI vocabulary, and formulaic structures. Supports English and Chinese. Triggers on \"remove AI patterns\", \"humanize text\", \"anti-AI polish\", \"去除AI写作痕迹\", \"人性化处理\"."
+allowed-tools: Read Write Edit Bash Glob Grep AskUserQuestion TodoWrite
+---
+
+# Scholar Anti-AI Writing
+
+Detect and eliminate AI writing patterns from academic prose. Based on Wikipedia's "Signs of AI writing" guide. Supports both English and Chinese text.
+
+**Core insight**: LLMs predict the most statistically likely outcome — creating detectable patterns. This skill identifies and rewrites those patterns while preserving meaning and adding authentic voice.
+
+## Pre-load (before execution)
+
+1. **Codebase docs**: If `.workflow/codebase/ARCHITECTURE.md` exists, read for project context
+2. **Specs**: `maestro load --type spec --category coding` — load coding conventions
+3. **Wiki knowledge**: `maestro search "academic writing research paper" --json` — top 5 entries as prior context
+4. All optional — proceed without if unavailable
+
+## Architecture Overview
+
+```
+User: "Remove AI patterns from my paper"
+         |
+         v
+┌──────────────────────────────────────────────────────────────┐
+│  SKILL.md (Orchestrator)                                      │
+│  Collect preferences → Dispatch phases → Track progress       │
+└──────────┬───────────────────────────────────────────────────┘
+           |
+   ┌───────┼───────────┬──────────────┐
+   v       v           v              v
+┌──────┐┌──────────┐┌──────────────┐
+│ P1   ││ P2       ││ P3           │
+│Detect││ Rewrite  ││ Validate     │
+│ &    ││ & Polish ││ & Score      │
+│Score ││          ││              │
+└──┬───┘└────┬─────┘└──────┬───────┘
+   │         │             │
+   v         v             v
+ pattern   polished     final score
+ report    prose        + diff report
+```
+
+## Key Design Principles
+
+1. **Pattern detection + soul injection**: Removing AI patterns is only half the job — add authentic voice.
+2. **Preserve meaning**: Core content and technical claims must remain intact.
+3. **Language-aware**: English and Chinese have different AI pattern signatures.
+4. **Scoring-driven**: Quantitative 5-dimension scoring (50-point scale) guides revision.
+5. **Academic tone**: Maintain scholarly register — humanize without becoming informal.
+
+## Interactive Preference Collection
+
+Before dispatching to any phase, collect these preferences:
+
+```
+Questions to ask the user:
+
+1. Input Source
+   "What text should I process? (file path, directory, or paste text)"
+   → inputSource
+
+2. Language
+   Options: English | Chinese | Bilingual (auto-detect per section)
+   → language
+
+3. Writing Context
+   Options: Academic Paper | Technical Report | Blog/Article | General Prose
+   → writingContext
+
+4. Aggressiveness
+   Options: Conservative (minimal changes) | Balanced (Recommended) | Aggressive (heavy rewrite)
+   → aggressiveness
+```
+
+Store responses as `antiAiPreferences` context for all phases.
+
+## Auto Mode Defaults
+
+When `workflowPreferences.autoYes === true`:
+- Process all .tex files in cwd
+- Auto-detect language
+- Academic Paper context, Balanced aggressiveness
+- Skip confirmation prompts
+
+## Execution Flow
+
+> **COMPACT DIRECTIVE**: Context compression MUST check TodoWrite phase status.
+> The phase currently marked `in_progress` is the active execution phase — preserve its FULL content.
+> Only compress phases marked `completed` or `pending`.
+
+### TodoWrite Setup
+
+```
+Anti-AI Writing:
+- [ ] Phase 1: Detect & Score — scan for AI patterns, generate initial score
+- [ ] Phase 2: Rewrite & Polish — rewrite flagged sections, add voice
+- [ ] Phase 3: Validate & Score — re-score, verify quality threshold
+```
+
+### Phase Sequence
+
+```
+Phase 1: Detect & Score
+   └─ Ref: phases/01-detect-score.md
+      ├─ Input: inputSource, language
+      └─ Output: patternReport (flagged passages + initial scores)
+
+Phase 2: Rewrite & Polish
+   └─ Ref: phases/02-rewrite-polish.md
+      ├─ Input: patternReport, writingContext, aggressiveness
+      └─ Output: polishedText (rewritten content)
+
+Phase 3: Validate & Score
+   └─ Ref: phases/03-validate-score.md
+      ├─ Input: polishedText, original text
+      └─ Output: finalReport (before/after scores, diff)
+```
+
+**Phase Reference Documents** (read on-demand when phase executes):
+
+| Phase | Document | Purpose | Compact |
+|-------|----------|---------|---------|
+| 1 | [phases/01-detect-score.md](phases/01-detect-score.md) | Scan patterns, score text | TodoWrite driven |
+| 2 | [phases/02-rewrite-polish.md](phases/02-rewrite-polish.md) | Rewrite and humanize | TodoWrite driven + sentinel |
+| 3 | [phases/03-validate-score.md](phases/03-validate-score.md) | Re-score, generate report | TodoWrite driven |
+
+**Compact Rules**:
+1. **TodoWrite `in_progress`** → preserve full content, do not compress
+2. **TodoWrite `completed`** → may compress to summary
+3. **sentinel fallback** → phases marked with sentinel contain compact sentinel; if only sentinel remains, **must immediately `Read()` to recover**
+
+## Core Rules
+
+1. **Never lose meaning**: Technical claims, data, and specific facts must survive rewriting.
+2. **Score before and after**: Every processed text gets a 5-dimension score (50-point scale).
+3. **Flag, don't force**: In Conservative mode, highlight issues but let the user decide.
+4. **Academic register**: For papers, maintain formal-but-natural tone. No slang or casual language.
+5. **Minimum threshold**: Target score >= 35/50 for academic papers, >= 40/50 for submission-ready.
+
+## Quick Scoring System (5 dimensions, 10 points each)
+
+| Dimension | Question | Target |
+|-----------|----------|--------|
+| **Directness** | Direct statements or announcements? | >= 7 |
+| **Rhythm** | Varied or metronomic? | >= 7 |
+| **Trust** | Respects reader intelligence? | >= 7 |
+| **Authenticity** | Sounds human? | >= 7 |
+| **Density** | Anything cuttable? | >= 7 |
+
+## Data Flow
+
+```
+Phase 1 ──patternReport──→ Phase 2
+Phase 2 ──polishedText──→ Phase 3
+Phase 1 ──originalText──→ Phase 3 (for comparison)
+```
+
+## Error Handling
+
+| Error | Action |
+|-------|--------|
+| File not found | Ask user for correct path |
+| Mixed languages in one file | Process each section in detected language |
+| Score below threshold after rewrite | Flag for manual review, suggest specific areas |
+| LaTeX commands broken during rewrite | Preserve LaTeX structure, only modify prose content |
+| User disagrees with changes | Offer side-by-side diff, allow per-section accept/reject |
+
+## Related Skills
+
+- **scholar-writing**: Phase 5 (Anti-AI Polish) uses this skill's patterns
+- **scholar-review**: Uses scoring to assess writing quality

package/skills/scholar-anti-ai-writing/references/patterns-chinese.md

@@ -0,0 +1,242 @@
+# 中文 AI 写作模式 - 完整参考
+
+Complete Chinese AI Writing Patterns Reference.
+
+## 内容模式 (CONTENT PATTERNS)
+
+### 1. 过度强调意义、遗产和更广泛的趋势
+
+**需要注意的词汇**：作为/充当、标志着/见证、是……的体现/证明/提醒、极其重要的/重要的/至关重要的/核心的/关键性的作用/时刻、凸显/强调/彰显了其重要性/意义、反映了更广泛的、象征着其持续的/永恒的/持久的、为……做出贡献、为……奠定基础、标志着/塑造着、代表/标志着一个转变、关键转折点、不断演变的格局、焦点、不可磨灭的印记、深深植根于
+
+**改写前**：
+> 加泰罗尼亚统计局于 1989 年正式成立，标志着西班牙区域统计演变史上的关键时刻。这一举措是西班牙全国范围内更广泛运动的一部分，旨在分散行政职能并加强区域治理。
+
+**改写后**：
+> 加泰罗尼亚统计局成立于 1989 年，负责独立于西班牙国家统计局收集和发布区域统计数据。
+
+---
+
+### 2. 过度强调知名度和媒体报道
+
+**需要注意的词汇**：独立报道、地方/区域/国家媒体、由知名专家撰写、活跃的社交媒体账号
+
+**改写前**：
+> 她的观点被《纽约时报》、BBC、《金融时报》和《印度教徒报》引用。她在社交媒体上拥有活跃的存在，拥有超过 50 万粉丝。
+
+**改写后**：
+> 在 2024 年《纽约时报》的采访中，她认为 AI 监管应该关注结果而不是方法。
+
+---
+
+### 3. 以 -ing 结尾的肤浅分析
+
+**需要注意的词汇**：突出/强调/彰显……、确保……、反映/象征……、为……做出贡献、培养/促进……、涵盖……、展示……
+
+**改写前**：
+> 寺庙的蓝色、绿色和金色色调与该地区的自然美景产生共鸣，象征着德克萨斯州的蓝帽花、墨西哥湾和多样化的德克萨斯州景观，反映了社区与土地的深厚联系。
+
+**改写后**：
+> 寺庙使用蓝色、绿色和金色。建筑师表示这些颜色是为了呼应当地的蓝帽花和墨西哥湾海岸。
+
+---
+
+### 4. 宣传和广告式语言
+
+**需要注意的词汇**：拥有（夸张用法）、充满活力的、丰富的（比喻）、深刻的、增强其、展示、体现、致力于、自然之美、坐落于、位于……的中心、开创性的（比喻）、著名的、令人叹为观止的、必游之地、迷人的
+
+**改写前**：
+> 坐落在埃塞俄比亚贡德尔地区令人叹为观止的区域内，Alamata Raya Kobo 是一座充满活力的城镇，拥有丰富的文化遗产和迷人的自然美景。
+
+**改写后**：
+> Alamata Raya Kobo 是埃塞俄比亚贡德尔地区的一座城镇，以其每周集市和 18 世纪教堂而闻名。
+
+---
+
+### 5. 模糊归因和含糊措辞
+
+**需要注意的词汇**：行业报告显示、观察者指出、专家认为、一些批评者认为、多个来源/出版物（实际引用却很少）
+
+**改写前**：
+> 由于其独特的特征，浩来河引起了研究人员和保护主义者的兴趣。专家认为它在区域生态系统中发挥着至关重要的作用。
+
+**改写后**：
+> 根据中国科学院 2019 年的调查，浩来河支持多种特有鱼类。
+
+---
+
+### 6. 提纲式的"挑战与未来展望"部分
+
+**需要注意的词汇**：尽管其……面临若干挑战……、尽管存在这些挑战、挑战与遗产、未来展望
+
+**改写前**：
+> 尽管工业繁荣，Korattur 面临着城市地区典型的挑战，包括交通拥堵和水资源短缺。尽管存在这些挑战，凭借其战略位置和正在进行的举措，Korattur 继续蓬勃发展，成为钦奈增长不可或缺的一部分。
+
+**改写后**：
+> 2015 年三个新 IT 园区开业后，交通拥堵加剧。市政公司于 2022 年启动了雨水排水项目，以解决反复发生的洪水。
+
+---
+
+## 语言和语法模式 (LANGUAGE PATTERNS)
+
+### 7. 过度使用的"AI 词汇"
+
+**高频 AI 词汇**：此外、与……保持一致、至关重要、深入探讨、强调、持久的、增强、培养、获得、突出（动词）、相互作用、复杂/复杂性、关键（形容词）、格局（抽象名词）、关键性的、展示、织锦（抽象名词）、证明、强调（动词）、宝贵的、充满活力的
+
+**改写前**：
+> 此外，索马里菜肴的一个显著特征是加入骆驼肉。意大利殖民影响的持久证明是当地烹饪格局中广泛采用意大利面，展示了这些菜肴如何融入传统饮食。
+
+**改写后**：
+> 索马里菜肴还包括骆驼肉，被认为是一种美味。在意大利殖民期间引入的意大利面菜肴仍然很常见，尤其是在南部。
+
+---
+
+### 8. 避免使用"是"（系动词回避）
+
+**需要注意的词汇**：作为/代表/标志着/充当 [一个]、拥有/设有/提供 [一个]
+
+**改写前**：
+> Gallery 825 作为 LAAA 的当代艺术展览空间。画廊设有四个独立空间，拥有超过 3000 平方英尺。
+
+**改写后**：
+> Gallery 825 是 LAAA 的当代艺术展览空间。画廊有四个房间，总面积 3000 平方英尺。
+
+---
+
+### 9. 否定式排比
+
+**改写前**：
+> 这不仅仅是节拍在人声下流动；它是攻击性和氛围的一部分。这不仅仅是一首歌，而是一种声明。
+
+**改写后**：
+> 沉重的节拍增加了攻击性的基调。
+
+---
+
+### 10. 三段式法则过度使用
+
+**改写前**：
+> 活动包括主题演讲、小组讨论和社交机会。与会者可以期待创新、灵感和行业洞察。
+
+**改写后**：
+> 活动包括演讲和小组讨论。会议之间还有非正式社交的时间。
+
+---
+
+### 11. 刻意换词（同义词循环）
+
+**改写前**：
+> 主人公面临许多挑战。主要角色必须克服障碍。中心人物最终获得胜利。英雄回到家中。
+
+**改写后**：
+> 主人公面临许多挑战，但最终获得胜利并回到家中。
+
+---
+
+### 12. 虚假范围
+
+**改写前**：
+> 我们穿越宇宙的旅程将我们从大爆炸的奇点带到宏伟的宇宙网，从恒星的诞生和死亡到暗物质的神秘舞蹈。
+
+**改写后**：
+> 这本书涵盖了大爆炸、恒星形成和当前关于暗物质的理论。
+
+---
+
+## 风格模式 (STYLE PATTERNS)
+
+### 13. 破折号过度使用
+
+**改写前**：
+> 这个术语主要由荷兰机构推广——而不是由人民自己。你不会说"荷兰，欧洲"作为地址——但这种错误标记仍在继续——即使在官方文件中。
+
+**改写后**：
+> 这个术语主要由荷兰机构推广，而不是由人民自己。你不会说"荷兰，欧洲"作为地址，但这种错误标记在官方文件中仍在继续。
+
+---
+
+### 14. 粗体过度使用
+
+**改写前**：
+> 它融合了 **OKR（目标和关键结果）**、**KPI（关键绩效指标）** 和视觉战略工具，如 **商业模式画布（BMC）** 和 **平衡计分卡（BSC）**。
+
+**改写后**：
+> 它融合了 OKR、KPI 和视觉战略工具，如商业模式画布和平衡计分卡。
+
+---
+
+### 15. 内联标题垂直列表
+
+**改写前**：
+> - **用户体验：** 用户体验通过新界面得到显著改善。
+> - **性能：** 性能通过优化算法得到增强。
+> - **安全性：** 安全性通过端到端加密得到加强。
+
+**改写后**：
+> 更新改进了界面，通过优化算法加快了加载时间，并添加了端到端加密。
+
+---
+
+## 交流模式 (COMMUNICATION PATTERNS)
+
+### 16. 协作交流痕迹
+
+**需要注意的词汇**：希望这对您有帮助、当然！、一定！、您说得完全正确！、您想要……、请告诉我、这是一个……
+
+**改写前**：
+> 这是法国大革命的概述。希望这对您有帮助！如果您想让我扩展任何部分，请告诉我。
+
+**改写后**：
+> 法国大革命始于 1789 年，当时财政危机和粮食短缺导致了广泛的动荡。
+
+---
+
+### 17. 知识截止日期免责声明
+
+**需要注意的词汇**：截至 [日期]、根据我最后的训练更新、虽然具体细节有限/稀缺……、基于可用信息……
+
+**改写前**：
+> 虽然关于公司成立的具体细节在现成资料中没有广泛记录，但它似乎是在 20 世纪 90 年代的某个时候成立的。
+
+**改写后**：
+> 根据注册文件，该公司成立于 1994 年。
+
+---
+
+## 填充模式 (FILLER PATTERNS)
+
+### 18. 填充短语
+
+| 改写前 | 改写后 |
+|--------|--------|
+| "为了实现这一目标" | "为了实现这一点" |
+| "由于下雨的事实" | "因为下雨" |
+| "在这个时间点" | "现在" |
+| "在您需要帮助的情况下" | "如果您需要帮助" |
+| "系统具有处理的能力" | "系统可以处理" |
+| "值得注意的是数据显示" | "数据显示" |
+
+---
+
+### 19. 过度限定
+
+**改写前**：
+> 可以潜在地可能被认为该政策可能会对结果产生一些影响。
+
+**改写后**：
+> 该政策可能会影响结果。
+
+---
+
+### 20. 通用积极结论
+
+**改写前**：
+> 公司的未来看起来光明。激动人心的时代即将到来，他们继续追求卓越的旅程。这代表了向正确方向迈出的重要一步。
+
+**改写后**：
+> 该公司计划明年再开设两个地点。
+
+---
+
+## 来源
+
+[基于维基百科：AI 写作特征](https://en.wikipedia.org/wiki/Wikipedia/Signs_of_AI_writing)