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.
Development
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.
Install
$ npx -y skills add Gentleman-Programming/engram --skill architecture-guardrails --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
/architecture-guardrails
Context preview
The summary Claude sees to decide when to auto-load this skill.
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.
SKILL.md
architecture-guardrails.SKILL.mdname: engram-architecture-guardrails
description: >
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.
license: Apache-2.0
metadata:
author: gentleman-programming
version: "1.0"
When to Use
Use this skill when:
- Adding a new subsystem or major package
- Moving responsibilities between local store, cloud, dashboard, or plugins
- Changing sync flow, source-of-truth rules, or persistence boundaries
---
Core Guardrails
1. Local SQLite is the source of truth; cloud is replication and shared access. 2. Keep plugin/adaptor layers thin; real behavior belongs in Go packages. 3. Prefer explicit boundaries: store, cloudstore, server, dashboard, autosync. 4. New features must fit the existing local-first mental model before they fit the UI. 5. Do not hide cross-system coupling inside helpers or templates.
---
Decision Rules
- Local-only concern -> `internal/store`
- Cloud materialization or org-wide control -> `internal/cloud/cloudstore`
- HTTP contract or enforcement -> `internal/cloud/cloudserver`
- Browser rendering and UX -> `internal/cloud/dashboard`
- Background orchestration -> `internal/cloud/autosync`
---
Validation
- Add regression tests for every boundary change.
- Verify local, remote, and dashboard behavior still tell the same product story.
- If the change touches sync, test both push and pull paths.
Read more
name: engram-architecture-guardrails description: > 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. license: Apache-2.0 metadata: author: gentleman-programming version: "1.0"
When to Use
Use this skill when:
- Adding a new subsystem or major package
- Moving responsibilities between local store, cloud, dashboard, or plugins
- Changing sync flow, source-of-truth rules, or persistence boundaries
---
Core Guardrails
1. Local SQLite is the source of truth; cloud is replication and shared access. 2. Keep plugin/adaptor layers thin; real behavior belongs in Go packages. 3. Prefer explicit boundaries: store, cloudstore, server, dashboard, autosync. 4. New features must fit the existing local-first mental model before they fit the UI. 5. Do not hide cross-system coupling inside helpers or templates.
---
Decision Rules
- Local-only concern -> `internal/store`
- Cloud materialization or org-wide control -> `internal/cloud/cloudstore`
- HTTP contract or enforcement -> `internal/cloud/cloudserver`
- Browser rendering and UX -> `internal/cloud/dashboard`
- Background orchestration -> `internal/cloud/autosync`
---
Validation
- Add regression tests for every boundary change.
- Verify local, remote, and dashboard behavior still tell the same product story.
- If the change touches sync, test both push and pull paths.
Ships withgentleman-programming-engram
Persistent memory system for AI coding agents. Agent-agnostic Go binary with SQLite + FTS5, MCP server, HTTP API, CLI, and TUI.
Get the whole plugin
Stats
6,585
Stars
681
Forks
Active
Maintenance
Go
Language
MIT
License
18h ago
Last commit
7mo ago
Created
Repo: Gentleman-Programming/engram
Other skills on gentleman-programming-engram.
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…
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…
Skill
business-rules
Product and business-rule guardrails for Engram. Trigger: Any change that affects sync behavior, project controls, permissions, or memory semantics.
Skill
commit-hygiene
Commit and branch naming standards for Engram contributors, enforced by GitHub rulesets. Trigger: Any commit creation, review, or branch cleanup.
Skill
cultural-norms
Cultural and collaboration norms for Engram contributors and agents. Trigger: Starting substantial work, reviewing changes, or defining team conventions.