Jeden Skill in Manus ausführen
mit einem Klick

Jeden Skill in Manus mit einem Klick ausführen

Loslegen

create-service

Sterne5

Forks0

Aktualisiert23. März 2026 um 23:39

Scaffold a new service class for data source interaction with tests and docblocks

Installation

Mit Codex oder Claude installieren Kopieren Sie diesen Prompt, fügen Sie ihn in Codex, Claude oder einen anderen Assistant ein und lassen Sie die Skill-Seite prüfen und installieren.

In Manus ausführen

Quelle

olavoasantos

olavoasantos/cliui

GitHub-Repository öffnen Creator-Repositorys ansehen

Download

In Manus ausführen

Verwandte BerufeSOC

Basierend auf der SOC-Berufsklassifikation

SoftwareentwicklerInformatik- und Mathematikberufe·SOC 15-1252

SKILL.md

readonly

name	create-service
description	Scaffold a new service class for data source interaction with tests and docblocks
user-invocable	false

Create Service

When creating a new service in this project, follow these conventions exactly.

File Placement

src/services/
├── ThingService.ts
└── specs/
    └── ThingService.unit.ts

Conventions

Naming: PascalCase with Service suffix.
Export: Single named export per file. No default exports.
Role: Services mediate mutations on data sources. They are the only layer that should write to data source state.
Layer separation: Services must not import from UI-specific modules (components, hooks, context providers).
Docblocks: The service class and all public methods must have JSDoc/TSDoc comments.
Tests: Every service must have a corresponding *.unit.ts file.

Checklist

Create src/services/<ServiceName>Service.ts with a single named export
Add JSDoc/TSDoc to the class and all public methods
Create src/services/specs/<ServiceName>Service.unit.ts with unit tests
Export from src/index.ts if the service is part of the public API
Register types in src/register.d.ts if applicable
Run pnpm run check to verify

Mehr aus diesem Repository

gleiches Repository

create-changeset

olavoasantos/cliui

Create a changeset entry describing changes to workspace packages

2026-04-175

create-component

olavoasantos/cliui

Scaffold a new UI component with the correct folder structure, styles, tests, and docblocks

2026-03-265

create-class

olavoasantos/cliui

Scaffold a new class with the correct file structure, naming, tests, and docblocks

2026-03-255

create-guard

olavoasantos/cliui

Scaffold a new runtime type guard with the correct naming and docblocks

2026-03-255

create-utility

olavoasantos/cliui

Scaffold a new utility function with the correct naming, tests, and docblocks

2026-03-255

write-tests

olavoasantos/cliui

Write tests following this project's testing conventions, file patterns, and placement rules

2026-03-255

name	create-service
description	Scaffold a new service class for data source interaction with tests and docblocks
user-invocable	false

Create Service

When creating a new service in this project, follow these conventions exactly.

File Placement

src/services/
├── ThingService.ts
└── specs/
    └── ThingService.unit.ts

Conventions

Naming: PascalCase with Service suffix.
Export: Single named export per file. No default exports.
Role: Services mediate mutations on data sources. They are the only layer that should write to data source state.
Layer separation: Services must not import from UI-specific modules (components, hooks, context providers).
Docblocks: The service class and all public methods must have JSDoc/TSDoc comments.
Tests: Every service must have a corresponding *.unit.ts file.

Checklist

Create src/services/<ServiceName>Service.ts with a single named export
Add JSDoc/TSDoc to the class and all public methods
Create src/services/specs/<ServiceName>Service.unit.ts with unit tests
Export from src/index.ts if the service is part of the public API
Register types in src/register.d.ts if applicable
Run pnpm run check to verify