Back to Details

existing-project-migration

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

Existing Project Migration

现有项目迁移

Use this skill for the two import migration tasks:
  • migration_setup
  • migration_convert
本技能适用于两种导入迁移任务：
  • migration_setup
  • migration_convert

Source Authority

源优先级

The uploaded artifacts drive the migration.
Priority:
  1. .import/project/
    from 
    projects.zip
    is the primary source for product behavior, routes, UI, workflows, integrations, and business logic.
  2. .import/database/
    from 
    database.zip
    is the primary source for persisted entities, table shape, and schema inference.
  3. .import/domain/
    and 
    .import/domain-source.txt
    from 
    domain.zip
    are supporting domain context.
  4. Org name, description, logos, colors, and brand context are presentation context only.
Do not let org/company knowledge redefine the imported app's product domain, workflows, entities, or schema.
上传的工件主导迁移流程。
优先级顺序：
  1. projects.zip
    中的
    .import/project/
    是产品行为、路由、UI、工作流、集成和业务逻辑的主要来源。
  2. database.zip
    中的
    .import/database/
    是持久化实体、表结构和模式推断的主要来源。
  3. domain.zip
    中的
    .import/domain/
    和
    .import/domain-source.txt
    为领域上下文提供支持。
  4. 组织名称、描述、标志、颜色和品牌上下文仅作为展示层信息。
请勿让组织/公司相关知识重新定义导入应用的产品领域、工作流、实体或模式。

Fixed Target Stack

固定目标技术栈

Migrate into the prepared Customware full-stack target:
  • Vite
  • React Router
  • TypeScript
  • Zod
  • Node
  • Hono
  • tRPC
  • SQLite via 
    better-sqlite3
  • Drizzle ORM and migrations
Do not preserve the uploaded source app's original stack as the runtime stack.
迁移至预先准备好的Customware全栈目标技术栈：
  • Vite
  • React Router
  • TypeScript
  • Zod
  • Node
  • Hono
  • tRPC
  • 通过
    better-sqlite3
    实现的SQLite
  • Drizzle ORM和迁移工具
请勿保留上传源应用的原始技术栈作为运行时栈。

Required References

必要参考文档

Read the reference for the current task before doing any work:
  • migration_setup
    : 
    .agents/skills/existing-project-migration/references/migration-setup.md
  • migration_convert
    : 
    .agents/skills/existing-project-migration/references/migration-convert.md
If the task kind is unclear, read both references and determine which one matches the active task text.
在开展任何工作前，请阅读当前任务对应的参考文档：
  • migration_setup
    ：
    .agents/skills/existing-project-migration/references/migration-setup.md
  • migration_convert
    ：
    .agents/skills/existing-project-migration/references/migration-convert.md
若任务类型不明确，请阅读两份参考文档并判断哪一份与当前任务文本匹配。

Shared Rules

通用规则

  • Keep the migration zip-driven.
  • Keep org context limited to brand presentation, not app-domain decisions.
  • Keep the target runtime on the fixed Customware full-stack template.
  • Use an agent-owned checklist while working. Do not rely on external validators to decide migration quality.
  • Re-read this skill plus 
    .import/migration-checklist.md
    and 
    .import/migration-plan.json
    after any interruption or compaction before continuing work.
  • Treat unreadable or raw binary domain content as low-confidence supporting material.
  • Fail rather than complete a task that cannot identify or preserve the imported app's core workflows.
  • Verify source-derived workflows, not generic template screens.
  • Create the required migration checklist and migration plan artifacts early, then keep them updated as the source of truth while working.
  • During 
    migration_setup
    , do not read the 
    migration_convert
    reference or broad target app/server internals until the checklist and plan files already exist with initial content.
  • Do not spend more than two consecutive turns on read-only exploration without either updating a required migration artifact, changing implementation files, or calling the explicit completion or failure command.
  • If the imported source remains too ambiguous to proceed after the required source intake, fail with a concrete summary instead of continuing exploratory loops.
  • 保持迁移流程由zip包驱动。
  • 将组织上下文限制在品牌展示层面，不影响应用领域决策。
  • 确保目标运行时基于固定的Customware全栈模板。
  • 工作时使用Agent专属检查清单，不要依赖外部验证器来判断迁移质量。
  • 在中断或压缩操作后，重新阅读本技能文档以及
    .import/migration-checklist.md
    和
    .import/migration-plan.json
    ，再继续工作。
  • 将不可读或原始二进制领域内容视为低可信度辅助材料。
  • 若无法识别或保留导入应用的核心工作流，应终止任务而非强行完成。
  • 验证基于源生成的工作流，而非通用模板页面。
  • 尽早创建所需的迁移检查清单和迁移计划工件，并在工作过程中将其作为事实来源持续更新。
  • 在
    migration_setup
    阶段，在检查清单和计划文件已包含初始内容前，请勿阅读
    migration_convert
    参考文档或宽泛的目标应用/服务器内部文档。
  • 连续进行只读探索的回合数不得超过两次，期间必须更新所需的迁移工件、修改实现文件，或调用明确的完成或失败命令。
  • 若完成必要的源信息收集后，导入的源内容仍过于模糊无法继续，应终止任务并给出具体总结，而非继续进行探索循环。

Completion Gate

完成验收标准

Before completing a migration task, confirm:
  • The app domain comes from 
    .import/project/
    , 
    .import/database/
    , and 
    .import/domain/
    .
  • Org branding was used only as presentation context.
  • The generated app is not generic and not based on unrelated org/company knowledge.
  • Validation covered source-derived workflows.
  • Any skipped workflow is listed with a concrete reason.
  • The working checklist is fully checked for this task.
  • Temporary checklist/work files are cleaned up at the end of 
    migration_convert
    after verification succeeds.
  • If the checklist still has required unchecked items, do not continue into the next task and do not complete successfully.
完成迁移任务前，请确认以下事项：
  • 应用领域信息来自
    .import/project/
    、
    .import/database/
    和
    .import/domain/
    。
  • 组织品牌仅用于展示层上下文。
  • 生成的应用并非通用模板，且未基于无关的组织/公司知识构建。
  • 验证覆盖了基于源生成的工作流。
  • 任何跳过的工作流都已列出具体原因。
  • 当前任务对应的检查清单已全部勾选完成。
  • 在
    migration_convert
    阶段验证成功后，清理临时检查清单/工作文件。
  • 若检查清单仍有未勾选的必填项，请勿进入下一任务，也不要标记任务为成功完成。