migrating-to-product-sdk

Automating codebase migration to @parity/product-sdk requires this Skill to detect legacy stacks and generate a migration spec. It creates a decision matrix and writes specifications to `.claude/migrations/specs/` without modifying code or running tests.

Legacy stacks detected during product-sdk migration include polkadot-apps, novasamatech, hand-rolled crypto/IPFS, and polkadot-api 1.x. The Skill identifies these stacks in the target repo and determines which migration areas apply using a decision matrix.

Generating a migration spec for a legacy product codebase involves running the Skill against a target workspace containing package.json files. It outputs the specification at `.claude/migrations/specs/`, which can be committed or opened as a GitHub issue.

Automated migration to product-sdk cannot be used to modify code or run tests. The Skill performs discovery, decision matrix analysis, and spec writing, requiring human approval at checkpoints before any downstream code changes are made.

Package.json files are required to migrate a codebase to product-sdk. The Skill needs a target workspace with package.json files and potential dependencies to perform discovery and generate the migration specification accurately.

Product-sdk migration requires human approval at checkpoints because the Skill only generates specifications and does not modify code. This ensures developers review the decision matrix analysis and migration spec before proceeding with actual code changes.