@guanlin4924/devflow-pi 0.1.93 → 0.1.95

package/plugins/devflow-design/skills/workflow-backend-tech-spec/SKILL.md

@@ -12,26 +12,26 @@ argument-hint: <功能名>
 user-invocable: true
 pattern: generator+tool-wrapper
 inputs:
-- .planning/features/{功能名}/api-contract.md
-- .planning/features/{功能名}/architecture-brief.md
-- .planning/features/{功能名}/architecture-brief.meta.json
-- .planning/requirements/baseline.md
-- .planning/features/{功能名}/功能点梳理.md (optional, Track B context when already available)
-- .planning/PROJECT.md
-- .planning/navigation/INDEX.md
-- .planning/rules/INDEX.md
-- .planning/execution-contract.md
-- .planning/toolchain.md
-- .planning/lessons/README.md
-- .context/spec/index.md
-- .context/spec/stacks/
-- .context/spec/backend/index.md
-- .context/spec/backend/
-- .context/workflow/
-- .context/lessons/README.md（如存在）
-- .planning/milestones/
+- .devflow/planning/features/{功能名}/api-contract.md
+- .devflow/planning/features/{功能名}/architecture-brief.md
+- .devflow/planning/features/{功能名}/architecture-brief.meta.json
+- .devflow/planning/requirements/baseline.md
+- .devflow/planning/features/{功能名}/功能点梳理.md (optional, Track B context when already available)
+- .devflow/planning/PROJECT.md
+- .devflow/planning/navigation/INDEX.md
+- .devflow/planning/rules/INDEX.md
+- .devflow/planning/execution-contract.md
+- .devflow/planning/toolchain.md
+- .devflow/planning/lessons/README.md
+- .devflow/context/spec/index.md
+- .devflow/context/spec/stacks/
+- .devflow/context/spec/backend/index.md
+- .devflow/context/spec/backend/
+- .devflow/context/workflow/
+- .devflow/context/lessons/README.md（如存在）
+- .devflow/planning/milestones/
 - references/affected-module-exploration.md
-output: .planning/features/{功能名}/后端技术方案.md
+output: .devflow/planning/features/{功能名}/后端技术方案.md
 allowed-tools:
 - Read
 - Write
@@ -46,7 +46,7 @@ allowed-tools:
 
 ## 需求追溯硬约束
 
-读取 `.planning/requirements/{feature}/traceability.json`。每个设计章节必须列 `覆盖 REQ: REQ-*`；定时任务、批处理、导入和通知至少拆为“编排（扫描/触发/锁/重试）”与“业务算法（判定/计算/写入）”两个可独立验证的小节。不得把遍历全部活跃组织、发送通知、文件解析等编排事实藏在算法描述中。
+读取 `.devflow/planning/requirements/{feature}/traceability.json`。每个设计章节必须列 `覆盖 REQ: REQ-*`；定时任务、批处理、导入和通知至少拆为“编排（扫描/触发/锁/重试）”与“业务算法（判定/计算/写入）”两个可独立验证的小节。不得把遍历全部活跃组织、发送通知、文件解析等编排事实藏在算法描述中。
 
 当架构简报包含 `analytics_query`、`analytics_projection`、`METRIC-*` 或 `RM-*` 时，后端方案额外必须分别写明：业务事实源；指标粒度/纳入排除/时区与修正；读模型或直接聚合路径；索引/扫描范围；新鲜度；watermark/迟到数据；重建与对账。不得把统计 SQL 混进事务命令，或以“后续补统计”跳过这些字段。
 
@@ -67,17 +67,17 @@ allowed-tools:
 
 ### 第一阶段：理解需求
 
-1. 读取 `.planning/requirements/baseline.md` 理解需求
-2. 读取 `.planning/PROJECT.md` 了解项目上下文
-3. 如果 baseline.md 不存在，询问用户需求或在 `.planning/milestones/` 中查找相关历史
-4. 读取 `references/project-rule-contract.md`，按 Spec Read Contract 发现并加载目标项目的后端规则包：`.planning/rules/INDEX.md` → `.context/spec/index.md` → 命中的 stack spec → 命中的 backend codebase spec → navigation → code-index（如存在且需要关系事实）→ 源码
+1. 读取 `.devflow/planning/requirements/baseline.md` 理解需求
+2. 读取 `.devflow/planning/PROJECT.md` 了解项目上下文
+3. 如果 baseline.md 不存在，询问用户需求或在 `.devflow/planning/milestones/` 中查找相关历史
+4. 读取 `references/project-rule-contract.md`，按 Spec Read Contract 发现并加载目标项目的后端规则包：`.devflow/planning/rules/INDEX.md` → `.devflow/context/spec/index.md` → 命中的 stack spec → 命中的 backend codebase spec → navigation → code-index（如存在且需要关系事实）→ 源码
 5. 读取 `references/code-explore-guide.md`，按项目导航和规则包做通用后端探索
 6. 读取 baseline 的 `反向审视与用户拍板`、`待确认事项`、`下游输入契约`：
    - 已确认的冲突/复用/替代方案决策必须进入技术方案
    - 影响 scope、语义、归属、兼容性或实现成本的未确认项，不得被当成已确认需求
    - 若未确认项阻塞后端方案，询问用户；`--auto` 或无法询问时写入待确认事项和风险
