Menu
Use when the user adds nodes, relationships, constraints, or indexes to the Neo4j knowledge graph, or edits any *.cypher file.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
| name | neo4j-schema |
| description | Use when the user adds nodes, relationships, constraints, or indexes to the Neo4j knowledge graph, or edits any *.cypher file. |
Sources: neo4j/init-schema.cypher, docs/health-dataspace-graph-schema.md,
.claude/rules/code-style.md (Cypher section).
neo4j/init-schema.cypher for existing constraints/indexes, and the target
layer's section in docs/health-dataspace-graph-schema.md.PascalCase, relationships UPPER_SNAKE_CASE, properties camelCase.
Always MERGE (never bare CREATE); constraints/indexes always IF NOT EXISTS
— the schema must stay idempotent and safe to re-run.neo4j/insert-synthetic-schema-data.cypher if needed.neo4j/init-schema.cypher mirrored in the markdown schema doc.ui/src/lib/graph-constants.ts LABEL_LAYER (see graph-visualisation skill).Use when the user adds or modifies a Next.js API route under ui/src/app/api/.
Use when the user works on EHDS articles, DSP protocol, DCP credentials, ODRL policies, or the audit trail.
Use when the user works on the force-directed graph explorer, layer colours, persona views, or node filtering.
Use when the user works on authentication, Keycloak configuration, OIDC, roles, or JWT claims.
Use when the user adds E2E tests, Playwright specs, or journey coverage.
Use when the user works on demo personas, localStorage persistence, or GitHub Pages static-export behaviour.