CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

68

Quality

81%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

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.
Repository
Gentleman-Programming/engram
Last updated
First committed

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.