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.
EnglishPR creation workflow for Engram following the issue-first enforcement system. Trigger: When creating a pull request, opening a PR, or preparing changes for review.
EnglishProduct and business-rule guardrails for Engram. Trigger: Any change that affects sync behavior, project controls, permissions, or memory semantics.
EnglishCultural and collaboration norms for Engram contributors and agents. Trigger: Starting substantial work, reviewing changes, or defining team conventions.
EnglishHTMX and templ interaction rules for the Engram dashboard. Trigger: Any change to htmx attributes, partial updates, forms, or server-rendered browser UI.
EnglishDocumentation alignment rules for Engram. Trigger: Any code or workflow change that affects user or contributor behavior.
EnglishAdapter boundary rules for plugin integrations. Trigger: Changes in plugin scripts/hooks for Claude, OpenCode, Gemini, or Codex.
EnglishDeep technical review protocol for Engram pull requests. Trigger: Reviewing any external or internal contribution before merge.
EnglishSpec-Driven Development workflow for Engram. Trigger: When user requests SDD or multi-phase implementation planning.
EnglishAPI contract guardrails for Engram server changes. Trigger: Any route, handler, payload, or status code modification.
EnglishTDD and coverage standards for Engram. Trigger: When implementing behavior changes in any package.
EnglishBubbletea/Lipgloss quality rules for Engram TUI. Trigger: Changes in model, update, view, navigation, or rendering.
EnglishCreation rules for Engram UI elements, pages, cards, metrics, and detail flows. Trigger: Adding or changing dashboard UI components or connected browsing flows.
EnglishVisual language rules for Engram surfaces. Trigger: Any dashboard styling, typography, spacing, or visual identity change.
EnglishUse when the user asks to create Trellis issues including "create a project", "create epics", "create features", "create tasks", "new project", "new epic", "new feature", "new task", "break down project into epics", "break down epic into features", "break down feature into tasks", "decompose project", "decompose epic", "decompose feature", or mentions creating any type of issue in Trellis.
EnglishKeep searchable long-term memory for coding agents in a local SQLite store and expose it through MCP when sessions keep forgetting prior decisions, conventions, and useful findings.
EnglishIncludes Engram Architecture Guardrails, Engram Branch PR, Engram Business Rules, and other workflows.
Supported by the Atlas install prompt. Skill-specific requirements vary.
Pack stats
What’s included
Engram 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.
Engram 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 review.
Engram Business Rules
Product and business-rule guardrails for Engram. Trigger: Any change that affects sync behavior, project controls, permissions, or memory semantics.
Engram Cultural Norms
Cultural and collaboration norms for Engram contributors and agents. Trigger: Starting substantial work, reviewing changes, or defining team conventions.
Engram Dashboard Htmx
HTMX and templ interaction rules for the Engram dashboard. Trigger: Any change to htmx attributes, partial updates, forms, or server-rendered browser UI.
Engram Docs Alignment
Documentation alignment rules for Engram. Trigger: Any code or workflow change that affects user or contributor behavior.
Engram Plugin Thin
Adapter boundary rules for plugin integrations. Trigger: Changes in plugin scripts/hooks for Claude, OpenCode, Gemini, or Codex.
Engram PR Review Deep
Deep technical review protocol for Engram pull requests. Trigger: Reviewing any external or internal contribution before merge.
Engram Sdd Flow
Spec-Driven Development workflow for Engram. Trigger: When user requests SDD or multi-phase implementation planning.
Engram Server API
API contract guardrails for Engram server changes. Trigger: Any route, handler, payload, or status code modification.
Engram Testing Coverage
TDD and coverage standards for Engram. Trigger: When implementing behavior changes in any package.
Engram Tui Quality
Bubbletea/Lipgloss quality rules for Engram TUI. Trigger: Changes in model, update, view, navigation, or rendering.
Engram UI Elements
Creation rules for Engram UI elements, pages, cards, metrics, and detail flows. Trigger: Adding or changing dashboard UI components or connected browsing flows.
Engram Visual Language
Visual language rules for Engram surfaces. Trigger: Any dashboard styling, typography, spacing, or visual identity change.
Issue Creation
Use when the user asks to create Trellis issues including "create a project", "create epics", "create features", "create tasks", "new project", "new epic", "new feature", "new task", "break down project into epics", "break down epic into features", "break down feature into tasks", "decompose project", "decompose epic", "decompose feature", or mentions creating any type of issue in Trellis.
Persist Reusable Coding Agent Memory Across Sessions with Engram
Keep searchable long-term memory for coding agents in a local SQLite store and expose it through MCP when sessions keep forgetting prior decisions, conventions, and useful findings.
Quick start
- Choose your skills. Select individual skills above, or choose the entire pack.
- Copy the install prompt. Use Copy install prompt above the list.
- Send it to your agent. Paste into your coding agent’s chat. Your agent reviews the source and guides the setup.
Try it with your agent
After installation, start with a request like:
Use the Engram Architecture Guardrails skill to help with my task.
Ask me for the context you need before getting started.Requirements & license
- A coding agent that can access your project files and install skills.
- Your agent checks each skill’s instructions, dependencies, and permissions during setup.
- Reported license for the skills shown: MIT. The author’s terms apply.