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/vepo/issues/issues-uxgit clone --depth 1 https://github.com/vepo/issuesWhat 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.00000 | $0.01279 |
| Opus 5 | $0.00000 | $0.00639 |
| Sonnet 5 | $0.00000 | $0.00256 |
| Haiku 4.5 | $0.00000 | $0.00128 |
Grade A, and why
issues-ux 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 2d 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 — 92 lines — stays where its author put it; the contents beside it link to each section on GitHub.
UI/UX — Nielsen heuristics
Every UI/UX change MUST be reviewed against Nielsen's 10 usability heuristics before merge.
UI Elements Gallery (mandatory)
Before creating or changing any UI element, read docs/ui-elements-gallery.md:
- Find an existing element to reuse (class, Material component, behavior).
- Match documented properties, style (tokens/classes), and behavior.
- If no element fits, add the new element to the gallery in the same PR.
- Do not introduce ad-hoc buttons, colors, or form patterns outside the gallery.
Checklist (per screen or flow)
| # | Heuristic | Issues application |
|---|---|---|
| 1 | Visibility of system status | Loading/disabled during submit; notification badge; kanban drop feedback; toasts |
| 2 | Match system / real world | Domain terms from domain-specification.md; PT-BR labels; familiar tracker patterns (Kanban, ticket ID) |
| 3 | User control & freedom | Cancel/close on dialogs; back navigation; logout; avoid disableClose unless required |
| 4 | Consistency & standards | Gallery elements + styles.scss; same button hierarchy; no one-off hex colours |
| 5 | Error prevention | mat-form-field validation; confirm destructive actions |
| 6 | Recognition over recall | Visible nav, status filter, project cards — minimise memory load |
| 7 | Flexibility & efficiency | Header search; Enter on search; role-based menu shortcuts |
| 8 | Aesthetic & minimalist | Flat UI principles below; content over decoration; clear hierarchy |
| 9 | Error recovery | .error messages; toasts; empty states with next-step guidance |
| 10 | Help & documentation | Footer OpenAPI link; empty states; tooltips where labels are ambiguous |
Flat UI design language
Issues follows flat UI design — the style popularized by Microsoft's Metro design language (Windows Phone, 2010) and continued in Microsoft Fluent Design. Flat design favours clarity and function over ornamental depth; it is the baseline for enterprise and productivity apps.
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.
- 2d ago First seen · 92 lines · 0 tokens per session scan A 2ab98654f371
issues-ux is a cursor rule published in the GitHub repository vepo/issues (8 stars, last pushed 1mo ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 1,279 tokens. 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
project-context
EDDI Backend — AI Agent Instructions. Complete project context, architecture, and coding guidelines.
cli-forge-schema
Generate GitHub-compatible Mermaid diagrams — auto-picks diagram type, splits complex ones, converts tables/kanban/PERT.
project-modules-and-stack
YiSmartCloud repo stack and Maven module map.
sprint-planning
BMAD BMM Agent: sprint-planning.
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.
dev-standard
Apache Superset development standards and guidelines for Cursor IDE.