services
AdonisJS service patterns (creation, registration, components). Use when adding or modifying services.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
메뉴
AdonisJS service patterns (creation, registration, components). Use when adding or modifying services.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Run, write, and troubleshoot Japa browser tests that use Playwright; use when you add or change frontend functionality that should be covered by tests
Testing guidelines. Use when writing or updating tests.
Caching with @adonisjs/cache (keys, tags, invalidation). Use when adding or debugging cache behavior.
Lucid models/migrations conventions and safe workflows. Use when changing schema or models.
Writing documentation. Use when key functionality is added or changed
Frontend rules conventions. Use when working with frontend-related tasks.
| name | services |
| description | AdonisJS service patterns (creation, registration, components). Use when adding or modifying services. |
| metadata | {"short-description":"AdonisJS service patterns."} |
app/services (path alias #services)node ace make:service ServiceName which will instantiate a new class in the #services folder.
@inject() class decorator should be used to inject other services when needed.Services are built using Components.
Services represents the what, Components represents the how it's done.
Both services and components are classes.
Components can be placed in the same file as the main service if they are specific to that service
One service can rely on many components
Components are injected into services, and their main purpose is to be swapped with component fakes during testing.
Fakes can be declared directly in test files if they are only relevant locally
Component fakes can be stateful objects