skills.rest
spencerbeggs
spencerbeggsCOMMUNITY
Explore all skills by this author →
GitHub

effect-v4-house-style

Standardize Effect v4 library architecture, error handling, and testing conventions.

2|Updated Jul 2, 2026
Search Tags:#typescript#architecture#best-practices#functional-programming#coding-standards#effect
One-click install
npx skills add https://github.com/spencerbeggs/effected --skill effect-v4-house-style
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: effect-v4-house-style
Source: https://github.com/spencerbeggs/effected/tree/main/plugin/skills/effect-v4-house-style
Command: npx skills add https://github.com/spencerbeggs/effected --skill effect-v4-house-style

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill resolves architectural ambiguity and inconsistency in Effect v4 projects by providing a unified set of conventions for module layout, error handling, and service composition.

Core Features & Use Cases

  • Architectural Consistency: Defines strict rules for file naming, module exports, and internal engine separation to ensure code readability and maintainability.
  • Error Taxonomy: Establishes a standardized approach to typed errors, ensuring failures are structured, recoverable, and descriptive.
  • Use Case: Use this guide when architecting a new Effect v4 library or performing a code review to ensure the implementation aligns with the established house style for layers, testing, and observability.

Quick Start

Apply the effect-v4-house-style guidelines to the current module by reviewing the module layout and error taxonomy rules defined in the skill documentation.

Frequently Asked Questions about effect-v4-house-style

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

FAQPage Schema
How do I standardize error handling in Effect v4 library development?▼

Standardize Effect v4 error handling by establishing a strict error taxonomy that ensures failures are structured, recoverable, and descriptive across your project. This enforces consistent typed errors throughout the ecosystem.

What is the best way to structure modules and layers in an Effect v4 project?▼

The best way to structure Effect v4 modules is by applying strict rules for file naming, module exports, and internal engine separation. This architectural consistency ensures code readability and maintainability across layers.

What coding conventions should I use for TypeScript functional programming with Effect?▼

For TypeScript functional programming with Effect, use specific coding conventions including defined TSDoc habits and layer composition rules. These standards ensure adherence to the architectural patterns required for consistent maintenance.

Does this house style guide apply to Effect v4 service composition and testing?▼

Yes, this house style guide applies directly to Effect v4 service composition and testing strategies. It defines specific layer composition rules and observability postures required for consistent library maintenance.

When do I need architectural conventions for an Effect v4 library?▼

You need architectural conventions for an Effect v4 library when starting a new project or performing a code review. This resolves architectural ambiguity by providing a unified set of rules for module layout and service design.

Related Skills

Explore More Software Engineering Skills→
thinking-machines-labthinking-machines-lab
4.0k

setup

Guide Tinker installation, environment setup, API key provisioning, and verification.

Official
Intermediate
alejandro-technologyalejandro-technology

enforcement

Enforce 4-layer module structure and dependency rules during PR reviews.

Community
Advanced
MatthieuszMatthieusz

coding-standards

Validate TypeScript code against predefined coding standards using static analysis tools.

Community
Advanced
Enso-SoftEnso-Soft
1

android-conventions

Standardize Android/Kotlin naming, patterns, and code style conventions.

Community
Basic