Register Effect Workspace Packages
When to Use
Create or move an Effect workspace package while checking registration, exports, generated barrels and packed contents.
Workflow
Compare the closest package with the same runtime and publishing role. Update the relevant workspace discovery, TypeScript, build, test, export-map and release surfaces. Keep dependency declarations aligned with runtime and peer roles. Regenerate owned barrels through codegen. Verify local resolution, public type checks and, for a publishable package, the dry pack contents and entrypoints. Apply repository changeset rules.
Example
Move a publishable workspace package and confirm both development imports and packed exports still resolve.
Limitations
Requires the relevant Effect workspace and its versioned tools. Use local project policy and authorized fixtures. Results cover only the checked packages and environments.
Bundled resources
Use the bundled local references for the applicable branch of the workflow: dependencies, publishing, registration. Run commands against the target Effect workspace.
Source
Adapted from the pinned skill tree. See the MIT license.
This snapshot of Effect v4 is vendored by Local Studio.