-7. 读取 `.planning/features/{功能名}/api-contract.md`。在双轨模式下，后端方案必须以 API 契约和需求基线作为权威输入，不得等待 Track B 的 `功能点梳理.md` 才开始。
-8. 读取 `.planning/features/{功能名}/architecture-brief.md` 和 `.meta.json`，在文档开头记录消费的 `brief_revision`、`graph_revision` 和 `static_context_snapshot_revision`。`comparison_status=confirmed` 的选择可作为实现依据；其他状态只能作为风险或待确认前提，不得把 recommendation 写成已决定实现。若 `assessment_level=full` 但未 confirmed，停止并回到架构评估。
+7. 读取 `.devflow/planning/features/{功能名}/api-contract.md`。在双轨模式下，后端方案必须以 API 契约和需求基线作为权威输入，不得等待 Track B 的 `功能点梳理.md` 才开始。
+8. 读取 `.devflow/planning/features/{功能名}/architecture-brief.md` 和 `.meta.json`，在文档开头记录消费的 `brief_revision`、`graph_revision` 和 `static_context_snapshot_revision`。`comparison_status=confirmed` 的选择可作为实现依据；其他状态只能作为风险或待确认前提，不得把 recommendation 写成已决定实现。若 `assessment_level=full` 但未 confirmed，停止并回到架构评估。
 9. 若 `功能点梳理.md` 已存在，可作为测试可读上下文补充读取；若不存在，不阻塞 Track A。
 10. 若 baseline、api-contract 或 `功能点梳理.md` 包含 `SL-*` 切片计划，读取 `skill://workflow-pipeline/references/slice-safety-guide.md`，只为当前执行切片生成后端方案。后置切片只可作为依赖上下文或后续范围，不得生成库表、接口、任务或运行时设计。
 
@@ -86,9 +86,9 @@ allowed-tools:
 在设计前，探索相关实现：
 
 1. **读取 PROJECT.md 的 Project Layout 章节**，确定后端代码所在目录
-2. 按 `references/project-rule-contract.md` 的顺序读取项目规则包，优先使用 `.planning/rules/INDEX.md` 和 `.context/spec/index.md` 匹配 stack/codebase spec，兼容 `.context/spec/`、`.context/workflow/`、`.context/lessons/` 和根目录 `AGENTS.md` / `CLAUDE.md`
-3. 读取 `.planning/navigation/INDEX.md` → 筛选后端/服务类型代码库 → 加载对应 `{name}.md` 导航文件，按目标项目实际结构识别领域/模型、服务、持久化、接口、任务、集成、配置和迁移入口
-4. 若 `.planning/code-index/` 存在，用 Symbol Index 和 Relation Graph 查询相关入口、调用链、读写资源、测试和外部集成候选；读取 `evidence_path:evidence_line` 后再写现状结论
+2. 按 `references/project-rule-contract.md` 的顺序读取项目规则包，优先使用 `.devflow/planning/rules/INDEX.md` 和 `.devflow/context/spec/index.md` 匹配 stack/codebase spec，兼容 `.devflow/context/spec/`、`.devflow/context/workflow/`、`.devflow/context/lessons/` 和根目录 `AGENTS.md` / `CLAUDE.md`
+3. 读取 `.devflow/planning/navigation/INDEX.md` → 筛选后端/服务类型代码库 → 加载对应 `{name}.md` 导航文件，按目标项目实际结构识别领域/模型、服务、持久化、接口、任务、集成、配置和迁移入口
+4. 若 `.devflow/planning/code-index/` 存在，用 Symbol Index 和 Relation Graph 查询相关入口、调用链、读写资源、测试和外部集成候选；读取 `evidence_path:evidence_line` 后再写现状结论
 5. **现有功能复用检查**：编写任何新逻辑前，必须先在项目中搜索是否已有相同或相似功能的实现。优先使用 code-index 查询 symbols/relations；缺失或过期时再按导航和 `rg` 兜底。搜索范围包括：
    - `pkg/` 目录（已有外部集成封装，如支付、红包、短信、二维码等）
    - Service 层（已有业务能力）
@@ -160,12 +160,12 @@ allowed-tools:
 
 ### 第三阶段：生成文档
 
-1. 创建 `.planning/features/{功能名}/` 目录
+1. 创建 `.devflow/planning/features/{功能名}/` 目录
 2. 读取 `assets/backend-spec-template.md` 模板
 3. 按模板结构填充内容，并写入 `需求基线衔接`、`后端规范影响`、`能力抽象建议` 章节
-4. 文件名格式：`.planning/features/{功能名}/后端技术方案.md`
+4. 文件名格式：`.devflow/planning/features/{功能名}/后端技术方案.md`
 
-If an older baseline still points to root `features/{功能名}/`, treat that as a legacy read path. New backend tech-spec output stays under `.planning/features/{功能名}/`.
+If an older baseline still points to root `features/{功能名}/`, treat that as a legacy read path. New backend tech-spec output stays under `.devflow/planning/features/{功能名}/`.
 
 ### 第三阶段.5 — ADR 创建（按需）
 
