@bovinphang/frontend-craft 2.6.0 → 2.8.0

package/skills/fec-accessibility-check/SKILL.md

@@ -1,39 +1,39 @@
 ---
 name: fec-accessibility-check
-description: Use when reviewing or improving frontend accessibility, semantic structure, keyboard support, focus management, ARIA labels, screen reader behavior, WCAG 2.2 issues, touch accessibility, or assistive-technology regressions; Chinese triggers include 无障碍, accessibility, a11y, WCAG, 屏幕阅读器.
+description: Use when reviewing or improving frontend accessibility, semantic structure, keyboard support, focus management, ARIA labels, screen reader behavior, WCAG 2.2 issues, touch accessibility, or assistive-technology regressions; Chinese triggers include accessibility, accessibility, a11y, WCAG, screen reader.
 ---
 
-# 无障碍实现规范（WCAG 2.2 AA）
+# Accessibility Implementation Specification (WCAG 2.2 AA)
 
 ## Purpose
 
-确保前端 UI 对残障用户可访问，满足 WCAG 2.2 AA 的核心要求，并能被键盘、屏幕阅读器、触控和缩放用户稳定使用。
+Ensure the front-end UI is accessible to users with disabilities, meets the core requirements of WCAG 2.2 AA, and is stable for keyboard, screen reader, touch, and zoom users.
 
 ## Procedure
 
-1. 检查语义结构：landmark、标题层级、表单 label、按钮/链接可访问名称、表格语义和图片 alt。
-2. 检查键盘路径：Tab 顺序、Enter/Space/Esc 行为、焦点可见、关闭后焦点恢复。
-3. 检查复杂组件：对话框、菜单、标签页、树、抽屉、表格和自定义控件的 ARIA 状态。
-4. 检查动态状态：loading、empty、error、toast 和异步更新需要被屏幕阅读器感知。
-5. 检查视觉与触控可读性：文本/背景对比、focus ring、缩放到 200%、减少动效偏好、触摸目标尺寸和移动端虚拟键盘行为。
-6. 用真实键盘路径复核关键流程，必要时补充屏幕阅读器或浏览器无障碍树观察；屏幕阅读器流程见 [references/screen-reader-testing.md](references/screen-reader-testing.md)。
-7. 复核 WCAG 2.2 新增高频风险：可见焦点不被遮挡、拖拽操作有替代路径、目标尺寸过小、帮助入口和认证流程不依赖记忆负担。
-8. 输出分级报告；报告格式见 [references/report-template.md](references/report-template.md)。
+1. Check the semantic structure: landmark, title level, form label, button/link accessible name, table semantics and image alt.
+2. Check the keyboard path: Tab order, Enter/Space/Esc behavior, focus visible, focus restored after closing.
+3. Check the ARIA status of complex components: dialog boxes, menus, tabs, trees, drawers, tables, and custom controls.
+4. Check dynamic status: loading, empty, error, toast and asynchronous updates need to be perceived by screen readers.
+5. Check visual and touch readability: text/background contrast, focus ring, zoom to 200%, reduced animation preference, touch target size, and mobile virtual keyboard behavior.
+6. Use the real keyboard path to review the key process, and if necessary, add a screen reader or browser accessibility tree observation; see [references/screen-reader-testing.md](references/screen-reader-testing.md) for the screen reader process.
+7. Review the new high-frequency risks in WCAG 2.2: the visible focus is not blocked, the drag operation has alternative paths, the target size is too small, and the help entrance and authentication process do not rely on memory burden.
+8. Output the classification report; see [references/report-template.md](references/report-template.md) for the report format.
 
-## 详细参考
+## Detailed reference
 
-撰写无障碍审查报告时，加载 [references/report-template.md](references/report-template.md)。需要验证屏幕阅读器公告、焦点读法和动态区域时，加载 [references/screen-reader-testing.md](references/screen-reader-testing.md)。
+When writing an accessibility review report, load [references/report-template.md](references/report-template.md). Load [references/screen-reader-testing.md](references/screen-reader-testing.md) when you need to verify screen reader announcements, focus pronunciations, and dynamic areas.
 
 ## Constraints
 
