effect

Model effects, failures, resources, and execution boundaries in Effect, Cats Effect 3, or ZIO codebases.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps you design, write, review, and debug code so that effects, dependencies, failures, resource lifetimes, and execution boundaries stay visible instead of hidden in control flow.

Core Features & Use Cases

  • Effect-aware design: Model observable work, state changes, concurrency, cancellation, and cleanup explicitly.
  • Library-guided implementation: Follow the project's existing effect system patterns and the matching guidance for Effect, Cats Effect 3, or ZIO.
  • Safe boundary handling: Keep supported work inside the effect system and require explicit approval before any unavoidable escape hatch.
  • Verification-first workflow: Check the real public API, installed version, tests, and runtime behavior before trusting a solution.

Quick Start

Use the effect skill to analyze this codebase and tell me how to keep its effects, failures, resources, and execution boundaries explicit.

Frequently Asked Questions about effect

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

FAQPage Schema
How do I keep effects explicit and manage resource cleanup in Scala effect systems?

To keep effects explicit, model observable work, failures, and resource cleanup directly within your chosen effect system like Effect, Cats Effect 3, or ZIO, preserving ownership and execution boundaries throughout the code.

What is the best way to handle concurrency and cancellation in ZIO or Cats Effect?

Handling concurrency and cancellation in ZIO or Cats Effect requires modeling state changes explicitly within the effect system, keeping supported work inside its boundaries and verifying behavior before using any non-effectful escape hatch.

How do I design effect-aware code that safely handles execution boundaries?

Designing effect-aware code involves modeling dependencies and execution boundaries visibly, matching the installed public API of your effect system, and requiring explicit approval before relying on any unavoidable escape hatches.

Can I use escape hatches for unsupported work inside Cats Effect 3 or ZIO?

Escape hatches in Cats Effect 3 or ZIO require explicit approval before use, ensuring supported work stays inside the effect system while preserving ownership and cleanup for any unavoidable boundary crossings.

Why does my effect system code fail to preserve resource lifetimes during cancellation?

Effect system code fails to preserve resource lifetimes when cleanup is hidden in control flow, which this approach solves by modeling failures and cleanup explicitly and verifying runtime behavior before trusting the solution.

Do I need to verify the installed public API before implementing effects in Scala?

Yes, you must verify the real public API, installed version, tests, and runtime behavior before implementing effects, ensuring the solution matches the project's existing effect system patterns and preserves safe execution.