@@ -201,7 +201,7 @@ If an older baseline still points to root `features/{功能名}/`, treat that as
 - 兼容性：无影响
 ```
 
-**ADR 存放路径**：`.planning/architecture/adr/{序号}-{主题}.md`
+**ADR 存放路径**：`.devflow/planning/architecture/adr/{序号}-{主题}.md`
 
 **不满足条件时不要创建 ADR。** 常规决策（字段名选择、参数顺序等）直接写在方案里即可。
 
@@ -213,9 +213,9 @@ If an older baseline still points to root `features/{功能名}/`, treat that as
 
 ### 第五阶段：结构化元数据
 
-完成后写入 `.planning/features/{功能名}/后端技术方案.meta.json`。必须从 `architecture-brief.meta.json` 原样复制：`brief_revision → architecture_brief_revision`、`graph_revision → architecture_graph_revision`、`static_context_snapshot_revision → architecture_static_context_snapshot_revision`、`comparison_status → architecture_comparison_status`。不得凭记忆填写或改写这些值。
+完成后写入 `.devflow/planning/features/{功能名}/后端技术方案.meta.json`。必须从 `architecture-brief.meta.json` 原样复制：`brief_revision → architecture_brief_revision`、`graph_revision → architecture_graph_revision`、`static_context_snapshot_revision → architecture_static_context_snapshot_revision`、`comparison_status → architecture_comparison_status`。不得凭记忆填写或改写这些值。
 
-完成后写入 `.planning/features/{功能名}/后端技术方案.meta.json`，字段定义见 `feature-development.yaml` 中 `steps[backend-tech-spec].meta_output.fields`：`api_count`, `table_count`, `migration_count`。
+完成后写入 `.devflow/planning/features/{功能名}/后端技术方案.meta.json`，字段定义见 `feature-development.yaml` 中 `steps[backend-tech-spec].meta_output.fields`：`api_count`, `table_count`, `migration_count`。
 
 ## 注意事项
 
@@ -227,8 +227,8 @@ If an older baseline still points to root `features/{功能名}/`, treat that as
 6. **必须描述现有功能** — 新功能如果影响现有功能，必须先描述现有功能的流程、字段、逻辑
 7. **统计类功能要详细** — 对于涉及统计表的变更，必须说明：现有字段及含义、现有统计 SQL/逻辑、Job 调度频率、新增字段及统计逻辑
 8. **只关注后端逻辑** — 流程图只描述后端服务的处理流程，不要包含前端行为
-9. **必须体现项目规则包** — 若目标项目存在 `.planning/rules/` 或 `.context/spec/`，后端方案必须列出适用规范、相关经验教训、工具链要求、测试策略和审查门禁
-10. **历史口径使用 `.planning`** — 与历史相关的判断优先来自 `.planning/milestones/`、`.planning/requirements/`、`.planning/lessons/` 和阶段 `CONTEXT.md`；`features/` 或 `.context/lessons/` 只作为目标项目存在时的兼容来源
+9. **必须体现项目规则包** — 若目标项目存在 `.devflow/planning/rules/` 或 `.devflow/context/spec/`，后端方案必须列出适用规范、相关经验教训、工具链要求、测试策略和审查门禁
+10. **历史口径使用 `.devflow/planning`** — 与历史相关的判断优先来自 `.devflow/planning/milestones/`、`.devflow/planning/requirements/`、`.devflow/planning/lessons/` 和阶段 `CONTEXT.md`；`features/` 或 `.devflow/context/lessons/` 只作为目标项目存在时的兼容来源
 11. **现有功能复用优先** — 编写任何新逻辑前，必须先在项目内搜索已有实现，避免重复造轮子。重点检查：`pkg/` 外部集成封装、Service 层业务能力、Repository 层数据访问模式、公共工具方法。发现已有封装时直接复用，严禁绕过直接写裸调用
 12. **遵循最佳实践标杆** — 新功能的设计（分层、命名、错误处理、参数封装、测试模式）必须与项目内已有标杆功能保持一致，不得引入与项目验证过的成熟模式相悖的新模式。若需偏离，必须在方案中说明理由
 13. **能力抽象** — 新功能中具有独立复用价值的部分（外部集成、通用业务能力），必须抽象为 `pkg/` 级模块，定义清晰的 Client 接口和参数/结果结构体，形成可被后续功能消费的项目能力资产
@@ -241,7 +241,7 @@ If an older baseline still points to root `features/{功能名}/`, treat that as
 - [ ] 涉及调用上游 API 的，是否已向用户索要接口文档并确认对接方案？（不可猜测 API 契约，包括 URL、认证、请求/响应结构、错误码）
 - [ ] 涉及的每个能力点（外部集成、业务逻辑、数据访问、工具方法），是否已在项目内完成复用搜索？**若已有封装却被绕过直接重写，方案不合格。**
 - [ ] `references/affected-module-exploration.md` 的探索产出检查是否全部通过？（现状流程图、字段/方法表格、集成点列表、复用/扩展/新增决策）**若不通过，必须先补充代码探索，不得继续写文档。**
-- [ ] 若 `.planning/code-index/` 存在，复用/影响范围/调用链/读写资源判断是否已查询 code-index 并回读源码 evidence？若未使用，是否说明缺失或过期原因？
+- [ ] 若 `.devflow/planning/code-index/` 存在，复用/影响范围/调用链/读写资源判断是否已查询 code-index 并回读源码 evidence？若未使用，是否说明缺失或过期原因？
 - [ ] 是否已找到项目内最佳实践标杆，并确认新功能的分层结构、命名、错误处理、参数封装模式与标杆一致？（若偏离，理由是否已写明？）
 - [ ] 新功能中具有独立复用价值的部分，是否已识别并抽象为 `pkg/` 级能力模块？接口定义、参数/结果结构体是否清晰？
 - [ ] 方案影响的现有功能是否已描述其**现状流程/字段/逻辑**？（先描述现状，再分析影响）
@@ -262,7 +262,7 @@ If an older baseline still points to root `features/{功能名}/`, treat that as
 
 - [ ] 方案包含：功能要点、影响范围、库表设计（DDL+ER）、流程设计、风险点
 - [ ] 不含前端组件、前端路由（那属于前端技术方案）
-- [ ] 若存在 `.planning/rules/` 或 `.context/spec/`，适用规范+经验教训+工具链+测试策略已列出
+- [ ] 若存在 `.devflow/planning/rules/` 或 `.devflow/context/spec/`，适用规范+经验教训+工具链+测试策略已列出
 - [ ] 审查结论已写入方案末尾
 
 **审查结论不通过时不得报告 "Step 3c 完成"。**

package/plugins/devflow-design/skills/workflow-backend-tech-spec/assets/backend-spec-template.md

@@ -38,9 +38,9 @@
 
 | 来源 | 结论 | 对本方案的影响 |
 |------|------|----------------|
-| `.planning/milestones/...` | {{结论}} | {{影响}} |
-| `.planning/requirements/...` | {{结论}} | {{影响}} |
-| `.planning/lessons/...` | {{结论}} | {{影响}} |
+| `.devflow/planning/milestones/...` | {{结论}} | {{影响}} |
+| `.devflow/planning/requirements/...` | {{结论}} | {{影响}} |
+| `.devflow/planning/lessons/...` | {{结论}} | {{影响}} |
 
 ## 四、现有功能说明
 
@@ -163,13 +163,13 @@ erDiagram
 
 | 规则来源 | 是否存在 | 影响说明 |
 |----------|----------|----------|
-| `.planning/rules/INDEX.md` | {{是/否}} | {{说明}} |
-| `.planning/execution-contract.md` | {{是/否}} | {{说明}} |
-| `.planning/toolchain.md` | {{是/否}} | {{说明}} |
-| `.planning/lessons/README.md` | {{是/否}} | {{说明}} |
-| `.context/spec/backend/index.md` | {{是/否}} | {{说明}} |
-| `.context/workflow/` | {{是/否}} | {{说明}} |
-| `.context/lessons/README.md` | {{是/否}} | {{说明}} |
+| `.devflow/planning/rules/INDEX.md` | {{是/否}} | {{说明}} |
+| `.devflow/planning/execution-contract.md` | {{是/否}} | {{说明}} |
+| `.devflow/planning/toolchain.md` | {{是/否}} | {{说明}} |
+| `.devflow/planning/lessons/README.md` | {{是/否}} | {{说明}} |
+| `.devflow/context/spec/backend/index.md` | {{是/否}} | {{说明}} |
+| `.devflow/context/workflow/` | {{是/否}} | {{说明}} |
+| `.devflow/context/lessons/README.md` | {{是/否}} | {{说明}} |
 | `AGENTS.md` / `CLAUDE.md` | {{是/否}} | {{说明}} |
 
 ### 9.2 适用规范

package/plugins/devflow-design/skills/workflow-backend-tech-spec/references/affected-module-exploration.md

@@ -14,7 +14,7 @@
 
 ### 步骤1：定位关键文件
 
-优先使用 `.planning/code-index/` 定位候选 symbol、entrypoint、calls、reads/writes 和 tested_by 关系；然后回读 `evidence_path:evidence_line` 附近源码。code-index 不存在或过期时，再按下表的目录约定和 `rg` 兜底。
+优先使用 `.devflow/planning/code-index/` 定位候选 symbol、entrypoint、calls、reads/writes 和 tested_by 关系；然后回读 `evidence_path:evidence_line` 附近源码。code-index 不存在或过期时，再按下表的目录约定和 `rg` 兜底。
 
 | 层级 | 定位方式 | 最少读取 |
 |------|----------|----------|
@@ -54,6 +54,6 @@
 - [ ] 是否有现有字段/方法/枚举的结构化表格（不是从 PRD 复制）？
 - [ ] 是否明确了每个模块是"复用"、"扩展"还是"新增"？
 - [ ] 是否实际读取了代码文件（不是仅靠文件名推断）？
-- [ ] 若 `.planning/code-index/` 存在，是否记录了用于定位的 symbol/relation evidence？
+- [ ] 若 `.devflow/planning/code-index/` 存在，是否记录了用于定位的 symbol/relation evidence？
 
 **此检查不通过，不得进入 Phase 3（生成文档）。**

package/plugins/devflow-design/skills/workflow-backend-tech-spec/references/code-explore-guide.md

@@ -4,7 +4,7 @@ Use this guide to explore the target backend without assuming outbound-call's Go
 
 ## Exploration Order
 
-1. Read `.planning/navigation/INDEX.md` → filter backend/service-type codebases → load their `{name}.md` navigation files to identify root, framework, entry points, layers, persistence, jobs, integrations, config, and commands.
+1. Read `.devflow/planning/navigation/INDEX.md` → filter backend/service-type codebases → load their `{name}.md` navigation files to identify root, framework, entry points, layers, persistence, jobs, integrations, config, and commands.
 2. Read the project rule package via `references/project-rule-contract.md`.
 3. Start from baseline `FP-*`, `BR-*`, `BC-*`, and confirmed `CR-*` decisions.
 4. Search only the relevant modules first; expand outward only when the call chain or data flow requires it.

package/plugins/devflow-design/skills/workflow-backend-tech-spec/references/project-rule-contract.md

@@ -6,30 +6,30 @@ Use this contract when generating backend technical plans. A project rule packag
 
 Look for rule sources in the target project, in this order:
 
-1. `.planning/rules/INDEX.md`
-2. `.planning/execution-contract.md`
-3. `.planning/toolchain.md`
-4. `.planning/lessons/README.md`
-5. `.planning/milestones/`
-6. `.planning/requirements/`
-7. `.context/spec/index.md`
-8. matching `.context/spec/stacks/{stack_key}.md`
-9. matching `.context/spec/backend/{codebase}.md`
-10. `.context/spec/backend/index.md`
-11. `.context/spec/backend/`
-12. `.planning/code-index/` when source-level relation facts are needed
-13. `.context/workflow/tdd.md`
-14. `.context/workflow/verification.md`
-15. `.context/workflow/checklist.md`
-16. `.context/lessons/README.md`
+1. `.devflow/planning/rules/INDEX.md`
+2. `.devflow/planning/execution-contract.md`
+3. `.devflow/planning/toolchain.md`
+4. `.devflow/planning/lessons/README.md`
+5. `.devflow/planning/milestones/`
+6. `.devflow/planning/requirements/`
+7. `.devflow/context/spec/index.md`
+8. matching `.devflow/context/spec/stacks/{stack_key}.md`
+9. matching `.devflow/context/spec/backend/{codebase}.md`
+10. `.devflow/context/spec/backend/index.md`
+11. `.devflow/context/spec/backend/`
+12. `.devflow/planning/code-index/` when source-level relation facts are needed
+13. `.devflow/context/workflow/tdd.md`
+14. `.devflow/context/workflow/verification.md`
+15. `.devflow/context/workflow/checklist.md`
+16. `.devflow/context/lessons/README.md`
 17. root `AGENTS.md`, `CLAUDE.md`, or equivalent project instruction files
 
 If none exist, explicitly write `未发现项目规则包` and continue with code exploration and conservative assumptions.
 
 History rule:
 
-- Use `.planning/milestones/`, `.planning/requirements/`, `.planning/lessons/`, and phase `CONTEXT.md` files as the primary history model.
-- Treat `.context/lessons/` and `features/` as compatible legacy/project-rule evidence only when present in the target project.
+- Use `.devflow/planning/milestones/`, `.devflow/planning/requirements/`, `.devflow/planning/lessons/`, and phase `CONTEXT.md` files as the primary history model.
+- Treat `.devflow/context/lessons/` and `features/` as compatible legacy/project-rule evidence only when present in the target project.
 - Do not require outbound-call style history files.
 
 ## What To Extract
@@ -37,8 +37,8 @@ History rule:
 Extract only backend-relevant rules:
 
 - Technology stack and framework.
-- Matching stack spec and codebase spec from `.context/spec/index.md` when available.
-- Code-index symbols/relations for affected entrypoints, callers, callees, data/resource reads and writes, tests, and external integrations when `.planning/code-index/` exists.
+- Matching stack spec and codebase spec from `.devflow/context/spec/index.md` when available.
+- Code-index symbols/relations for affected entrypoints, callers, callees, data/resource reads and writes, tests, and external integrations when `.devflow/planning/code-index/` exists.
 - Layer model and dependency direction.
 - Naming, function signature, validation, error handling, logging, transaction, pagination, permission, and data access rules.
 - Required code generation, mock generation, dependency injection, migration, or build commands.

package/plugins/devflow-design/skills/workflow-design-rule-pack/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: workflow-design-rule-pack
-description: Use when workflow-ui-spec or workflow-frontend-tech-spec needs a reusable UI/UX design rule package, ui-ux-pro-max recommendations, or project installation of .context/spec/design across repositories.
+description: Use when workflow-ui-spec or workflow-frontend-tech-spec needs a reusable UI/UX design rule package, ui-ux-pro-max recommendations, or project installation of .devflow/context/spec/design across repositories.
 ---
 
 # Workflow Design Rule Pack
@@ -11,12 +11,12 @@ This skill provides the reusable source for the project design rule package cons
 
 Use this skill when:
 
-- A project lacks `.context/spec/design/index.md`.
+- A project lacks `.devflow/context/spec/design/index.md`.
 - UI workflow steps need the shared UI/UX recommendation pack.
 - `ui-ux-pro-max` should be available in a project without copying it by hand.
 - The same design rules need to be reused across repositories.
 
-`workflow-project-context` is the default lifecycle owner for frontend projects: it invokes this installer after the code index is ready, records the result in the initialization manifest, and owns `.context/spec/design/index.md`. Call this skill directly only to repair or deliberately refresh the shared recommendation assets.
+`workflow-project-context` is the default lifecycle owner for frontend projects: it invokes this installer after the code index is ready, records the result in the initialization manifest, and owns `.devflow/context/spec/design/index.md`. Call this skill directly only to repair or deliberately refresh the shared recommendation assets.
 
 Do not use this skill as a replacement for `workflow-ui-spec` or `workflow-frontend-tech-spec`. It only installs and documents shared references; workflow skills still decide how to apply them.
 
@@ -30,7 +30,7 @@ devflow_design_rule(args=[])
 
 Default behavior:
 
-- Copies `assets/design/` into `.context/spec/design/`.
+- Copies `assets/design/` into `.devflow/context/spec/design/`.
 - Creates missing directories.
 - Does not overwrite existing project files.
 - Keeps project-specific confirmed tokens in the target project.
@@ -64,7 +64,7 @@ for path in \
   recommendations/accessibility.md \
   recommendations/component-library.md \
   tools/ui-ux-pro-max/SKILL.md; do
-  test -s ".context/spec/design/$path"
+  test -s ".devflow/context/spec/design/$path"
 done
 ```
 
