engram-ui-elements

SkillMonitoring & ops

Gives your agent rules for building dashboard pages, cards, and metrics in the Engram project.

Then ask your AI: use the engram-ui-elements skill

Details

Instructions available. Your AI can read the instructions. Execution depends on the setup they require.

Add it as a step in a pipeline you build on Ahel, or connect Ahel to Claude, ChatGPT, Cursor, Claude Code or Codex and ask your AI to use it.

About this skill

Creation rules for Engram UI elements, pages, cards, metrics, and detail flows. Trigger: Adding or changing dashboard UI components or connected browsing flows.

What this skill tells your AI

The instructions your AI receives, as published by gentleman-programming/engram in skills/ui-elements/SKILL.md and read by Ahel’s review.

When to Use

Use this skill when:

  • Adding a new page or partial to the dashboard
  • Creating cards, metrics, tables, lists, or detail views
  • Designing connected navigation between related entities

UX Rules

  1. Every list item should lead somewhere useful when domain relationships exist.
  2. Prefer connected flows: project -> session -> observation -> full detail.
  3. Empty states must explain what is missing and what unlocks data.
  4. Metrics must reflect real system state, not decorative counters.
  5. Detail pages should show metadata, content, and the next relevant links.

Composition Rules

  • Use metrics for orientation, not for replacing core content.
  • Use cards for browsable entities and tables for dense comparative admin data.
  • Avoid nested framed boxes unless they communicate a hierarchy the user needs.
  • Keep action controls close to the entity they affect.

Signals

GitHub stars
7k
Forks
733
Last commit
Oct 2026
Advanced
Item type
skill
Key
engram-ui-elements
Source
github.com/gentleman-programming/engram