with one click
rushdb
rushdb contains 5 collected skills from rush-db, with repository-level occupation coverage and site-owned skill detail pages.
Skills in this repository
Model data in RushDB's property-centric LMPG graph. Use this skill when designing a schema, choosing label names, planning property structure, defining relationships, importing nested JSON data, or evolving an existing schema. Also use when the user asks how RushDB stores data, how relationships work, or how to structure records for a new use case.
Build RushDB queries, searches, filters, and aggregations. Use this skill whenever an agent needs to interact with RushDB data — listing records, filtering by properties, counting, summing, averaging, grouping by dimension, traversing relationships between record types, running semantic/vector search, or building any findRecords call. Also use when discovering what labels and properties exist in the database.
Use RushDB as a persistent, structured memory layer for AI agents. Use this skill whenever an agent needs to store session data, remember past decisions, recall prior context by meaning, build a knowledge graph that survives across conversations, associate memories via relationships, or replace a separate vector DB / key-value store with a single ACID-safe graph. Also use when the user says "remember this", "store that", or "what did we decide about X".
Design a tailored RushDB schema for any use case through guided conversation. Use this skill when a user is starting a new project, unsure what labels to define, asking "what records should I create", or wants a scaffold for a known domain (e-commerce, healthcare, SaaS, CRM, agent memory, etc.). Interviews the user, maps their domain to a starter schema of RECORD labels + properties + relationships, and outputs a ready-to-run bulkCreateRecords bootstrap payload.
Build faceted filter UIs on top of RushDB. Use this skill when generating code for filter sidebars, multi-select facets, range sliders, or any UI that lets users narrow a record set by property values. Covers the full flow: discover properties + types, enumerate distinct values, map each type to the right widget, and assemble the live where clause as filters change.