encore-service

Define canonical Encore.ts service structures with encore.service.ts files.

26|5|Updated Jan 8, 2026
One-click install
npx skills add https://github.com/encoredev/skills --skill encore-service
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: encore-service
Source: https://github.com/encoredev/skills/tree/main/encore/service
Command: npx skills add https://github.com/encoredev/skills --skill encore-service

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Organize and standardize Encore.ts services by providing a canonical structure and patterns that reduce ambiguity and improve maintainability.

Core Features & Use Cases

  • Enforces a required encore.service.ts file and a minimal service layout (service, optional api.ts and db.ts)
  • Supports single-service, multi-service, and large-system architectures with clear boundaries
  • Guides cross-service calls using patterns from ~encore/clients and documented service-to-service guidelines

Quick Start

Create a new Encore.ts service by adding an encore.service.ts file and follow the minimal structure shown.

Frequently Asked Questions about encore-service

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

FAQPage Schema
How do I structure Encore.ts microservices for scalability?

Structure Encore.ts microservices by enforcing a required encore.service.ts file alongside optional api.ts and db.ts files to establish clear service boundaries and canonical organization for scalable architectures.

What is the canonical Encore.ts service layout pattern?

The canonical Encore.ts service layout requires an encore.service.ts file to define the service, supplemented by optional api.ts for endpoints and db.ts for database access to reduce ambiguity and improve maintainability.

How do I handle cross-service calls in Encore.ts?

Handle cross-service calls in Encore.ts by importing and using patterns from ~encore/clients, which provides typed clients for executing service-to-service communication following documented guidelines.

Can I use this Encore.ts service structure for both single-service and multi-service architectures?

Yes, this Encore.ts service structure supports single-service, multi-service, and large system-based architectures by prescribing clear service boundaries and scalable patterns applicable to projects of all sizes.

Why does my Encore.ts service organization feel inconsistent?

Encore.ts service organization feels inconsistent without a canonical structure, which this pattern solves by enforcing the required encore.service.ts file and prescribing minimal layouts to standardize service boundaries.

What's the best way to define service boundaries in Encore.ts?

The best way to define service boundaries in Encore.ts is following a canonical structure with an encore.service.ts file and optional api.ts and db.ts files, ensuring clear separation for maintainable microservices.