Skip to content
Agentmart
Submit a tool

engram-ui-elements

Creation rules for Engram UI elements, pages, cards, metrics, and detail flows.

Skill by gentleman-programming

IndexedApache-2.0★ 7,588
Write a review

Install

Works with Claude Code, Claude apps, Codex, Cursor, Gemini CLI, GitHub Copilot, VS Code, OpenCode, Goose, Windsurf. Read the repository before you give any tool access to your data.

npx agentmarket install skill/gentleman-programming-engram-ui-elements

Asks which of your tools to add it to (Claude Code, Codex, Cursor, VS Code, Windsurf, Gemini CLI, Claude Desktop) and shows the change first. See https://agentmart.dev/cli.

Get the weekly diff

The weekly diff: one email a week with new agent tools, notable updates and grade changes, plus security alerts for tools you follow. Double opt-in, one-click unsubscribe.

We use your email only for this newsletter. Privacy

About

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

Use cases: design, data

No reviews yet. Installed it? Reviews come from verified installers only. How reviews work

Permissions

What this skill can do and what it asks for, from its SKILL.md. Checked Oct 25, 2026.

Tools
No tools found
Secrets
None asked for
Install scripts
None found

Network hosts it talks to 1

  • codeload.github.com · found in install command

Files it touches

  • ~/.claude/skills/engram-ui-elements

What's inside

Skill name
engram-ui-elements
Description
Creation rules for Engram UI elements, pages, cards, metrics, and detail flows. Trigger: Adding or changing dashboard UI components or connected browsing flows.
License
Apache-2.0
Metadata
author: gentleman-programming · version: 1.0
Instructions
27 lines in SKILL.md · view on GitHub

Agent Skills spec issues

  • name: "engram-ui-elements" does not match folder "ui-elements"

Files (1)

  • SKILL.md

SKILL.md (first lines)

## 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.

From Gentleman-Programming/engram, Apache-2.0.

More from Gentleman-Programming/engram

Signals

Stars
7,588
Forks
791
Open issues
73
Last commit (this folder)
Mar 7, 2026 (7 months ago)
Last release
Oct 23, 2026 (5 days ago)

From GitHub (fetched Oct 24, 2026).

Details

Version
1.0
License
Apache-2.0
First seen
Oct 24, 2026
Last checked
Oct 24, 2026

More from gentleman-programming

Cite this page

engram-ui-elements skill. Agent Mart. https://agentmart.dev/skills/gentleman-programming-engram-ui-elements (last updated 2026-10-24)