existing-project-migration

Original：🇺🇸 English

Translated

Use this skill for Customware existing-project migration tasks that convert uploaded `projects.zip`, `database.zip`, and `domain.zip` artifacts into the standard full-stack Customware target app. This skill is for `migration_setup` and `migration_convert` tasks and enforces zip-driven source discovery, migration-plan creation, source-workflow parity, and source-derived Playwright verification.

4installs

Sourcecustomware-ai/skills

Added on2026-05-05

NPX Install

npx skill4agent add customware-ai/skills existing-project-migration

SKILL.md Content

View Translation Comparison →

Existing Project Migration

Use this skill for the two import migration tasks:

```
migration_setup
```
```
migration_convert
```

Source Authority

The uploaded artifacts drive the migration.

Priority:

```
.import/project/
```
from
```
projects.zip
```
is the primary source for product behavior, routes, UI, workflows, integrations, and business logic.
```
.import/database/
```
from
```
database.zip
```
is the primary source for persisted entities, table shape, and schema inference.

.import/domain/

and

.import/domain-source.txt

from

domain.zip

are supporting domain context.

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.

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.

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.

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.

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.