neo4j-labs

Brand identity guidelines for Neo4j Labs projects. Use when creating documentation, README files, presentations, diagrams, or marketing materials for Neo4j Labs projects. Defines visual identity, tone, messaging, and lifecycle badges that differentiate Labs from official Neo4j products while maintaining brand connection.

Ensure consistency with Neo4j brand guidelines, Needle design system, and Cypher code style conventions. Use when creating Neo4j documentation, diagrams, presentations, Cypher queries, code examples, or any content that should align with Neo4j's visual identity and coding standards. Reference https://neo4j.design for the Needle design system.

Generate Excalidraw JSON format diagrams for documentation, architecture diagrams, flowcharts, entity relationships, and visual explanations. Use when users request Excalidraw diagrams, .excalidraw files, visual diagrams for docs, architecture visualizations, flowcharts, or when converting ASCII art/placeholder diagrams to proper Excalidraw format.

Runs Cypher, inspects the schema / data model via `neo4j-cli query :schema`, manages Neo4j Aura, Neo4j connection (dbms) and embedding-provider credentials, manages local Neo4j Docker containers (create / list / get / start / stop / delete, including ephemeral runs that emit a .env for `query --env`), and installs the embedded self-skill or any curated catalog skill from neo4j-contrib/neo4j-skills into supported AI agents. Use when the user wants to execute or pipe Cypher, inspect/view/introspect the schema or generate a data model (labels, relationship types, properties) via `:schema`, embed text inline as a parameter, list/create/get/delete/provision/resize Aura instances or tenants, manage Aura Agents, manage Aura/dbms/embed credentials, run / start / stop a local Neo4j Docker container, install/remove/list/refresh agent skills (self or catalog), or self-update the neo4j-cli binary via `neo4j-cli update`. Skip for Cypher syntax, Neo4j drivers, Kubernetes, Neo4j Browser, or other databases.

Strict maintainability review — abstraction quality, file size, spaghetti growth. Use for a stellar code quality review, deep quality audit, or harsh maintainability review.

Fixture CLI for golden-file tests. Trigger when render code changes.

Use when working with Neo4j command-line tools including neo4j-admin, cypher-shell, aura-cli, and neo4j-mcp

Use when upgrading Neo4j drivers to new major versions

Comprehensive guide for developing a Terraform provider in Go against the Neo4j Aura API, using the modern terraform-plugin-framework. Use this skill whenever the user is writing, reviewing, structuring, testing, or debugging any part of a Terraform provider codebase — including resource/data source definitions, schema design, CRUD operations, error handling, import support, state upgrades, acceptance testing, and documentation. Trigger on any mention of "terraform provider", "plugin framework", "resource schema", "data source", "acceptance test", "tfproviderlint", "terraform import", or "state upgrade" in the context of provider development. Also trigger when reviewing Go code that imports terraform-plugin-framework packages.