-- 优先使用语义化 HTML，而不是 ARIA。
-- `role` 不应覆盖原生语义。
-- 交互元素必须可键盘访问。
-- 表单错误必须与字段关联。
-- 颜色对比度风险需要指出具体文本/背景组合。
-- 不用 ARIA 弥补可以用原生 HTML 解决的问题。
-- 不把浏览器自动可访问树当作最终结论；关键路径需要用键盘和至少一种辅助技术或等价检查验证。
+- Prefer semantic HTML over ARIA.
+- `role` should not override native semantics.
+- Interactive elements must be keyboard accessible.
+- Form errors must be associated with fields.
+- Color contrast risks need to be pointed out for specific text/background combinations.
+- Don't use ARIA to make up for problems that can be solved with native HTML.
+- Do not treat automatic browser accessibility trees as final; critical paths need to be verified with the keyboard and at least one assistive technology or equivalent check.
 
 ## Expected Output
 
-交互元素可键盘访问，语义和 ARIA 使用正确，焦点管理稳定；无障碍检查报告保存为 `reports/accessibility-review-YYYY-MM-DD-HHmmss.md`。
+Interactive elements are keyboard accessible, semantics and ARIA are used correctly, and focus management is stable; accessibility check reports are saved as `reports/accessibility-review-YYYY-MM-DD-HHmmss.md`.

package/skills/fec-accessibility-check/references/report-template.md

@@ -1,23 +1,23 @@
-# 无障碍检查报告模板
+# Accessibility inspection report template
 
 ```markdown
-# 无障碍检查报告
+#Accessibility Inspection Report
 
-> 生成时间: YYYY-MM-DD HH:mm
-> 评审工具: frontend-craft
-> 标准: WCAG 2.2 AA
+> Generation time: YYYY-MM-DD HH:mm
+> Review tool: frontend-craft
+> Standard: WCAG 2.2 AA
 
-## 必须修复 (N项)
-- **[文件:行号]** 问题描述 -> 建议修改
+## Must be fixed (N items)
+- **[File:line number]** Problem description -> Suggested modifications
 
-## 建议改进 (N项)
-- **[文件:行号]** 问题描述 -> 建议修改
+## Suggested improvements (N items)
+- **[File:line number]** Problem description -> Suggested modifications
 
-## 已通过项
+## Passed items
 - ...
 
-## 建议的代码修改
+## Suggested code modifications
 - ...
 ```
 
-检查完成后，将报告保存到 `reports/accessibility-review-YYYY-MM-DD-HHmmss.md`，并告知用户报告路径。
+After the check is completed, save the report to `reports/accessibility-review-YYYY-MM-DD-HHmmss.md` and inform the user of the report path.

package/skills/fec-accessibility-check/references/screen-reader-testing.md

@@ -1,33 +1,33 @@
-# 屏幕阅读器测试
+# Screen reader testing
 
-## 何时测试
+## When to test
 
-以下场景需要使用屏幕阅读器或浏览器无障碍树进行检查：
+The following scenarios require checking using a screen reader or browser accessibility tree:
 
-- 对话框、抽屉、菜单、标签页、组合框、树形控件和自定义控件。
-- 异步状态更新、toast 通知、校验错误和 loading 区域。
-- 表格、虚拟列表、图表、dashboard 和数据密集型控件。
-- 触摸探索、虚拟键盘或焦点顺序可能与桌面不同的移动端流程。
+- Dialog boxes, drawers, menus, tabs, combo boxes, tree controls and custom controls.
+- Asynchronous status updates, toast notifications, validation errors and loading areas.
+- Tables, virtual lists, charts, dashboards and data-intensive controls.
+- Mobile processes where touch exploration, virtual keyboard, or focus order may differ from desktop.
 
