skills.rest
nemmtor
nemmtorCOMMUNITY
Explore all skills by this author →
GitHub

effect-best-practices

Enforces unified Effect-TS best practices across services, errors, schemas, actions, and observability for teams building large codebases.

14|Updated Oct 6, 2025
Search Tags:#architecture#observability#effect-ts#type-safety#best-practices#tagged-errors#service-patterns
One-click install
npx skills add https://github.com/nemmtor/ts-databuilders --skill effect-best-practices-nemmtor
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: effect-best-practices
Source: https://github.com/nemmtor/ts-databuilders/tree/main/.claude/skills/effect-best-practices
Command: npx skills add https://github.com/nemmtor/ts-databuilders --skill effect-best-practices-nemmtor

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Codifies consistent, safe patterns for building with Effect-TS to minimize drift and maintenance burden across projects.

Core Features & Use Cases

  • Enforces modern service patterns with Effect.Service and automatic accessors.
  • Standardizes error handling using Schema.TaggedError and catchTag/catchTags.
  • Promotes schema-driven models, branded IDs, and explicit dependencies for reliable composition.
  • Provides guidance for tracing, layering, and observability to improve system reliability.

Quick Start

Define a new Effect-TS service using the recommended patterns: declare dependencies, wrap methods with Effect.fn, and model errors with Schema.TaggedError.

Frequently Asked Questions about effect-best-practices

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

FAQPage Schema
How do I standardize error handling in Effect-TS using tagged errors?▼

Modern service patterns in Effect-TS require using Effect.Service with automatic accessors, declaring explicit service dependencies, and wrapping methods with Effect.fn to maintain reliable composition and traceability.

How do I add tracing and observability to an Effect-TS application?▼

Tracing and observability in Effect-TS are added by wrapping service methods with Effect.fn and applying structured layering guidance. This improves system reliability by enforcing consistent tracing across all architectural boundaries.

What is the best way to structure large Effect-TS codebases for team collaboration?▼

Large Effect-TS codebases are structured for team collaboration by enforcing unified architecture patterns across services, errors, schemas, and actions. This minimizes pattern drift and reduces maintenance burden across multiple projects.

Do I need schema-driven models and branded IDs for reliable composition in Effect-TS?▼

Schema-driven models and branded IDs are required for reliable composition in Effect-TS. Promoting these patterns alongside explicit dependency declarations ensures type safety and consistent data modeling throughout the architecture.

Related Skills

Explore More Software Engineering Skills→
scotttrinhscotttrinh

effect-patterns-domain-modeling

Model TypeScript domain logic with Effect-TS patterns for error tagging and schema validation.

Community
Advanced
scotttrinhscotttrinh

effect-patterns-observability

Implement structured logging, metrics, and tracing in Effect-TS workflows.

Community
Advanced
PaulJPhilpPaulJPhilp
785

effect-patterns-domain-modeling

Model Effect-TS domains with branded types, tagged errors, and Schema validation.

Community
Intermediate
ojowwalker77ojowwalker77
110

Effect-TS Expert

Refactor TypeScript codebases to adopt Effect-TS patterns for typed errors and Layers.

Community
Advanced