engram-server-api

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

Safety Notice

This listing is imported from skills.sh public index metadata. Review upstream SKILL.md and repository scripts before running.

Copy this and send it to your AI assistant to learn

Install skill "engram-server-api" with this command: npx skills add gentleman-programming/engram/gentleman-programming-engram-engram-server-api

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 Transparency

This detail page is rendered from real SKILL.md content. Trust labels are metadata-based hints, not a safety guarantee.

Related Skills

Related by shared tags or category signals.

Coding

engram-memory-protocol

No summary provided by upstream source.

Repository SourceNeeds Review
Coding

gentleman-bubbletea

No summary provided by upstream source.

Repository SourceNeeds Review
Coding

engram-testing-coverage

No summary provided by upstream source.

Repository SourceNeeds Review