@@ -75,7 +75,7 @@ Pass only when every expected file exists and is non-empty. A missing file, a ze
 ## Source of Truth
 
 - Skill source: `skill://workflow-design-rule-pack/assets/design/`
-- Project installed copy: `.context/spec/design/`
+- Project installed copy: `.devflow/context/spec/design/`
 
 Workflow skills must read the installed project copy. The project copy is the place where local overrides and confirmed project tokens live.
 
@@ -85,7 +85,7 @@ Design conclusion priority remains:
 
 1. User decisions, design artifacts, confirmed requirement baseline
 2. Existing code, component library, current project tokens
-3. `.context/spec/design/tokens/project-tokens.md`
-4. `.context/spec/design/recommendations/` and `ui-ux-pro-max` query results
+3. `.devflow/context/spec/design/tokens/project-tokens.md`
+4. `.devflow/context/spec/design/recommendations/` and `ui-ux-pro-max` query results
 
 Recommendation sources are never authoritative project facts unless the user or project rules explicitly confirm them.

package/plugins/devflow-design/skills/workflow-design-rule-pack/assets/design/index.md

@@ -32,9 +32,9 @@
 工具位置：
 
 ```bash
-python3 .context/spec/design/tools/ui-ux-pro-max/scripts/search.py "<query>" --design-system -p "<Project Name>"
-python3 .context/spec/design/tools/ui-ux-pro-max/scripts/search.py "<query>" --domain ux
-python3 .context/spec/design/tools/ui-ux-pro-max/scripts/search.py "<query>" --stack react
+python3 .devflow/context/spec/design/tools/ui-ux-pro-max/scripts/search.py "<query>" --design-system -p "<Project Name>"
+python3 .devflow/context/spec/design/tools/ui-ux-pro-max/scripts/search.py "<query>" --domain ux
+python3 .devflow/context/spec/design/tools/ui-ux-pro-max/scripts/search.py "<query>" --stack react
 ```
 
 常用域：

