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.
Documentation alignment rules for Engram. Trigger: Any code or workflow change that affects user or contributor behavior.
$ npx -y skills add Gentleman-Programming/engram --skill docs-alignment --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
/docs-alignmentContext preview
The summary Claude sees to decide when to auto-load this skill.
Documentation alignment rules for Engram. Trigger: Any code or workflow change that affects user or contributor behavior.
name: engram-docs-alignment description: > Documentation alignment rules for Engram. Trigger: Any code or workflow change that affects user or contributor behavior. license: Apache-2.0 metadata: author: gentleman-programming version: "1.0"
Use this skill when:
---
1. Docs must describe current behavior, not intended behavior. 2. Update docs in the same PR as the code change. 3. Validate examples before publishing. 4. Remove references to deprecated files, endpoints, or scripts.
---
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.