# Dvt New Service Scaffold

> Use when creating a new backend service at DVT. Scaffolds the standard service layout, health checks, structured logging, and CI wiring so every service starts from the same baseline.

- Skill: `bassonrichard/dvt-new-service-scaffold` (Agent Skill, multi-file: 2 files)
- Install (CLI): `npx skillmds@latest add bassonrichard/dvt-new-service-scaffold`
- Raw SKILL.md: https://api.skillmd.com/api/skills/bassonrichard/dvt-new-service-scaffold/raw
- Safety review: pending (external: skill-scanner PASS, skillspector PASS)
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: bassonrichard (https://skillmd.com/u/bassonrichard)
- Updated: 2026-09-22
- Page: https://skillmd.com/skills/bassonrichard/dvt-new-service-scaffold

---


# DVT New Service Scaffold

Stand up a new DVT backend service that matches the house architecture on day one.

## When to use this skill

Use this skill when you need to:
- Create a brand-new backend service or microservice.
- Bring an existing prototype up to the DVT baseline.

## Standard layout

```
src/
  api/          # transport layer (HTTP/gRPC handlers) — thin
  domain/       # business logic, no framework imports
  infra/        # db, queues, external clients
  config/       # typed config loaded from env
test/
```

## Steps

1. Create the layout above; keep `domain/` free of framework/transport imports.
2. Add a `/healthz` (liveness) and `/readyz` (readiness) endpoint.
3. Wire structured JSON logging with a request/correlation id on every log line.
4. Load config from environment via a typed config module — never read `process.env` directly in business code.
5. Add the standard CI pipeline (lint → test → build → container scan).

## References

| Reference | When to load |
|---|---|
| references/checklist.md | Full pre-merge checklist for a new service |