effect-usage-cc

Evaluate Effect (effect-ts) adoption for TypeScript components with five-level verdicts.

Updated Apr 16, 2026
One-click install
npx skills add https://github.com/bengous/agents-skills --skill effect-usage-cc
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: effect-usage-cc
Source: https://github.com/bengous/agents-skills/tree/main/effect-usage-cc
Command: npx skills add https://github.com/bengous/agents-skills --skill effect-usage-cc

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires jq, rg, and includes scripts (resource) and references (resource) components.

What problem does it solve?

Developers and architects frequently struggle to decide whether the Effect (effect-ts) model is the right abstraction for a given TypeScript component; this Skill turns ambiguous adoption questions into documented, per-component verdicts and clear trade-offs so teams avoid unnecessary ceremony or fragile designs.

Core Features & Use Cases

  • Decision matrix & verdicts: Provides a five-level verdict (Required, Recommended, Optional, Discouraged, Not Appropriate) for contexts like API servers, job workers, database layers, CLIs, and integrations.
  • Guardrails & anti-pattern detection: Enumerates common mistakes (wrapping pure functions, single-use layers, nested runSync, Effect in React) and advises corrective actions with provenance markers for assertions.
  • References & tooling: Links to detailed reference docs for adoption strategy, core patterns, error handling, testing, and includes a probe script to assess a repository's Effect posture.
  • Use case: Use this Skill during architecture reviews to decide whether to convert a service to Effect, to design Effect boundaries, or to audit existing Effect adoption for overuse or gaps.

Quick Start

Ask the skill to evaluate a specific module or service and return a verdict with reasoning, provenance markers, and referenced guidance.

Frequently Asked Questions about effect-usage-cc

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

FAQPage Schema
When should I use Effect in TypeScript projects?

Effect is recommended for API servers, job workers, database layers, CLIs, and integrations requiring structured error handling and resource lifecycle management. A five-level verdict helps decide adoption and avoid unnecessary ceremony or fragile designs.

How do I decide if an Effect adoption architecture review is needed for a service?

Evaluate structural leverage, error and resource lifecycle needs, and component boundaries to determine if an architecture review is needed. Exclude React component logic and trivial scripts, focusing on service design, worker pipelines, and integration points for a documented verdict.

Does Effect work with React components in TypeScript?

Effect is not appropriate for React component logic in TypeScript. The decision support tool explicitly excludes React components from its evaluation scope, advising against wrapping UI logic and recommending corrective actions to prevent anti-patterns.

What are common Effect anti-patterns and how do I fix them?

Common anti-patterns include wrapping pure functions, creating single-use layers, nesting runSync, and using Effect in React. Corrective actions are provided with provenance markers to audit existing adoption for overuse or gaps.

Can I audit my repository's existing Effect adoption posture?

You can audit your repository's Effect adoption posture using an included probe script. This tool assesses existing usage, identifies gaps or overuse, and returns a verdict with references and guardrails for corrective actions.