-## 最小流程
+## Minimum process
 
-1. 先只用键盘操作：Tab、Shift+Tab、Enter、Space、Esc，以及适用场景下的方向键。
-2. 在浏览器开发者工具中检查可访问名称、角色、状态和元素关系。
-3. 条件允许时至少跑一轮辅助技术验证：NVDA/Firefox、JAWS/Chrome、VoiceOver/Safari 或 TalkBack/Chrome。
-4. 验证路由变化、校验错误、加载完成和破坏性确认是否有正确公告。
-5. 记录具体用户影响、期望读法、实际读法和建议修复方式。
+1. First use the keyboard only: Tab, Shift+Tab, Enter, Space, Esc, and the arrow keys in applicable scenarios.
+2. Check accessible names, roles, states, and element relationships in the browser developer tools.
+3. If possible, run at least one round of assistive technology verification: NVDA/Firefox, JAWS/Chrome, VoiceOver/Safari or TalkBack/Chrome.
+4. Verify that routing changes, check errors, load completion, and destructive acknowledgments are properly advertised.
+5. Document specific user impact, expected reading, actual reading, and recommended fixes.
 
-## 动态内容
+## Dynamic content
 
-- 非阻塞状态更新使用 `aria-live="polite"`。
-- 紧急错误可谨慎使用 `role="alert"`，不要滥用。
-- 只有当用户任务上下文发生变化时才移动焦点，例如打开弹窗或提交后跳转。
-- 关闭浮层后，将焦点恢复到触发控件。
+- Use `aria-live="polite"` for non-blocking state updates.
+- Use `role="alert"` with caution for emergency errors and do not abuse it.
+- Only move focus when the user task context changes, such as opening a pop-up window or jumping after submission.
+- After closing the overlay, return focus to the trigger control.
 
-## 常见问题
+## FAQ
 
-- 纯图标按钮没有可访问名称。
-- 对话框内容先于标题被朗读，或缺少模态边界。
-- 表单错误只在视觉上展示，没有用 `aria-describedby` 与字段关联。
-- Toast 消失太快，屏幕阅读器用户来不及理解。
-- 虚拟列表行丢失行位置、表格语义或键盘连续性。
+- Icon-only buttons don't have accessible names.
+- The dialog content is read before the title, or the modal boundary is missing.
+- Form errors are only displayed visually and are not associated with fields using `aria-describedby`.
+- Toast disappears too quickly for screen reader users to understand.
+- Virtual list rows lose row position, table semantics, or keyboard continuity.

package/skills/fec-alchemy/SKILL.md

@@ -3,72 +3,72 @@ name: fec-alchemy
 description: Use when absorbing ideas, capabilities, workflows, architecture, quality systems, ecosystem extensions, or engineering practices from any reference system into the current project through original, project-native redesign rather than copying.
 ---
 
-# 项目吸收与原创化融合
+# Integration of project absorption and originality
 
 ## Purpose
 
-将一个或多个参考系统中的优秀思想、能力和工程实践，转化为当前项目中原创、可维护、符合目标项目风格的改进。
+Convert excellent ideas, capabilities, and engineering practices from one or more reference systems into improvements in the current project that are original, maintainable, and consistent with the target project style.
 
-适用于吸收、借鉴、对标、迁移或融合另一个代码库、产品、框架、库、服务、CLI、插件、文档体系、AI/Agent 工具链、架构或工程工作流。普通 Bug 修复、单独 API 使用问题或直接文件格式转换不应使用本 Skill，除非用户明确要求项目级吸收或适配。
+Suitable for absorbing, borrowing, benchmarking, migrating or integrating another code base, product, framework, library, service, CLI, plug-in, documentation system, AI/Agent tool chain, architecture or engineering workflow. This Skill should not be used for general bug fixes, individual API usage issues, or direct file format conversions, unless the user explicitly requests project-level ingestion or adaptation.
 
 ## Procedure
 
