memora-frontend

Create Memora frontend UIs using the Memora Design System and API contracts.

1|Updated Feb 8, 2026
One-click install
npx skills add https://github.com/aiob3/llm-readable-kit --skill memora-frontend
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: memora-frontend
Source: https://github.com/aiob3/llm-readable-kit/tree/main/.claude/plugins/memora-frontend/skills/memora-frontend
Command: npx skills add https://github.com/aiob3/llm-readable-kit --skill memora-frontend

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Reduces the time and friction to build consistent Memora frontends by applying a unified design system and standard API contracts across graph visualizations, memory CRUD forms, and dashboards.

Core Features & Use Cases

  • Uniform Memora Design System usage for all frontend components (graphs, tables, forms, panels).
  • UI patterns for knowledge graphs, memory management, and views that call /api/graph, /api/memories, and /api/views.
  • Quick adaptation to local SQLite (memoria.db) with optional Postgres canonical schemas via API endpoints.

Quick Start

Implement a Memora frontend page that renders the knowledge graph from /api/graph and lists memories from /api/memories using the Memora Design System.

Frequently Asked Questions about memora-frontend

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I build a frontend dashboard for a knowledge graph visualization?

A knowledge graph visualization dashboard applies a unified design system to render graph data from /api/graph endpoints, enforcing API-contract adherence and dark-mode styling for consistent UI components across panels.

What is the best way to create memory CRUD forms that call /api/memories?

Memory CRUD forms apply standardized UI patterns and design system components to interact with /api/memories endpoints, ensuring data conforms to the local SQLite backend schema by default for consistent management.

Does the Memora frontend design system work with a Postgres database schema?

Yes, the design system supports optional Postgres canonical schema integration via pg, adapting UI patterns for dashboards and views while defaulting to the local SQLite database backend for local development.

Can I use this design system for dashboards querying /api/views?

Yes, the design system provides uniform UI component patterns specifically designed to handle dashboards querying /api/views, rendering tables and panels while maintaining strict API-contract adherence.

Why enforce API-contract adherence when building Memora frontend UIs?

Enforcing API-contract adherence ensures graph visualizations, memory forms, and dashboards reliably communicate with backend endpoints, reducing integration friction and preventing data mapping errors across the frontend.