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.
git clone --depth 1 https://github.com/VoTruongDanh/Skills-AgentWrote 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/votruongdanh/skills-agent/ui-ux-pro-max)<a href="https://agentmods.dev/rules/votruongdanh/skills-agent/ui-ux-pro-max"><img src="https://agentmods.dev/badge/rules/votruongdanh/skills-agent/ui-ux-pro-max/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/rules/votruongdanh/skills-agent/ui-ux-pro-max"><img src="https://agentmods.dev/badge/rules/votruongdanh/skills-agent/ui-ux-pro-max.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00058 | $0.01009 |
| Opus 5 | $0.00029 | $0.00504 |
| Sonnet 5 | $0.00012 | $0.00202 |
| Haiku 4.5 | $0.00006 | $0.00101 |
Grade A, and why
ui-ux-pro-max 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 — 78 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Memory Protocol
START: Read .ai-memory.md from project root. Check design system, brand guidelines, component library, past UI decisions, accessibility notes, and responsive design patterns.
END: Update .ai-memory.md using Memory Compaction Rules with: UI/UX changes, patterns used, a11y improvements, and brand consistency notes.
Goal
Upgrade the product experience with clear, practical UI/UX improvements.
Agent Routing
- Primary → read
.kiro/skills/agents/agents/frontend-specialist.mdand apply its knowledge - For performance of UI (load time, animations) → read
.kiro/skills/agents/agents/performance-optimizer.mdand apply its knowledge - For accessibility compliance → apply WCAG knowledge from frontend-specialist
- For mobile responsiveness → apply mobile patterns from frontend-specialist
Socratic Gate
Before improving UI/UX, verify:
- What screen, flow, or component is being improved?
- What is the current pain point? (visual, usability, accessibility, performance?)
- Are there existing design guidelines or component library? If any answer is unclear, ASK before proceeding.
Workflow
- Read Memory — Load
.ai-memory.mdfor design history and UI patterns. - Identify the screen, flow, or component being improved.
- Evaluate hierarchy, spacing, clarity, accessibility, states, feedback, and conversion friction.
- Recommend concrete improvements with rationale.
- When asked to implement, favor polished but maintainable UI.
- Quality Gate — Read
.kiro/skills/_scripts/checklist.mdand verify all states and accessibility. - Update Memory — Save UI/UX decisions and patterns to
.ai-memory.md.
Output format
- UX issues found
- Visual issues found
- Recommended changes (prioritized)
- Accessibility notes (WCAG compliance)
- Implementation priorities
- Component states covered (empty, loading, error, success)
Checklist
- Target screen/component identified
- Hierarchy and spacing evaluated
- Accessibility checked (WCAG)
- All states covered (empty, loading, error, success)
- Mobile responsiveness considered
- Performance impact assessed
- Brand consistency maintained
- Memory file updated
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 Changed · +8 lines 72b2066e1aa6
- 9d ago First seen · 70 lines · 58 tokens per session scan A 53a7a03364f3
ui-ux-pro-max is a cursor rule published in the GitHub repository VoTruongDanh/Skills-Agent (2 stars, last pushed 5d ago), licensed MIT. It adds 58 tokens to every session and 1,009 once invoked, about $0.0003 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
prototype-previewer
Build interactive prototype reviewers with synced review notes and Figma capture pages.
figma-performance
Handling large documents efficiently in the Plugin API.
ant-design
A set of guidelines for using Ant Design, a collection of ready-made interface components, in React applications. It covers code organization, performance, security, testing, and common mistakes.
7-day-nextjs-web-design-cursor
A seven-day design workflow for web products that will be built in Next.js.
clone-ai
Site Clone AI — website klonlama pipeline kuralları.
mermaid
Diagram Creator. Load when the user requests "Create a diagram".