/docs-alignment
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.
- Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
- You can call itInvoke it directly when you want it.
- Slash command
/docs-alignment
Context 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.
SKILL.md
docs-alignment.SKILL.mdname: 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"
When to Use
Use this skill when:
- Changing APIs, setup flows, or plugin behavior
- Updating CLI commands or examples
- Writing contributor guidance
---
Alignment Rules
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.
---
Verification
- [ ] Endpoint names match server routes
- [ ] Script names match repository paths
- [ ] Command examples execute as documented
- [ ] Cross-agent notes are still accurate
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
Other skills on gentleman-programming-engram.
- /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.
Open skill - /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.
Open skill - /architecture-guardrails
Architecture guardrails for Engram across local store, cloud sync, dashboard, and plugins. Trigger: Any change that affects system boundaries, ownership, state flow, or cross-package responsibilities.
Open skill - /backlog-triage
Backlog triage protocol for Engram: audit open issues and PRs, classify each item, infer maintainer ideology from comments, and produce an actionable disposition report. Trigger: Auditing open issues or PRs, triaging the backlog, reviewing contributor submissions as a
Open skill - /branch-pr
PR creation workflow for Engram following the issue-first enforcement system. Trigger: When creating a pull request, opening a PR, or preparing changes for review.
Open skill - /business-rules
Product and business-rule guardrails for Engram. Trigger: Any change that affects sync behavior, project controls, permissions, or memory semantics.
Open skill