package/plugins/devflow-design/skills/workflow-design-rule-pack/assets/design/recommendations/accessibility.md

@@ -26,6 +26,6 @@
 ## 查询辅助
 
 ```bash
-python3 .context/spec/design/tools/ui-ux-pro-max/scripts/search.py "accessibility aria focus keyboard form labels color contrast" --domain ux
-python3 .context/spec/design/tools/ui-ux-pro-max/scripts/search.py "aria focus keyboard semantic form" --domain web
+python3 .devflow/context/spec/design/tools/ui-ux-pro-max/scripts/search.py "accessibility aria focus keyboard form labels color contrast" --domain ux
+python3 .devflow/context/spec/design/tools/ui-ux-pro-max/scripts/search.py "aria focus keyboard semantic form" --domain web
 ```

package/plugins/devflow-design/skills/workflow-design-rule-pack/assets/design/recommendations/component-library.md

@@ -26,6 +26,6 @@
 需要补充组件模式时，可查：
 
 ```bash
-python3 .context/spec/design/tools/ui-ux-pro-max/scripts/search.py "form button modal table accessibility" --domain ux
-python3 .context/spec/design/tools/ui-ux-pro-max/scripts/search.py "button form table" --stack shadcn
+python3 .devflow/context/spec/design/tools/ui-ux-pro-max/scripts/search.py "form button modal table accessibility" --domain ux
+python3 .devflow/context/spec/design/tools/ui-ux-pro-max/scripts/search.py "button form table" --stack shadcn
 ```

