memory
ALWAYS ACTIVE — Persistent memory protocol. You MUST save decisions, conventions, bugs, and discoveries to engram proactively. Do NOT wait for the user to ask.
API contract guardrails for Engram server changes. Trigger: Any route, handler, payload, or status code modification.
$ npx -y skills add Gentleman-Programming/engram --skill server-api --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
/server-apiContext preview
The summary Claude sees to decide when to auto-load this skill.
API contract guardrails for Engram server changes. Trigger: Any route, handler, payload, or status code modification.
name: engram-server-api description: > API contract guardrails for Engram server changes. Trigger: Any route, handler, payload, or status code modification. license: Apache-2.0 metadata: author: gentleman-programming version: "1.0"
Use this skill when:
---
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.
---
---
If payload or route changes, update docs in the same PR.
Persistent memory system for AI coding agents. Agent-agnostic Go binary with SQLite + FTS5, MCP server, HTTP API, CLI, and TUI.
Repo: Gentleman-Programming/engram
ALWAYS ACTIVE — Persistent memory protocol. You MUST save decisions, conventions, bugs, and discoveries to engram proactively. Do NOT wait for the user to ask.
Architecture guardrails for Engram across local store, cloud sync, dashboard, and plugins. Trigger: Any change that affects system boundaries, ownership, state…
Backlog triage protocol for Engram: audit open issues and PRs, classify each item, infer maintainer ideology from comments, and produce an actionable…
PR creation workflow for Engram following the issue-first enforcement system. Trigger: When creating a pull request, opening a PR, or preparing changes for…
Product and business-rule guardrails for Engram. Trigger: Any change that affects sync behavior, project controls, permissions, or memory semantics.
Commit and branch naming standards for Engram contributors, enforced by GitHub rulesets. Trigger: Any commit creation, review, or branch cleanup.