# Omh Backend

[omh] Designing an API, server, or data-layer change: prepare server, API, and...

- Repository: https://github.com/rlaope/oh-my-hermes (5004 stars)
- Category: Design
- License: MIT
- Last updated: 2026-11-01
- Runs scripts: no, instructions only

## Install

Claude Code: `npx skills add rlaope/oh-my-hermes --skill omh-backend -g -a claude-code -y`
Codex: `npx skills add rlaope/oh-my-hermes --skill omh-backend -g -a codex -y`
Cursor: `npx skills add rlaope/oh-my-hermes --skill omh-backend -g -a cursor -y`
Gemini CLI: `npx skills add rlaope/oh-my-hermes --skill omh-backend -g -a gemini-cli -y`

## Description

[omh] Designing an API, server, or data-layer change: prepare server, API, and data-layer contracts, auth boundary, error paths, response shape, and schema/migration discipline, before implementation. Use when the user says: backend, back-end, back end, backend skill, server side, server-side, api design, api contract.

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

# Backend

This is an OMH `backend` workflow skill, projected for Agent Skills hosts (Claude Code, Codex, Cursor, opencode, OpenClaw, pi).

## Why This Exists

`backend` gives OMH a first-class server-side workflow so Hermes can prepare auth boundaries, error paths, response shapes, and migration order without becoming the hidden runtime that executes them.

## Do Not Use When

- The work is the database itself -- a slow query and the index that fixes it, DDL that locks a live table, N+1 queries, or when to partition or shard; use `omh-relational-db`, which owns the lock behaviour and rollback of each statement.
- The request is about web UI, layout, or a design system; use `omh-frontend`.
- The request is a security posture or threat review rather than a service design; use `omh-security-safety-review`.
- The request is to run or judge the verification of an already-built service; use `omh-verification-gate`.
- The request is a Rust-language change whose risk is compiler, ownership, or `unsafe` discipline; use `omh-rust`.
- The work is a batch or streaming job's rerun, backfill, duplicate rows, or a warehouse table's downstream readers; use `omh-data-pipelines`.

## Examples

Good example:

- Prompt: Design a REST API with a Postgres schema and migrations for the billing service.
- Expected behavior: Prepare backend_service_contract/v1, auth_boundary_map/v1, error_path_table/v1, response_shape_contract/v1, and schema_migration_plan/v1, then hand off with the per-stack reference named.
- Why: The request is server-side design across an endpoint surface and its storage, before any code exists.

Bad example:

- Prompt: The migration is written, so mark the schema as migrated and the API as live.
- Expected behavior: Mark migration application, integration runs, and deployment as not_observed and name the smallest observed proof for each.
- Why: A prepared migration plan is not an applied migration, and a contract is not a running service.

## Completion Checklist

The rest: https://github.com/rlaope/oh-my-hermes/blob/HEAD/agent-skills/omh-backend/SKILL.md