-1. 明确目标和参考系统：
-   - 将当前仓库视为目标系统，它的架构、命名、测试、发布模型和维护边界是事实来源。
-   - 将外部仓库、上传压缩包、文档、示例、产品描述或运行体验视为参考系统，它们只提供证据和启发。
-   - 识别吸收范围：产品能力、架构模式、领域模型、接口协议、数据流、运行时行为、开发体验、质量体系、交付流程、文档知识或生态扩展。
-   - 信息较多时可使用 [assets/intake-template.md](assets/intake-template.md) 建立简要清单。
-2. 建立目标项目基线：
-   - 先读取目标项目 README、包元数据、目录结构、配置、现有入口、扩展点、测试命令和发布说明。
-   - 找出目标项目已有类似能力，判断应增强、合并、替换、拆分、文档化还是新增。
-3. 扫描参考项目：
-   - 优先查看 README、包元数据、源码布局、项目形态相关目录、关键模块、测试、示例和发布说明。
-   - 将观察记录为能力、意图、模式和取舍，不记录为要复制的文件清单。
-4. 提炼候选能力：
-   - 对每个候选项说明它解决的问题、用户价值、适配度、依赖、风险、可验证性和与目标项目现状的关系。
-   - 对许可证、来源不清楚或实现高度绑定参考项目的候选项，只提炼思想，不复用表达。
-5. 映射到目标架构：
-   - 使用目标项目原生命名、模块边界、依赖策略、编码约定和测试方式重新设计。
-   - 避免创建与现有模块竞争的并行系统；避免因为参考项目用了某依赖就盲目引入依赖。
-   - 非平凡变更可使用 [assets/absorption-plan-template.md](assets/absorption-plan-template.md)。
-6. 原创化实现或计划：
-   - 编写新代码或新文档，不复制参考项目中的非平凡代码、提示词、配置或文档表达。
-   - 吸收生态扩展、提示词、命令、插件、自动化、Agent 或规则时，统一职责边界并删除重复指令。
-   - 大型任务先交付垂直薄切片，并记录被拒绝或延期的候选项。
-7. 验证和汇报：
-   - 运行最相关的类型检查、Lint、测试、构建、文档校验或 Skill 校验。
-   - 如果无法验证，明确说明阻塞原因、风险范围和需要用户确认的信息。
-   - 必要时使用 [assets/review-checklist.md](assets/review-checklist.md) 做人工复核。
+1. Clarify goals and reference systems:
+- Treat the current repository as the target system and its architecture, naming, testing, release model and maintenance boundaries as the source of truth.
+- Treat external repositories, uploaded packages, documentation, examples, product descriptions or running experiences as reference systems that only provide evidence and inspiration.
+- Identify the scope of absorption: product capabilities, architectural patterns, domain models, interface protocols, data flow, runtime behavior, development experience, quality system, delivery process, documentation knowledge or ecological expansion.
+- When there is a lot of information, you can use [assets/intake-template.md](assets/intake-template.md) to create a brief list.
+2. Establish a target project baseline:
+- First read the target project README, package metadata, directory structure, configuration, existing entries, extension points, test commands and release notes.
+- Find out that the target project already has similar capabilities and determine whether they should be enhanced, merged, replaced, split, documented or added.
+3. Scan reference items:
+- Prioritize reading README, package metadata, source code layout, project form related directories, key modules, tests, examples and release notes.
+- Record observations as capabilities, intentions, patterns, and trade-offs, not as a checklist of documents to copy.
+4. Refining candidate capabilities:
+- For each candidate, describe the problem it solves, user value, suitability, dependencies, risks, verifiability and relationship to the current status of the target project.
+- For candidates whose licenses and sources are unclear or whose implementation is highly bound to reference projects, only refine ideas and do not reuse expressions.
+5. Map to target architecture:
+- Redesign using native naming, module boundaries, dependency strategies, coding conventions and testing methods of the target project.
+- Avoid creating parallel systems that compete with existing modules; avoid blindly introducing dependencies just because the reference project uses them.
+- Non-trivial changes can use [assets/absorption-plan-template.md](assets/absorption-plan-template.md).
+6. Original realization or plan:
+- Write new code or new documentation without copying non-trivial code, prompt words, configurations or documentation expressions from the reference project.
+- Unify the boundaries of responsibilities and remove duplicate instructions when absorbing ecological extensions, prompt words, commands, plug-ins, automations, agents or rules.
+- Large tasks are delivered in vertical thin slices first, and rejected or delayed candidates are recorded.
+7. Verification and reporting:
+- Run the most relevant type checks, lints, tests, builds, documentation checks or skill checks.
+- If it cannot be verified, clearly state the cause of the blockage, the scope of the risk and the information that requires user confirmation.
+- Use [assets/review-checklist.md](assets/review-checklist.md) for manual review when necessary.
 
 ## Constraints
 
