What problem does it solve?
This skill resolves the architectural confusion and dependency conflicts inherent in porting or building command-line tools for the Effect v4 ecosystem, where traditional CLI packages are deprecated or incompatible.
Core Features & Use Cases
- Framework Guidance: Provides the correct mapping from deprecated v3 packages to the new core-integrated modules like effect/unstable/cli and effect/unstable/process.
- Architectural Best Practices: Defines the strict separation between pure libraries and integrated CLI packages, ensuring proper dependency management and exit-code contracts.
- Use Case: Use this skill when you need to implement a new CLI tool that requires file system access, process spawning, or terminal interaction while maintaining strict type safety and avoiding the common pitfalls of the v3-to-v4 transition.
Quick Start
Ask the assistant to explain the correct implementation of a Command environment for a new CLI tool using the effect v4 core modules.