arango-solutions/arango-sparql-py
Cursor rule Cursor
Always-on project identity and hard guardrails for arango-sparql-py.
Python-native SPARQL 1.1 to AQL transpiler and microservice for ArangoDB
arango-solutions/arango-sparql-py
Cursor rule Cursor
Always-on project identity and hard guardrails for arango-sparql-py.
arango-solutions/arango-sparql-py
Cursor rule Cursor
Backend Python conventions — FastAPI service, rdflib parsing, AQL builder, OWL schema mapping.
arango-solutions/arango-sparql-py
Cursor rule Cursor
Testing rules — pyoxigraph as ground truth, W3C DAWG harness, golden tests, eval harness.
arango-solutions/arango-sparql-py
Cursor rule Cursor
NL→SPARQL pipeline rules — Turtle prompts, providers, fewshot, tenant guardrails.
arango-solutions/arango-sparql-py
Cursor rule Cursor
Frontend rules — Vite + React + TS + CodeMirror SPARQL + Cytoscape RDF visualization.
arango-solutions/arango-sparql-py
Cursor rule Cursor
Production-ready mandate - never simplify away completeness in error handling, edge cases, security, tests, observability, or config.
arango-solutions/arango-sparql-py
Cursor rule Cursor
Small verifiable steps over big-bang changes - each increment must compile, pass tests, and be functional.
arango-solutions/arango-sparql-py
Cursor rule Cursor
Everything has a place - enforce file size limits, directory conventions, and module cohesion.
arango-solutions/arango-sparql-py
Cursor rule Cursor
Match the codebase - search for existing patterns, utilities, and conventions before writing new code.
arango-solutions/arango-sparql-py
Cursor rule Cursor
When unsure, ask the user - never silently guess on ambiguous requirements, architecture, or scope.
arango-solutions/arango-sparql-py
Cursor rule Cursor
Every code change deserves a test change - new functions get tests, bug fixes get regression tests.
arango-solutions/arango-sparql-py
Cursor rule Cursor
Enforces single-page, context-centric UI patterns for the object-centric workspace.
arango-solutions/arango-sparql-py
Cursor rule Cursor
If you didn't run it, you didn't ship it - always build, test, and exercise changed code before claiming done.
arango-solutions/arango-sparql-py
Cursor rule Cursor
Unused code is a missing feature, not garbage - wire it in instead of deleting to silence linters.