Define and enforce a structured service layer with domain-specific errors.
npx skills add https://github.com/EpicenterHQ/epicenter --skill services-layer
Please help me install this Agent Skill. Skill: services-layer Source: https://github.com/EpicenterHQ/epicenter/tree/main/.agents/skills/services-layer Command: npx skills add https://github.com/EpicenterHQ/epicenter --skill services-layer
Defines and enforces a clean, testable service layer pattern with domain-specific errors and consistent Result-based flows across platforms.
Create a new service by defining domain errors with createTaggedError, exporting a live instance, and implementing methods that follow the three-layer architecture.
High-intent search queries and answers about installing and using this skill.
A service layer pattern separates business logic from UI and data access using a three-layer architecture (Service → Query → UI). You need it to enforce modularity, create testable services, and standardize domain-specific error handling across platforms.
Structure domain-specific errors using createTaggedError to attach contextual metadata. This Result-based error handling approach ensures consistent error messaging, namespaces exports correctly, and maintains reliable service flows across desktop and web variants.
Implement Result-based error handling by creating tagged domain errors with contextual metadata and structuring service methods to return Result objects. This enforces consistent messaging and testing practices across your three-layer architecture.
Yes, the service layer pattern applies platform-aware variants to support both desktop and web. It organizes namespace exports and domain logic to maintain consistent errors and flows across different platform implementations.
The best way is using a namespace export pattern alongside tagged error creation. This modular approach cleanly separates service instances, domain errors with contextual data, and platform-specific variants for maintainable code.
Test domain errors and service implementations by validating createTaggedError metadata and Result-based flows. The structured three-layer architecture ensures services remain isolated, allowing you to verify consistent error messaging and domain logic independently.
jota-batutaEnforce strict TypeScript/Node.js backend conventions with Result-based error handling and Zod environment validation.
alejandro-technologyEnforce centralized error handling across service, application, and UI layers.
PTKDrakeGuide Laravel application architecture planning with pattern selection and project structure.
agusmdevImplement FastAPI Router-Service-Repository layers with async SQLAlchemy and Pydantic v2.
