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.
Cultural and collaboration norms for Engram contributors and agents. Trigger: Starting substantial work, reviewing changes, or defining team conventions.
$ npx -y skills add Gentleman-Programming/engram --skill cultural-norms --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
/cultural-normsContext preview
The summary Claude sees to decide when to auto-load this skill.
Cultural and collaboration norms for Engram contributors and agents. Trigger: Starting substantial work, reviewing changes, or defining team conventions.
name: engram-cultural-norms description: > Cultural and collaboration norms for Engram contributors and agents. Trigger: Starting substantial work, reviewing changes, or defining team conventions. license: Apache-2.0 metadata: author: gentleman-programming version: "1.0"
Use this skill when:
---
1. Product coherence beats local cleverness. 2. Every visible feature should feel connected to the full Engram experience. 3. Avoid generic enterprise UI/architecture drift. 4. Prefer explicit decisions and documented rules over tribal knowledge. 5. Quality means behavior, naming, tests, docs, and UX all line up.
---
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.