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.
67
Quality
80%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
View guide
Securityby
Passed
No findings from the security scan
Fix and improve this skill with Tessl
tessl review fix ./skills/ui-elements/SKILL.mdWhen 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
- Every list item should lead somewhere useful when domain relationships exist.
- Prefer connected flows: project -> session -> observation -> full detail.
- Empty states must explain what is missing and what unlocks data.
- Metrics must reflect real system state, not decorative counters.
- 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.
- Repository
- Gentleman-Programming/engram
- Commit
763a6ba
- 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.