# Engram Server API

> Engram Server API is an Agent Skill for development published in the Gentleman-Programming/engram repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.

API contract guardrails for Engram server changes. Trigger: Any route, handler, payload, or status code modification.

- Skill name: `engram-server-api`
- Category: [Development](https://www.openparable.com/skill/development/1)
- Source: https://github.com/Gentleman-Programming/engram/blob/HEAD/skills/server-api/SKILL.md
- Repository: Gentleman-Programming/engram (5,463 GitHub stars when collected)

## SKILL.md

## When to Use

Use this skill when:
- Adding or changing HTTP routes
- Updating handler request/response schemas
- Modifying status code behavior

---

## Contract Rules

1. Every new/changed endpoint must have tests.
2. Cover both success and error paths.
3. Keep scripts and docs aligned with real handlers.
4. Do not reference non-existent endpoints in plugins/hooks.

---

## Required Validation

- Handler-level tests for parsing/validation errors
- E2E tests for route behavior and response body
- Regression test for every bugfix related to API contracts

---

## Docs Rules

If payload or route changes, update docs in the same PR.

---

Source: https://www.openparable.com/skill/development/engram-server-api (OpenParable). Cite the canonical URL above.
