effect-usage-cc

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.