package/plugins/devflow-design/skills/workflow-design-rule-pack/assets/design/recommendations/design-systems.md

@@ -13,7 +13,7 @@
 优先用动态工具生成完整建议：
 
 ```bash
-python3 .context/spec/design/tools/ui-ux-pro-max/scripts/search.py "<product type> <industry> <style keywords>" --design-system -p "<Feature or Project Name>" --format markdown
+python3 .devflow/context/spec/design/tools/ui-ux-pro-max/scripts/search.py "<product type> <industry> <style keywords>" --design-system -p "<Feature or Project Name>" --format markdown
 ```
 
 输出只能进入 UI-SPEC 的“推荐方案（待拍板）”或“待确认事项”，不能直接进入“设计稿事实”。

package/plugins/devflow-design/skills/workflow-design-rule-pack/assets/design/recommendations/responsive-grid.md

@@ -24,6 +24,6 @@
 ## 查询辅助
 
 ```bash
-python3 .context/spec/design/tools/ui-ux-pro-max/scripts/search.py "responsive layout mobile horizontal scroll touch target" --domain ux
-python3 .context/spec/design/tools/ui-ux-pro-max/scripts/search.py "responsive layout" --stack html-tailwind
+python3 .devflow/context/spec/design/tools/ui-ux-pro-max/scripts/search.py "responsive layout mobile horizontal scroll touch target" --domain ux
+python3 .devflow/context/spec/design/tools/ui-ux-pro-max/scripts/search.py "responsive layout" --stack html-tailwind
 ```

