/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.
$ npx -y skills add Gentleman-Programming/engram --skill dashboard-htmx --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
/dashboard-htmx
Context preview
The summary Claude sees to decide when to auto-load this skill.
HTMX and templ interaction rules for the Engram dashboard. Trigger: Any change to htmx attributes, partial updates, forms, or server-rendered browser UI.
SKILL.md
dashboard-htmx.SKILL.mdname: engram-dashboard-htmx description: > HTMX and templ interaction rules for the Engram dashboard. Trigger: Any change to htmx attributes, partial updates, forms, or server-rendered browser UI. license: Apache-2.0 metadata: author: gentleman-programming version: "1.0"
When to Use
Use this skill when:
- Adding htmx partial loading or filter controls
- Wiring forms or toggles in the dashboard
- Changing browser/search interactions
---
HTMX Rules
1. Server-rendered HTML is the product; htmx enhances it, it does not replace it. 2. Prefer simple `hx-get` and `hx-include` over custom client-side state. 3. Filters must preserve the active state users would expect across interactions. 4. Forms that mutate system state must still work as normal HTTP posts. 5. Partial endpoints return meaningful HTML on their own, not fragments that depend on hidden JS assumptions.
---
Interaction Rules
- Search and filter controls must compose cleanly.
- Toggle actions must visibly reflect the resulting server state.
- Connected navigation should keep URLs meaningful and shareable.
- Use htmx for speed, not to hide business logic in the browser.
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
Other skills on gentleman-programming-engram.
- /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.
Open 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.
Open 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.
Open 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 disposition report. Trigger: Auditing open issues or PRs, triaging the backlog, reviewing contributor submissions as a
Open 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 review.
Open skill - /business-rules
Product and business-rule guardrails for Engram. Trigger: Any change that affects sync behavior, project controls, permissions, or memory semantics.
Open skill