effect-v4-cli

Guide Effect v4 CLI builds with effect/unstable/cli and process modules.

2|Updated Jul 2, 2026
One-click install
npx skills add https://github.com/spencerbeggs/effected --skill effect-v4-cli
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: effect-v4-cli
Source: https://github.com/spencerbeggs/effected/tree/main/plugin/skills/effect-v4-cli
Command: npx skills add https://github.com/spencerbeggs/effected --skill effect-v4-cli

SYSTEM DOCUMENTATION & REQUIREMENTS

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.

Frequently Asked Questions about effect-v4-cli

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

FAQPage Schema
How do I build a type-safe CLI using Effect v4 core modules?

Build a type-safe CLI using Effect v4 by utilizing the effect/unstable/cli module for command structures and effect/unstable/process for child process management, ensuring strict exit-code contracts and proper service layer provision for Node.js environments.

Why does my @effect/cli package break when upgrading to Effect v4?

The @effect/cli package breaks during an Effect v4 upgrade because traditional CLI packages are deprecated and incompatible. Migrate architectural implementations to the new core-integrated effect/unstable/cli module to resolve dependency conflicts.

What is the correct way to manage child processes in an Effect v4 CLI?

Manage child processes in an Effect v4 CLI by using the effect/unstable/process module. This core-integrated module ensures proper child process management and service layer provision within Node.js environments.

How do I enforce strict exit-code contracts in a Node.js CLI built with Effect?

Enforce strict exit-code contracts in a Node.js CLI by applying Effect v4 architectural best practices. Define strict separation between pure libraries and integrated CLI packages to ensure proper process termination and service layer provision.

Can I use Effect v4 for command-line tools that require file system access and terminal interaction?

Yes, use Effect v4 for command-line tools requiring file system access and terminal interaction. The framework provides core-integrated modules that maintain strict type safety while avoiding common v3-to-v4 transition pitfalls.