backend-patterns

Files (2)

• SKILL.md
• SKILL.md.lock

SKILL.md (first lines)

<!-- bodyRef: skills/sources/backend-patterns.md -->

<!-- Generated by `harness skills bootstrap`. Edit to tune; re-run to regenerate. -->
<!-- Static skills point at live docs by design — do not hardwire version-pinned API here. -->

Use this skill when building or reviewing backend services.

## Concepts (timeless)
- Layer the code: transport/handler → service (business logic) → repository (data access). Keep business logic independent of storage and framework.
- Validate untrusted input at the system boundary; never trust data from the wire.
- Make external effects idempotent and bounded (timeouts, retries with backoff, circuit-breaking).
- Return a consistent result/error shape; log detailed context server-side, surface safe messages outward.
- Prefer dependency injection over globals so the service is testable.

## Pull current docs first
Frameworks, ORMs, and client SDKs evolve — confirm the current API before coding:
- your framework's current docs (use Context7 or WebFetch)

## Checklist
- [ ] Clear handler/service/repository boundaries; no business logic in handlers
- [ ] Inputs validated at the boundary with a schema
- [ ] Timeouts + bounded retries on every outbound call
- [ ] No N+1 queries; queries are bounded/paginated
- [ ] Errors logged with context; no sensitive data leaked to clients

## Gotchas

_Highest-signal section. Seed empty; grow it from real failures this skill
hits — `harness skills propose` suggests entries here from drift evidence._

- _none observed yet_

From ichiorca/shipsignal, Apache-2.0.

More from ichiorca/shipsignal