gentleman-programming/engram-architecture-guardrails
skills/architecture-guardrails/SKILL.md
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 --global
skillsauthnpx skillsauth add gentleman-programming/engram engram-architecture-guardrailsInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 25, 2026, 11:49 AM13.8s1 file scanned
SKILL.md
- name:
- engram-architecture-guardrails
- description:
- >
- and plugins. Trigger:
- Any change that affects system boundaries, ownership,
- license:
- Apache-2.0
- 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
- Local SQLite is the source of truth; cloud is replication and shared access.
- Keep plugin/adaptor layers thin; real behavior belongs in Go packages.
- Prefer explicit boundaries: store, cloudstore, server, dashboard, autosync.
- New features must fit the existing local-first mental model before they fit the UI.
- 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.
Related Skills
gentleman-programming/engram-memory
testing
VerifiedTrustedCommunity
ALWAYS ACTIVE — Persistent memory protocol. You MUST save decisions, conventions, bugs, and discoveries to engram proactively. Do NOT wait for the user to ask.
3,507SKILL.mdUpdated Apr 25, 2026
gentleman-programming/engram-visual-language
testing
VerifiedTrustedCommunity
Visual language rules for Engram surfaces. Trigger: Any dashboard styling, typography, spacing, or visual identity change.
2,810SKILL.mdUpdated Apr 25, 2026
gentleman-programming/engram-ui-elements
data-ai
VerifiedTrustedCommunity
Creation rules for Engram UI elements, pages, cards, metrics, and detail flows. Trigger: Adding or changing dashboard UI components or connected browsing flows.
2,810SKILL.mdUpdated Apr 25, 2026
gentleman-programming/engram-tui-quality
testing
VerifiedTrustedCommunity
Bubbletea/Lipgloss quality rules for Engram TUI. Trigger: Changes in model, update, view, navigation, or rendering.
2,810SKILL.mdUpdated Apr 25, 2026