Organize TypeScript backend logic into reusable services with defineService and dependency injection.
npx skills add https://github.com/perimetre/ai-toolkit --skill services
Please help me install this Agent Skill. Skill: services Source: https://github.com/perimetre/ai-toolkit/tree/main/plugins/perimetre-apps/skills/services Command: npx skills add https://github.com/perimetre/ai-toolkit --skill services
Decouple business logic from HTTP routes by organizing it into reusable, testable service modules that sit between routes/controllers and data sources.
Define a new service using defineService, implement a getById method, and invoke it from a route to perform a business operation.
High-intent search queries and answers about installing and using this skill.
To decouple business logic from HTTP routes in a TypeScript backend, you can encapsulate domain logic and orchestration into reusable service modules that sit between routes and data sources. This separation keeps routes thin and makes logic easily testable.
The best way to organize backend logic for dependency injection in TypeScript is by defining services that accept a context object for dependencies. This allows you to compose services from data sources, APIs, and other services without tight coupling.
To handle success and error results in TypeScript services without throwing exceptions, return results as discriminated unions using an ok discriminator. This pattern allows explicit success and error handling directly from the service output.
Yes, you can compose multiple backend services together using tRPC and TypeScript. By defining services with a dedicated API and injecting dependencies, you can orchestrate end-to-end workflows by calling other services within a single service method.
You should keep API routes thin and delegate logic to services to achieve a clean separation of concerns across routes and data layers. This architecture enables easy testing, high reusability, and maintainable end-to-end workflows.
Yes, you need to use the defineService API to define a service in your TypeScript backend architecture. This API requires a context object for dependencies and structures your domain logic to sit between controllers and data sources.
mepukaDefine service interfaces and bind live/test implementations through layers.
SwokingCreate API action controllers extending BaseAction for standardized JSON endpoints.
mDevsLabsVerify backend API changes end-to-end via the LobeHub CLI against a local dev server.
c0x12cDesigns RPC-style APIs with Controller, Manager, Repository layers.
