extract-to-package

Extract a Unity module into a standalone UPM package with asmdefs and tests.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/punkfuncgames/tetris-clone --skill extract-to-package
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: extract-to-package
Source: https://github.com/punkfuncgames/tetris-clone/tree/main/.claude/skills/extract-to-package
Command: npx skills add https://github.com/punkfuncgames/tetris-clone --skill extract-to-package

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Extracts a generic Unity module from the game into a reusable UPM package, enabling teams to share mature modules across projects and reduce duplication.

Core Features & Use Cases

  • Module scoping & boundaries: clearly delineates the module to extract, its dependencies, and testing surface.
  • Package scaffolding: creates a standard Packages/com.punkfuncgames.extract-to-package/ layout, asmdef files, and runtime/tests structure.
  • Migration guidance: provides a repeatable pipeline from module to package with validation steps.

Quick Start

Run the module extraction workflow to package the targeted Unity module into a reusable UPM package ready for repository publishing.

Frequently Asked Questions about extract-to-package

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

FAQPage Schema
How do I extract a Unity module into a reusable UPM package?

Extracting a Unity module into a UPM package involves scoping module boundaries, scaffolding standard folder structures with asmdef files, and defining a reproducible migration workflow with validation steps.

What is the best way to modularize Unity game code for reuse across projects?

Modularizing Unity game code for reuse involves extracting generic modules into standalone UPM packages, eliminating hard references to the original game, and providing dependency mapping with guardrails.

How do I set up asmdef files and tests when migrating code to a Unity package?

Setting up asmdef files and tests during Unity package migration requires scaffolding a standard runtime and tests directory structure under the Packages folder to establish a reproducible packaging workflow.

Does this Unity package extraction workflow handle dependencies on the original game?

The Unity package extraction workflow eliminates hard references to the original game by providing dependency mapping and guardrails, allowing the standalone UPM package to operate independently across projects.

Can I use this to prepare a Unity package for archiving in a GitHub repo?

Yes, this workflow packages your targeted Unity module into a reusable UPM package with a standard folder structure, asmdef files, and documentation, making it ready for repository publishing and archiving.