Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx agentmods add rules/arango-solutions/arango-sparql-py/ui-architecturegit clone --depth 1 https://github.com/arango-solutions/arango-sparql-pyWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/rules/arango-solutions/arango-sparql-py/ui-architecture)<a href="https://agentmods.dev/rules/arango-solutions/arango-sparql-py/ui-architecture"><img src="https://agentmods.dev/badge/rules/arango-solutions/arango-sparql-py/ui-architecture.svg" alt="Measured on agentmods" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5 | $0.03578 | $0.03578 |
| Opus 5 | $0.01789 | $0.01789 |
| Sonnet 5 | $0.00716 | $0.00716 |
| Haiku 4.5 | $0.00358 | $0.00358 |
Grade A, and why
ui-architecture scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 4d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 277 lines — stays where its author put it; the contents beside it link to each section on GitHub.
UI Architecture Rules — Object-Centric Workspace
Intent
The workspace is one persistent stage: users stay on the graph while acting on objects (classes, edges, properties, documents, ontologies, runs, pipeline steps). Features are added as capabilities on those objects, not as new destinations.
Two failure modes must never happen:
- The user asks "where am I?" (navigation disorientation).
- The user asks "what does this color/size mean?" with no answer available in-UI (encoding ambiguity).
Core Principles
0. LEFT-CLICK SELECTS, RIGHT-CLICK ACTS.
This is the interaction contract behind every other rule.
| Gesture | Meaning | Surface |
|---|---|---|
| Left-click on an entity | Select + open read-only detail panel | FloatingDetailPanel (canvas entities) or AssetInfoPanel (explorer assets) |
| Right-click on an entity or canvas | Open context menu of actions | ContextMenu |
| Drag between explorer and canvas | Initiate extraction / reparenting / import | Drop zones |
| Keyboard accelerator (1–5, Esc, etc.) | Shortcut for the most frequent menu items | window key listener when focus is not in an input |
Never attach mutation actions to left-click (no "click to approve", no "click to delete"). Read-only selection must be safe.
1. NO NEW ROUTES FOR WORKSPACE WORKFLOWS.
All new object-centric work integrates into /workspace.
- Exempt routes:
/login,/logout,/api/*route handlers (health, ready), and any framework-mandated auth/error shells. - Legacy routes (
/curation,/dashboard,/library,/ontology/[id],/pipeline,/quality,/upload,/entity-resolution) existed before this rule. Do not link to them from new code, do not extend them with new features, and plan migration to overlays. Removing a legacy route is preferred over growing one. - Deep-linking is done via query params on
/workspace, read byuseSearchParams()— e.g.?ontologyId=…&runId=…&lens=confidence. This preserves shareable URLs without introducing routes.
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 4d ago First seen · 277 lines · 3,578 tokens per session scan A 966648037395
ui-architecture is a cursor rule published in the GitHub repository arango-solutions/arango-sparql-py (2 stars, last pushed 18d ago), licensed MIT. It adds 3,578 tokens to every session, about $0.0179 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other cursor rules, from other repositories
css-styling
CSS architecture, tokens, and styling rules for this Docusaurus site. Apply when creating or modifying components, styles, layouts, or any UI-facing code.
codex-premium-website-skills
Apply Codex Skills standards to frontend, website, motion, accessibility, QA, agent reasoning, and handoff work.
shadcn-tailwind-guide
本规范定义了使用 shadcn/ui 和 Tailwind CSS 开发新组件的标准流程和最佳实践。.
ui-components
USE WHEN: Building UI components, structuring layouts, and applying styles using Tailwind CSS.
performance
Frontend performance optimization rules. Apply when optimizing UI or bundle.
ui-components
USE WHEN: Building UI components, structuring layouts, and applying styles using Tailwind CSS.