package/plugins/devflow-design/skills/workflow-design-rule-pack/assets/design/recommendations/stack-guidelines.md

@@ -1,17 +1,17 @@
 # Stack Guidelines Recommendations
 
-本文件提供技术栈实现参考。项目 `.context/spec/stacks/`、前端代码约定和 workflow 内置 stack slots 优先。
+本文件提供技术栈实现参考。项目 `.devflow/context/spec/stacks/`、前端代码约定和 workflow 内置 stack slots 优先。
 
 ## 使用方式
 
 按项目实际栈调用动态工具补充：
 
 ```bash
-python3 .context/spec/design/tools/ui-ux-pro-max/scripts/search.py "layout form table accessibility performance" --stack react
-python3 .context/spec/design/tools/ui-ux-pro-max/scripts/search.py "image routing cache hydration" --stack nextjs
-python3 .context/spec/design/tools/ui-ux-pro-max/scripts/search.py "composition api form table state" --stack vue
-python3 .context/spec/design/tools/ui-ux-pro-max/scripts/search.py "responsive utility accessibility" --stack html-tailwind
-python3 .context/spec/design/tools/ui-ux-pro-max/scripts/search.py "components theme form" --stack shadcn
+python3 .devflow/context/spec/design/tools/ui-ux-pro-max/scripts/search.py "layout form table accessibility performance" --stack react
+python3 .devflow/context/spec/design/tools/ui-ux-pro-max/scripts/search.py "image routing cache hydration" --stack nextjs
+python3 .devflow/context/spec/design/tools/ui-ux-pro-max/scripts/search.py "composition api form table state" --stack vue
+python3 .devflow/context/spec/design/tools/ui-ux-pro-max/scripts/search.py "responsive utility accessibility" --stack html-tailwind
+python3 .devflow/context/spec/design/tools/ui-ux-pro-max/scripts/search.py "components theme form" --stack shadcn
 ```
 
 ## 前端技术方案使用边界

package/plugins/devflow-design/skills/workflow-design-rule-pack/assets/design/recommendations/ux-patterns.md

@@ -35,6 +35,6 @@
 ## 查询辅助
 
 ```bash
-python3 .context/spec/design/tools/ui-ux-pro-max/scripts/search.py "loading error feedback duplicate submit animation" --domain ux
-python3 .context/spec/design/tools/ui-ux-pro-max/scripts/search.py "form validation feedback" --domain web
+python3 .devflow/context/spec/design/tools/ui-ux-pro-max/scripts/search.py "loading error feedback duplicate submit animation" --domain ux
+python3 .devflow/context/spec/design/tools/ui-ux-pro-max/scripts/search.py "form validation feedback" --domain web
 ```

package/plugins/devflow-design/skills/workflow-design-rule-pack/assets/design/tokens/project-tokens.md

@@ -4,7 +4,7 @@
 
 ## 状态
 
-当前项目尚未沉淀全局设计 token。workflow-ui-spec 生成某个功能的 token 时，应先写入对应功能的 `.planning/features/{功能名}/UI-SPEC.md`。
+当前项目尚未沉淀全局设计 token。workflow-ui-spec 生成某个功能的 token 时，应先写入对应功能的 `.devflow/planning/features/{功能名}/UI-SPEC.md`。
 
 ## 允许写入本文件的条件
 

package/plugins/devflow-design/skills/workflow-design-rule-pack/assets/design/tools/ui-ux-pro-max/SKILL.md

@@ -135,7 +135,7 @@ Extract key information from user request:
 **Always start with `--design-system`** to get comprehensive recommendations with reasoning:
 
 ```bash
-python3 .context/spec/design/tools/ui-ux-pro-max/scripts/search.py "<product_type> <industry> <keywords>" --design-system [-p "Project Name"]
+python3 .devflow/context/spec/design/tools/ui-ux-pro-max/scripts/search.py "<product_type> <industry> <keywords>" --design-system [-p "Project Name"]
 ```
 
 This command:
@@ -146,7 +146,7 @@ This command:
 
 **Example:**
 ```bash
-python3 .context/spec/design/tools/ui-ux-pro-max/scripts/search.py "beauty spa wellness service" --design-system -p "Serenity Spa"
+python3 .devflow/context/spec/design/tools/ui-ux-pro-max/scripts/search.py "beauty spa wellness service" --design-system -p "Serenity Spa"
 ```
 
 ### Step 2b: Persist Design System (Master + Overrides Pattern)
@@ -154,7 +154,7 @@ python3 .context/spec/design/tools/ui-ux-pro-max/scripts/search.py "beauty spa w
 To save the design system for hierarchical retrieval across sessions, add `--persist`:
 
 ```bash
-python3 .context/spec/design/tools/ui-ux-pro-max/scripts/search.py "<query>" --design-system --persist -p "Project Name"
+python3 .devflow/context/spec/design/tools/ui-ux-pro-max/scripts/search.py "<query>" --design-system --persist -p "Project Name"
 ```
 
 This creates:
