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.
Visual language rules for Engram surfaces. Trigger: Any dashboard styling, typography, spacing, or visual identity change.
$ npx -y skills add Gentleman-Programming/engram --skill visual-language --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
/visual-languageContext preview
The summary Claude sees to decide when to auto-load this skill.
Visual language rules for Engram surfaces. Trigger: Any dashboard styling, typography, spacing, or visual identity change.
name: engram-visual-language description: > Visual language rules for Engram surfaces. Trigger: Any dashboard styling, typography, spacing, or visual identity change. license: Apache-2.0 metadata: author: gentleman-programming version: "1.0"
Use this skill when:
---
1. The dashboard must feel like Engram, not a generic SaaS admin. 2. Prefer strong hierarchy, fewer containers, and clearer breathing room. 3. Use the TUI-inspired palette and mono/display accents intentionally. 4. Format machine timestamps and raw identifiers into human-scannable UI. 5. Decorative framing must never make content harder to read.
---
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.