neo4j-data-models
Neo4j Data Models
When to Use
Use this skill when designing or extending a Neo4j graph data model. Covers naming conventions, node/relationship design, property management, fraud detection domain models, and modeling best practices.
Design Process
Start with specific business questions before designing the model. Follow a three-phase cycle:
- Conceptualize the structure (nodes, relationships, properties)
- Design queries that answer the business questions
- Validate against real data and optimize
Every node requires a unique identifier or property combination. Prioritize the model around the application's most frequent or critical queries.
Naming Conventions
Node Labels — CapitalCase
More from michaelkeevildown/claude-agents-skills
neo4j-cypher
Neo4j Cypher query language reference — patterns, performance, fraud-domain queries, and Neo4j 5+ features.
13neo4j-driver-js
Neo4j JavaScript driver 6.x — connection setup, session management, impersonation security, transaction functions, type handling, and result-to-UI data mapping.
8shadcn-ui
shadcn/ui component library — installation, usage patterns, theming, form integration, and accessibility.
7git-workflow
Git workflow conventions — branching strategy, commit messages, PR workflow, and rebase vs merge.
7fastapi
FastAPI — route definitions, dependency injection, Pydantic models, middleware, and async patterns.
6agent-teams
Agent Teams workflow — parallel multi-agent development with stack-aware coordination (build-first for frontend, TDD for Python/Rust), feature doc lifecycle, file ownership, and quality gates.
6