fec-alchemy · diff
git:20260607.44659b6 to git:20260611.9d7f5e4
50 added, 50 removed. Audit A to A.
---
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.