migrate-to-multi-artifact

Migrate single-app projects into a pnpm workspace supporting multiple artifacts.

Updated Apr 20, 2026
One-click install
npx skills add https://github.com/AmirEmad11/instabot --skill migrate-to-multi-artifact-amiremad11
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: migrate-to-multi-artifact
Source: https://github.com/AmirEmad11/instabot/tree/main/.local/secondary_skills/migrate-to-multi-artifact
Command: npx skills add https://github.com/AmirEmad11/instabot --skill migrate-to-multi-artifact-amiremad11

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? When a user wants to add a mobile app, slide deck, or any second app alongside an existing project, the project must first be restructured to support multiple artifacts. This Skill orchestrates that migration without breaking the existing app. ## Core Features & Use Cases - Migration Proposal Workflow: Creates plan files under .local/tasks/ and calls proposeMigration with a port task plus optional follow-up tasks. - Canonical Port Plans: Provides ready-to-copy port rubrics for fullstack_js and Expo projects, plus a template for follow-up task plans (mobile apps, slides, video, auth). - Verification Scripts: Includes shell scripts that detect project structure, copy backend/frontend files, fix imports (zod/v4, @workspace/db), and run post-migration sanity checks. - Use Case: A user with an existing restaurant website asks for a mobile companion app. The Skill ports the website into a pnpm workspace, then guides building an Expo app that reuses the same brand assets, colors, and fonts. ## Quick Start Ask the assistant to migrate the project to multi-artifact support so a mobile app can be added alongside the existing app.

Frequently Asked Questions about migrate-to-multi-artifact

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I add a mobile app to an existing web project?

First migrate the project to a multi-artifact pnpm workspace, then create an Expo artifact. The migration ports the existing app unchanged; the follow-up task builds the mobile app reusing the same brand assets, colors, and fonts.

How to migrate an Expo app into a pnpm workspace?

Copy app.json, the app/ routing directory, and all source directories into a new Expo artifact, then fix imports to use generated hooks from @workspace/api-client-react. Run the expo_sanity_check.sh script to verify all directories, imports, and assets were copied.

Does the migration change how my existing app looks or works?

No. The port task's goal is exact visual and functional parity. New features, refactoring, and bug fixes are explicitly out of scope; only file moves and import fixes are performed.

Why does pnpm dev fail at the workspace root after migration?

The workspace root has no dev script by design. Artifacts run via workflows using restart_workflow, which wires required environment variables like PORT and BASE_PATH. Root-level pnpm dev failing is expected, not a migration error.

What happens to Tailwind v3 projects during migration?

The frontend copy script detects Tailwind v3, copies the tailwind config, fixes content paths, installs tailwindcss@3 with postcss and autoprefixer, and removes the @tailwindcss/vite plugin to avoid conflicts.