Architecture guardrails
Skill Gentleman-Programming/engram/skills/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.From its SKILL.md
npx -y skills add Gentleman-Programming/engram --skill architecture-guardrailsAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
What its file declares
Copied from the file, not written here
The file declares its own license as Apache-2.0. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.
SKILL.md
1.5 KB, as published. Nobody here has run it
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.