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/preshan/grocerylist/ui-ux-rulesgit clone --depth 1 https://github.com/preshan/GroceryListWrote 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/preshan/grocerylist/ui-ux-rules)<a href="https://agentmods.dev/rules/preshan/grocerylist/ui-ux-rules"><img src="https://agentmods.dev/badge/rules/preshan/grocerylist/ui-ux-rules.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.00203 | $0.00203 |
| Opus 5 | $0.00102 | $0.00102 |
| Sonnet 5 | $0.00041 | $0.00041 |
| Haiku 4.5 | $0.00020 | $0.00020 |
Grade A, and why
ui-ux-rules 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 3d 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.
What it actually says
UI UX Rules
The app must be faster and easier than using Samsung Notes checkboxes.
Core flow: Home Screen -> Quick Item Selection -> Confirm List -> Shopping Mode
UX priorities:
- One-tap start from home.
- Swipe or tap between categories.
- Whole item row should be tappable.
- Selected count should always be visible.
- Quick buttons: Select All, Deselect All, Favorites, Frequent Items, Clear.
- Final shopping list should be grouped by category or store type.
- Shopping mode should be distraction-free.
- Avoid showing banner ads in active shopping mode for MVP.
- Use large tap targets.
- Use readable text.
- Support older users and small phones.
Implementation reminders:
- Keep search visible in Quick Item Selection.
- Keep confirm action obvious and always reachable.
- Use empty states with a clear next action.
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.
- 3d ago First seen · 35 lines · 203 tokens per session scan A d863e230018b
ui-ux-rules is a cursor rule published in the GitHub repository preshan/GroceryList (2 stars, last pushed 3mo ago), licensed MIT. It adds 203 tokens to every session, about $0.0010 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
ui-components
USE WHEN: Building UI components, structuring layouts, and applying styles using Tailwind CSS.
ui-components
USE WHEN: Building UI components, structuring layouts, and applying styles using Tailwind CSS.
frontend-theme-guidelines
Cursor rule "frontend-theme-guidelines" from KroMiose/nekro-agent, covering 前端主题系统开发指南, 主题系统架构, 核心文件结构, 基本原则 and 主题使用指南.
taste-enforcement
These dials drive all downstream decisions. Adjust per-prompt when the user specifies a different mood.
ui-architecture
Enforces single-page, context-centric UI patterns for the object-centric workspace.
ui-motion-workflow
Orchestrate motion-aware UI work by sequencing direction, provider choice, implementation, and browser validation.