-- 不把吸收任务变成机械化 diff 合并。
-- 不整体照搬参考项目的命名体系、文件结构或实现细节。
-- 不在许可证或用户意图不明确时逐字复用参考项目中的非平凡代码、文档、提示词或配置。
-- 不为了匹配参考项目而削弱安全、隐私、权限边界、测试、可维护性或目标项目产品方向。
-- 不声称原创化，除非输出能解释目标设计为何不同、为何适配目标项目、如何验证。
-- 不把长篇参考材料塞进主说明；大型任务读取 [references/methodology.md](references/methodology.md)，许可证和原创风险读取 [references/originality-and-licensing.md](references/originality-and-licensing.md)。
+- Don't turn absorb tasks into mechanized diff merging.
+- Does not copy the naming scheme, file structure, or implementation details of the reference project in its entirety.
+- Do not reuse verbatim non-trivial code, documentation, hints, or configurations from reference projects when the license or user intent is unclear.
+- Do not compromise security, privacy, permission boundaries, testing, maintainability, or target project product direction to match the reference project.
+- Do not claim originality unless the output can explain why the target design is different, why it is suitable for the target project, and how to verify it.
+- Don't cram long reference material into the main description; large assignments read [references/methodology.md](references/methodology.md), licenses and original risks read [references/originality-and-licensing.md](references/originality-and-licensing.md).
 
 ## Expected Output
 
-分析类任务输出：
+Analysis task output:
 
-- 吸收候选项
-- 推荐目标设计
-- 实现计划
-- 风险与许可证说明
-- 验证清单
+- Absorption candidates
+- Recommended target design
+- Realize the plan
+- Description of risks and licenses
+- Verification Checklist
 
-实现类任务输出：
+Implementation class task output:
 
-- 已完成变更
-- 原创化说明
-- 验证结果
-- 剩余工作
+- Changes completed
+- Instructions for originalization
+- Verification results
+- Remaining work
 
-仓库级任务中，如果宿主工具支持文件编辑，应创建或更新项目本地计划文档。
+In warehouse-level tasks, if the host tool supports file editing, the project's local plan document should be created or updated.
 
-## 详细参考
+## Detailed reference
 
-- [references/methodology.md](references/methodology.md) - 详细吸收方法论。
-- [references/originality-and-licensing.md](references/originality-and-licensing.md) - 原创性、许可证和来源风险约束。
+- [references/methodology.md](references/methodology.md) - Absorb methodology in detail.
+- [references/originality-and-licensing.md](references/originality-and-licensing.md) - Originality, license and provenance risk constraints.

package/skills/fec-alchemy/assets/absorption-plan-template.md

@@ -1,47 +1,47 @@
-# Alchemy 吸收计划
+#Alchemy Absorption Plan
 
-## 目标
+## Target
 
-描述需要交付的目标项目原生化改进。
+Describe the target project native improvements that need to be delivered.
 
-## 参考项目优势
+## Reference project advantages
 