@@ -163,7 +163,7 @@ This creates:
 
 **With page-specific override:**
 ```bash
-python3 .context/spec/design/tools/ui-ux-pro-max/scripts/search.py "<query>" --design-system --persist -p "Project Name" --page "dashboard"
+python3 .devflow/context/spec/design/tools/ui-ux-pro-max/scripts/search.py "<query>" --design-system --persist -p "Project Name" --page "dashboard"
 ```
 
 This also creates:
@@ -179,7 +179,7 @@ This also creates:
 After getting the design system, use domain searches to get additional details:
 
 ```bash
-python3 .context/spec/design/tools/ui-ux-pro-max/scripts/search.py "<keyword>" --domain <domain> [-n <max_results>]
+python3 .devflow/context/spec/design/tools/ui-ux-pro-max/scripts/search.py "<keyword>" --domain <domain> [-n <max_results>]
 ```
 
 **When to use detailed searches:**
@@ -197,7 +197,7 @@ python3 .context/spec/design/tools/ui-ux-pro-max/scripts/search.py "<keyword>" -
 Get implementation-specific best practices. If user doesn't specify a stack, **default to `html-tailwind`**.
 
 ```bash
-python3 .context/spec/design/tools/ui-ux-pro-max/scripts/search.py "<keyword>" --stack html-tailwind
+python3 .devflow/context/spec/design/tools/ui-ux-pro-max/scripts/search.py "<keyword>" --stack html-tailwind
 ```
 
 Available stacks: `html-tailwind`, `react`, `nextjs`, `vue`, `svelte`, `swiftui`, `react-native`, `flutter`, `shadcn`, `jetpack-compose`
@@ -251,7 +251,7 @@ Available stacks: `html-tailwind`, `react`, `nextjs`, `vue`, `svelte`, `swiftui`
 ### Step 2: Generate Design System (REQUIRED)
 
 ```bash
-python3 .context/spec/design/tools/ui-ux-pro-max/scripts/search.py "beauty spa wellness service elegant" --design-system -p "Serenity Spa"
+python3 .devflow/context/spec/design/tools/ui-ux-pro-max/scripts/search.py "beauty spa wellness service elegant" --design-system -p "Serenity Spa"
 ```
 
 **Output:** Complete design system with pattern, style, colors, typography, effects, and anti-patterns.
@@ -260,16 +260,16 @@ python3 .context/spec/design/tools/ui-ux-pro-max/scripts/search.py "beauty spa w
 
 ```bash
 # Get UX guidelines for animation and accessibility
-python3 .context/spec/design/tools/ui-ux-pro-max/scripts/search.py "animation accessibility" --domain ux
+python3 .devflow/context/spec/design/tools/ui-ux-pro-max/scripts/search.py "animation accessibility" --domain ux
 
 # Get alternative typography options if needed
-python3 .context/spec/design/tools/ui-ux-pro-max/scripts/search.py "elegant luxury serif" --domain typography
+python3 .devflow/context/spec/design/tools/ui-ux-pro-max/scripts/search.py "elegant luxury serif" --domain typography
 ```
 
 ### Step 4: Stack Guidelines
 
 ```bash
-python3 .context/spec/design/tools/ui-ux-pro-max/scripts/search.py "layout responsive form" --stack html-tailwind
+python3 .devflow/context/spec/design/tools/ui-ux-pro-max/scripts/search.py "layout responsive form" --stack html-tailwind
 ```
 
 **Then:** Synthesize design system + detailed searches and implement the design.
@@ -282,10 +282,10 @@ The `--design-system` flag supports two output formats:
 
 ```bash
 # ASCII box (default) - best for terminal display
-python3 .context/spec/design/tools/ui-ux-pro-max/scripts/search.py "fintech crypto" --design-system
+python3 .devflow/context/spec/design/tools/ui-ux-pro-max/scripts/search.py "fintech crypto" --design-system
 
 # Markdown - best for documentation
-python3 .context/spec/design/tools/ui-ux-pro-max/scripts/search.py "fintech crypto" --design-system -f markdown
+python3 .devflow/context/spec/design/tools/ui-ux-pro-max/scripts/search.py "fintech crypto" --design-system -f markdown
 ```
 
 ---

package/plugins/devflow-design/skills/workflow-design-rule-pack/scripts/install.py

@@ -34,7 +34,7 @@ def copy_tree(src: Path, dst: Path, overwrite: bool, include_index: bool) -> tup
 
 
 def main() -> int:
-    parser = argparse.ArgumentParser(description="Install .context/spec/design rule pack")
+    parser = argparse.ArgumentParser(description="Install .devflow/context/spec/design rule pack")
     parser.add_argument("--target", default=".", help="Target repository root, default current directory")
     parser.add_argument("--overwrite", action="store_true", help="Overwrite existing target files")
     parser.add_argument(
@@ -47,7 +47,7 @@ def main() -> int:
     skill_root = Path(__file__).resolve().parents[1]
     source = skill_root / "assets" / "design"
     target_root = Path(args.target).resolve()
-    target = target_root / ".context" / "spec" / "design"
+    target = target_root / ".devflow/context" / "spec" / "design"
 
     if not source.exists():
         raise SystemExit(f"Source design rule pack not found: {source}")