ladybugdb
Expert guide for LadybugDB — an embedded, in-process property graph database using openCypher. Use this skill whenever the user is working with LadybugDB, writing Cypher queries for LadybugDB, using the `lbug` CLI, importing `real_ladybug` in Python, using `@ladybugdb/core` in Node.js, or building any application with LadybugDB. Also triggers when the user asks about LadybugDB schema design, graph algorithms (PageRank, Louvain), HNSW vector search, full-text search, ATTACH to PostgreSQL/DuckDB/Delta Lake, LLM embeddings with CREATE_EMBEDDING, or bulk data import/export with COPY FROM/TO. Use even if the user just says 'ladybug graph db' or pastes a .lbug file path.
What this skill does
# LadybugDB LadybugDB is an **embedded, in-process property graph database** — no server process required. It uses the openCypher query language with a **required, predefined schema** (unlike Neo4j), columnar disk-based storage, vectorized query execution, and serializable ACID transactions. ## Quick orientation - **Schema-first**: you must create node/rel tables before inserting data - **One primary key per node table** — automatically indexed, unique, non-null - **Walk semantics**: repeated edges allowed in MATCH (unlike Neo4j's trail semantics) - **One write transaction at a time**; multiple concurrent reads are fine - **In-memory mode**: use `":memory:"` as the database path for ephemeral databases ## Installation ```bash # CLI curl -s https://install.ladybugdb.com | bash # Linux brew install ladybug # macOS # Python pip install real_ladybug # Node.js npm install @ladybugdb/core ``` ## CLI basics ```bash lbug mydb.lbug # open/create on-disk DB lbug # in-memory (ephemeral) lbug mydb.lbug < schema.cypher # batch mode ``` Key shell commands: `:schema` (show tables), `:help`, `:quit`, `:mode [json|csv|markdown|...]` ## Reference files Load only the sections you need: | File | Contents | |------|----------| | `references/cypher-reference.md` | DDL, DML, MATCH queries, transactions, macros, LadybugDB vs Neo4j differences | | `references/python.md` | Python (`real_ladybug`) — connection, query, DataFrame, transactions | | `references/nodejs.md` | Node.js (`@ladybugdb/core`) — connection, query, streaming, transactions | | `references/java.md` | Java — Maven setup, connection, query, transactions | | `references/rust.md` | Rust — Cargo setup, connection, query, Value types | | `references/go.md` | Go — module setup, connection, query, transactions | | `references/swift.md` | Swift — SPM setup, connection, query, async/await | | `references/import.md` | COPY FROM, LOAD FROM, DataFrame import, cloud storage, performance tips | | `references/export.md` | COPY TO, DataFrame export (pandas/polars/arrow), DuckDB export | | `references/graph-algorithms.md` | PageRank, Louvain, WCC, SCC, K-Core, shortest paths — PROJECT_GRAPH | | `references/vector-search.md` | HNSW index, CREATE/QUERY/DROP_VECTOR_INDEX, RAG pattern | | `references/full-text-search.md` | BM25, CREATE/QUERY/DROP_FTS_INDEX, stemmers | | `references/llm-embeddings.md` | CREATE_EMBEDDING — OpenAI, Ollama, Google, Bedrock, Voyage AI | | `references/attach.md` | ATTACH/DETACH — PostgreSQL, DuckDB, SQLite, Delta Lake, Iceberg, Neo4j | | `references/cli.md` | `lbug` shell flags, commands, output modes, batch/scripting mode | | `references/explorer.md` | Ladybug Explorer Docker GUI — launch, env vars, volume mount | ## Common task routing | Task | Read | |------|------| | Schema design, Cypher queries, differences from Neo4j | `cypher-reference.md` | | Python integration | `python.md` | | Node.js / TypeScript integration | `nodejs.md` | | Java integration | `java.md` | | Rust integration | `rust.md` | | Go integration | `go.md` | | Swift / iOS / macOS integration | `swift.md` | | Bulk import — COPY FROM, LOAD FROM, DataFrames, cloud storage | `import.md` | | Bulk export — COPY TO, DataFrame export, DuckDB | `export.md` | | PageRank, Louvain, WCC, SCC, K-Core, shortest paths | `graph-algorithms.md` | | HNSW vector similarity search, RAG | `vector-search.md` | | Full-text search (BM25) | `full-text-search.md` | | LLM embeddings (OpenAI, Ollama, Bedrock…) | `llm-embeddings.md` | | ATTACH to PostgreSQL, DuckDB, Delta Lake, Neo4j | `attach.md` | | CLI shell, batch scripts | `cli.md` | | Ladybug Explorer browser GUI (Docker) | `explorer.md` | ## Key gotchas 1. **`SET n.prop = NULL`** to remove a property (not `REMOVE`) 2. **`label(n)`** not `labels(n)`; **`id(n)`** not `elementId(n)` 3. **`UNWIND`** instead of `FOREACH` 4. List functions use `list_` prefix: `list_concat`, `list_sort`, etc. 5. Variable-length paths **must** have an upper bound (default 30): `[:Follows*1..5]` 6. `LOAD FROM` (not `LOAD CSV FROM`) — supports CSV, Parquet, JSON, DataFrames 7. No manual index creation — primary key index is automatic; use FTS/vector extensions for search
Related in Design
contribute
IncludedLocal-only OSS contribution command center. Auto-refreshes the user's in-flight PR and issue state on invoke so conversations start with full context — no need to brief Claude on what's in flight. Helps the user find issues to contribute to on GitHub, builds per-repo dossiers of what each upstream expects (CLA, DCO, branch convention, AI policy, draft-first, review bots, issue templates), runs deterministic gates before any external action so AI-assisted contributions don't reach maintainers as slop. State is markdown-only: candidate files at ~/.contribute-system/candidates/, repo dossiers at ~/.contribute-system/research/, append-only event log at ~/.contribute-system/log.jsonl. No database, no cloud calls. Use when the user asks about their PRs / issues / contributions, wants to find new work to take on, claim an issue, build/refresh a repo's dossier, or draft a Design Issue or PR. Trigger with "/contribute", "what's my PR status", "find a contribution", "claim issue X", "draft a Design Issue for Y", "refresh dossier for Z".
architectural-analysis
IncludedUser-triggered deep architectural analysis of a codebase or scoped subtree across eight modes — information architecture, data flow, integration points, UI surfaces, interaction patterns, data model, control flow, and failure modes. This skill should be used when the user asks to "diagram this codebase," "map the architecture," "show the data flow," "give me an ERD," "trace control flow," "find the integration points," "verify the layout pattern," "audit the UX architecture," or any similar request whose primary deliverable is mermaid diagrams plus cited reports under docs/architecture/. Dispatches haiku/sonnet sub-agents in parallel for per-mode exploration, then verifies every citation mechanically before any node lands in a diagram. Not for one-off prose explanations of code (use code-explanation) or for high-level system design from scratch (use system-design).
mcp
IncludedModel Context Protocol (MCP) server development and tool management. Languages: Python, TypeScript. Capabilities: build MCP servers, integrate external APIs, discover/execute MCP tools, manage multi-server configs, design agent-centric tools. Actions: create, build, integrate, discover, execute, configure MCP servers/tools. Keywords: MCP, Model Context Protocol, MCP server, MCP tool, stdio transport, SSE transport, tool discovery, resource provider, prompt template, external API integration, Gemini CLI MCP, Claude MCP, agent tools, tool execution, server config. Use when: building MCP servers, integrating external APIs as MCP tools, discovering available MCP tools, executing MCP capabilities, configuring multi-server setups, designing tools for AI agents.
react-native-skia
IncludedDesign, build, debug, and optimise high-polish animated graphics in React Native or Expo using @shopify/react-native-skia, Reanimated, and Gesture Handler. Use when the user wants canvas-driven UI, shaders, paths, rich text, image filters, sprite fields, Skottie, video frames, snapshots, web CanvasKit setup, or performance tuning for custom motion-heavy elements such as loaders, hero art, cards, charts, progress indicators, particle systems, or gesture-driven surfaces. Also use when the user asks for fluid, glow, glass, blob, parallax, 60fps/120fps, or GPU-friendly animated effects in React Native, even if they do not explicitly say "Skia". Do not use for ordinary form/layout work with standard views.
plaid
IncludedProduct Led AI Development — guides founders from idea to launched product. Six capabilities: Idea (discover a product idea), Validate (pressure-test the idea against fatal flaws, problem reality, competition, and 2-week MVP feasibility), Plan (vision intake + document generation), Design (translate image references into a design.md spec), Launch (go-to-market strategy), and Build (roadmap execution). Use when someone says "PLAID", "plaid idea", "help me find an idea", "product idea", "idea from my business", "idea from my expertise", "plaid validate", "validate my idea", "pressure-test", "is this idea good", "find fatal flaws", "validate the problem", "plan a product", "define my vision", "generate a PRD", "product strategy", "plaid design", "design from image", "translate image to design", "create design.md", "extract design tokens", "plaid launch", "go-to-market", "launch plan", "GTM strategy", "launch playbook", "plaid build", "build the app", "start building", or "execute the roadmap".
nextjs-framer-motion-animations
IncludedAdds production-safe Motion for React or Framer Motion animations to Next.js apps, including reveal, hover and tap micro-interactions, whileInView, stagger, AnimatePresence, layout and layoutId transitions, reorder, scroll-linked UI, and lightweight route-content transitions. Use when the user asks to add, refactor, or debug Motion or Framer Motion in App Router or Pages Router codebases, especially around server/client boundaries, reduced motion, LazyMotion, bundle size, hydration, or route transitions. Avoid for GSAP-style timelines, WebGL or 3D scenes, heavy scroll storytelling, or CSS-only effects unless Motion is explicitly requested.