-| 候选项 | 参考洞察 | 目标项目缺口 | 策略 | 优先级 |
+| Candidates | Reference Insights | Target Project Gaps | Strategy | Prioritization |
 |---|---|---|---|---|
-|  |  |  | 增强 / 新增 / 拆分 / 合并 / 替换 / 文档化 / 拒绝 |  |
+| | | | Enhance / Add / Split / Merge / Replace / Document / Reject | |
 
-## 目标设计
+## Target design
 
-- 目标架构落点：
-- 用户可见能力：
-- 公开 API / CLI / 配置 / UI 入口：
-- UI / API / 数据 / 运行时 / 工具链 / 文档影响：
-- 公开 API 或用户可见行为：
-- 内部数据流：
-- 命名和约定：
-- 依赖影响：
-- 向后兼容性：
+- Target architecture placement:
+- User visible capabilities:
+- Public API/CLI/Configuration/UI entrance:
+- UI/API/Data/Runtime/Toolchain/Documentation Impact:
+- Public API or user-visible behavior:
+- Internal data flow:
+- Naming and conventions:
+- Dependency impact:
+- Backward compatibility:
 
-## 实现步骤
+## Implementation steps
 
 1.
 2.
 3.
 
-## 验证
+## Verify
 
-- 类型检查：
+- Type checking:
 - Lint：
-- 单元测试：
-- 集成测试：
-- 构建：
-- 人工评审：
-
-## 风险
-
-- 许可证 / 来源：
-- 范围膨胀：
-- 架构重叠：
-- 性能：
-- 安全：
-- 维护：
+- Unit tests:
+- Integration testing:
+- Build:
+- Human review:
+
+## Risk
+
+- License/Source:
+- Range expansion:
+- Architecture overlap:
+- Performance:
+- Security:
+- Maintenance:

package/skills/fec-alchemy/assets/intake-template.md

@@ -1,55 +1,55 @@
-# Alchemy 信息收集模板
-
-## 目标项目
-
-- 路径 / URL：
-- 项目定位：
-- 项目类型：
-- 主要用户：
-- 技术栈：
-- 当前相关模块：
-- 已有类似能力：
-- 目标项目适配边界：
-- 验证命令：
-- 约束条件：
-
-## 参考项目
-
-- 路径 / URL：
-- 项目定位：
-- 项目类型：
-- 主要用户：
-- 技术栈：
-- 重点模块：
-- 特色能力：
-- 许可证 / 来源：
-- 风险：
-
-## 能力域清单
-
-- 产品能力：
-- 架构模式：
-- 领域模型：
-- 接口协议：
-- 数据流：
-- 运行时行为：
-- 开发体验：
-- 质量体系：
-- 交付流程：
-- 文档知识：
-- 生态扩展：
-
-## 项目形态探针
-
-- 前端项目（页面 / 组件 / 路由 / 状态 / 数据请求 / 表单 / 设计系统 / 可访问性 / 性能 / 构建）：
-- 后端项目（API / 服务边界 / 数据库 / 队列 / 缓存 / 认证授权 / 任务调度 / 可观测性 / 部署）：
-- 工具或 CLI 项目（命令模型 / 配置 / 插件机制 / 错误输出 / 安装分发 / 模板）：
-- AI/Agent 项目（skills / commands / hooks / rules / agents / MCP / prompt / workflow）：
-- 库项目（公开 API / 类型 / 兼容性 / 构建产物 / 示例 / 版本策略）：
-- 文档或知识库项目（信息架构 / 导航 / 示例 / 搜索 / 版本化 / 贡献流程 / 发布节奏）：
-
-## 不吸收范围
-
-- 明确拒绝：
-- 延后观察：
-- 只作为灵感不落地：
+#Alchemy information collection template
+
+## Target project
+
+- Path/URL:
+- Project positioning:
+- Project type:
+- Main users:
+- Technology stack:
+- Current relevant modules:
+- Already have similar capabilities:
+- Target project adaptation boundary:
+- Verification command:
+- Constraints:
+
+## Reference project
+
+- Path/URL:
+- Project positioning:
+- Project type:
+- Main users:
+- Technology stack:
+- Key modules:
+- Featured abilities:
+- License/Source:
+- Risks:
+
+## List of capability domains
+
+- Product capabilities:
+- Architecture pattern:
+- Domain model:
+- Interface protocol:
+- Data flow:
+- Runtime behavior:
+- Development experience:
+- Quality system:
+- Delivery process:
+- Document knowledge:
+- Ecological expansion:
+
+## Project shape probe
+
+- Front-end projects (Pages/Components/Routing/State/Data Requests/Forms/Design System/Accessibility/Performance/Build):
+- Back-end projects (API / service boundary / database / queue / cache / authentication and authorization / task scheduling / observability / deployment):
+- Tool or CLI project (command model / configuration / plug-in mechanism / error output / installation distribution / template):
+- AI/Agent project (skills/commands/hooks/rules/agents/MCP/prompt/workflow):
+- Library project (Public API/Types/Compatibility/Build Artifacts/Examples/Version Policy):
+- Documentation or knowledge base project (information architecture / navigation / examples / search / versioning / contribution process / release cadence):
+
+## No absorption range
+
+- Explicit rejection:
+- Delayed observation:
+- Only as inspiration but not implemented:

