effect-service

Generate Effect-TS services with typed interfaces, DI tags, and Layer.live implementations.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/legacy3/wowlab --skill effect-service
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: effect-service
Source: https://github.com/legacy3/wowlab/tree/main/.claude/skills/effect-service
Command: npx skills add https://github.com/legacy3/wowlab --skill effect-service

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Generate new Effect-TS services with proper patterns. Use when creating new services, layers, or adding methods to existing services.

Core Features & Use Cases

  • Interface & Tag: Define a typed contract and a DI tag for your service.
  • Live Layer Template: Provide a ready-to-use Effect Layer for production.
  • Alternative: Effect.Service Pattern: Show a simpler default pattern for small services.

Quick Start

Create and scaffold a new service using the provided templates, replacing placeholders with your domain logic.

Frequently Asked Questions about effect-service

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

FAQPage Schema
How do I generate a new Effect-TS service with proper dependency injection patterns?

Generate a new Effect-TS service by defining a typed interface and DI tag, then applying the Skill's Layer.live template or Effect.Service pattern. The Skill scaffolds the complete service structure with proper dependency injection tagging and naming conventions.

What's the best way to structure Effect-TS services with layers and DI tags?

Structure services using the Skill's template: define a typed interface contract, create a DI tag for dependency resolution, implement a Layer.live for production use, and export through barrel files. This ensures consistent patterns across your Effect-TS architecture.

Can I add methods to existing Effect-TS services using this pattern?

Yes. The Skill supports extending existing services by generating new methods that maintain your project's Effect-TS patterns, including typed interfaces, DI tags, and Layer implementations without breaking consistency.

Do I need to manually write Layer.live implementations for each Effect-TS service?

No. The Skill provides ready-to-use Layer.live templates that you customize with your domain logic, eliminating boilerplate and ensuring your implementation satisfies Effect-TS functional and technical requirements.

What's the difference between using Layer.live and Effect.Service patterns in Effect-TS?

Layer.live provides a full production-ready implementation with dependency injection composition. Effect.Service offers a simpler default pattern for smaller services. The Skill generates both templates so you choose based on your service complexity.

How do I ensure consistent naming conventions across multiple Effect-TS services?

The Skill enforces naming conventions through its templates: typed interfaces, DI tags, Layer implementations, and barrel re-exports follow standardized patterns, ensuring consistency across all services you generate in your Effect-TS project.