effect-v4-imports

Standardize Effect v4 module imports with enforced aliases and namespace policies.

68|13|Updated Aug 9, 2025

Search Tags:#code quality #typescript #refactoring #migration #imports #effect

Ready to run

npx skills add https://github.com/kriegcloud/beep-effect --skill effect-v4-imports

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: effect-v4-imports
Source: https://github.com/kriegcloud/beep-effect/tree/main/.agents/skills/effect-v4-imports
Command: npx skills add https://github.com/kriegcloud/beep-effect --skill effect-v4-imports

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps manage and standardize imports when migrating to Effect v4, ensuring cleaner code and adherence to best practices.

Core Features & Use Cases

Alias Management: Enforces specific aliases for common Effect modules (e.g., effect/Array to A).
Module Policy: Guides the preference for dedicated namespace imports over root imports.
Migration Support: Discourages the use of deprecated v3 APIs and specific unstable modules.

Quick Start

Use the effect-v4-imports skill to apply standard aliases for Effect v4 imports.

Frequently Asked Questions about effect-v4-imports

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

FAQPage Schema

How do I standardize Effect v4 imports for TypeScript code quality?▼

Standardize Effect v4 imports by enforcing specific module aliases like Array to A and Option to O, ensuring namespace-first helper module policies, and migrating deprecated package paths for cleaner codebases.

What is the best way to migrate deprecated Effect v3 API imports?▼

Migrate deprecated Effect v3 API imports by discouraging the use of deprecated v3 APIs and specific unstable modules, replacing them with stable Effect v4 module paths to ensure adherence to stable module policies.

How do I enforce A/O/P/R/S aliases for Effect modules during refactoring?▼

Enforce A/O/P/R/S aliases for Effect modules during refactoring by applying standard import aliases such as mapping effect/Array to A, ensuring consistent namespace-first helper module imports across the codebase.

Does Effect v4 prefer dedicated namespace imports over root imports?▼

Yes, Effect v4 prefers dedicated namespace imports over root imports. This module policy guides developers to use specific namespace-first helper module imports to maintain import hygiene and codebase cleanliness.

Why should I use namespace-first helper module imports in Effect v4?▼

Use namespace-first helper module imports in Effect v4 to satisfy requirements for cleaner codebases, enforce import hygiene, and ensure adherence to stable module policies during your TypeScript migration.