Skip to content
Back to skills

Backend Service Implementation

ASecurity

Implement a backend service or API change from contract through domain logic, validation, persistence, failure handling, tests, and observability.

  • 16 stars
  • 0 votes
  • 0 copies
  • 2 views
  • Added September 11, 2026
ai-agentsapibackend

Works with

  • api

Security analysis

A100/100

Scanned September 11, 2026

npx -y skills add Dadmin88/hermes-profile-packs --skill backend-service-implementation --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Backend Service Implementation?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Backend Service Implementation
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/dadmin88-backend-service-implementation/badge)](https://www.skillsdirectory.com/skills/dadmin88-backend-service-implementation)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: backend-service-implementation
description: Implement a backend service or API change from contract through domain logic, validation, persistence, failure handling, tests, and observability.
---
# Backend Service Implementation

Use for server-side application features, APIs, jobs, and domain behavior.

## Procedure
1. Read product acceptance criteria, architecture/interface decisions, existing conventions, and relevant data contracts.
2. Trace the current request/data path before editing.
3. Define or confirm inputs, authorization, validation, domain invariants, outputs, and error semantics.
4. Implement the smallest cohesive change while preserving compatibility unless a migration is explicitly approved.
5. Handle persistence boundaries, transactions, retries, and external dependencies deliberately.
6. Add tests at the cheapest layer that proves the changed behavior and important failures.
7. Run targeted checks and inspect logs/metrics or runtime behavior when applicable.
8. Hand off interface changes and migration implications to dependent specialists.

## Quality gate
The change is done when behavior is correct under normal and failure conditions, tests prove the relevant contract, and operationally important failures are diagnosable.

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…