package/skills/fec-alchemy/assets/review-checklist.md

@@ -1,31 +1,31 @@
-# Alchemy 评审检查清单
+#Alchemy Review Checklist
 
-## 架构
+## Architecture
 
-- [ ] 变更属于选定的目标模块。
-- [ ] 没有重复实现已有能力、入口、抽象或用户工作流。
-- [ ] 职责清晰且不重叠。
-- [ ] 命名符合目标项目语义。
-- [ ] 目标架构落点清晰，未为了参考项目形态引入并行体系。
-- [ ] 配置、运行时流程、工具函数和文档承诺没有互相冲突。
+- [ ] Changes belong to the selected target module.
+- [ ] No duplication of existing capabilities, portals, abstractions, or user workflows.
+- [ ] Responsibilities are clear and non-overlapping.
+- [ ] Naming conforms to target project semantics.
+- [ ] The target architecture has a clear focus, and no parallel system is introduced for reference project form.
+- [ ] Configuration, runtime processes, utility functions, and document commitments do not conflict with each other.
 
-## 原创性
+## Originality
 
-- [ ] 不存在缺少许可证依据的非平凡复制代码或文本。
-- [ ] 实现已用目标项目原生风格表达。
-- [ ] 参考项目影响被总结为思想、模式或行为。
-- [ ] 如许可证要求，已保留必要署名。
+- [ ] There is no non-trivial copying of code or text that lacks a license basis.
+- [ ] Implementation has been expressed using the native style of the target project.
+- [ ] Reference project impact summarized as thoughts, patterns, or behaviors.
+- [ ] Where required by the license, necessary attribution has been retained.
 
-## 质量
+## Quality
 
-- [ ] 测试或验证步骤覆盖了被吸收的行为。
-- [ ] 错误与边界场景已处理。
-- [ ] 依赖新增有充分理由。
-- [ ] 文档和示例已更新。
-- [ ] 选用的项目形态探针与实际目标相关，没有做无关全量扫描。
+- [ ] The test or verification step covers the absorbed behavior.
+- [ ] Errors and edge scenarios have been handled.
+- [ ] There are good reasons to rely on new additions.
+- [ ] Documentation and examples updated.
+- [ ] The selected project form probe is related to the actual target, and no irrelevant full scan is performed.
 
-## 交付
+## Delivery
 
-- [ ] 已总结面向用户的变更。
-- [ ] 已说明被拒绝的候选项。
-- [ ] 已记录风险和后续工作。
+- [ ] User-facing changes summarized.
+- [ ] Rejected candidates have been described.
+- [ ] Risks and follow-up actions documented.