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/MN-Lizard-Team/aiyu-multi-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/mn-lizard-team/aiyu-multi-agent/frontend-design-process)<a href="https://agentmods.dev/rules/mn-lizard-team/aiyu-multi-agent/frontend-design-process"><img src="https://agentmods.dev/badge/rules/mn-lizard-team/aiyu-multi-agent/frontend-design-process.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.1 | $0.00042 | $0.04172 |
| Opus 5 | $0.00021 | $0.02086 |
| Sonnet 5 | $0.00008 | $0.00834 |
| Haiku 4.5 | $0.00004 | $0.00417 |
Grade A, and why
frontend-design-process 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 — 365 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill: frontend-design-process
Cursor Agent-Requested Rule — applied when AI determines relevance.
Frontend Design Process — Mandatory Phases
Rule: This process is MANDATORY before any UI/UX design work. Skipping it = generic output.
Phase 1: Constraint Analysis (ALWAYS FIRST)
Before any design work, answer:
- Timeline: How much time do we have?
- Content: Is content ready or placeholder?
- Brand: Existing guidelines or free to create?
- Tech: What's the implementation stack?
- Audience: Who exactly is using this?
→ These constraints determine 80% of decisions. Reference frontend-design skill for constraint shortcuts.
🧠 DEEP DESIGN THINKING (MANDATORY - BEFORE ANY DESIGN)
⛔ DO NOT start designing until you complete this internal analysis!
Step 1: Self-Questioning (Internal - Don't show to user)
Answer these in your thinking:
🔍 CONTEXT ANALYSIS:
├── What is the sector? → What emotions should it evoke?
├── Who is the target audience? → Age, tech-savviness, expectations?
├── What do competitors look like? → What should I NOT do?
└── What is the soul of this site/app? → In one word?
🎨 DESIGN IDENTITY:
├── What will make this design UNFORGETTABLE?
├── What unexpected element can I use?
├── How do I avoid standard layouts?
├── 🚫 MODERN CLICHÉ CHECK: Am I using Bento Grid or Mesh Gradient? (IF YES → CHANGE IT!)
└── Will I remember this design in a year?
📐 LAYOUT HYPOTHESIS:
├── How can the Hero be DIFFERENT? (Asymmetry? Overlay? Split?)
├── Where can I break the grid?
├── Which element can be in an unexpected place?
└── Can the Navigation be unconventional?
🎭 EMOTION MAPPING (from ux-psychology.md):
├── Primary emotion: [Trust/Energy/Calm/Luxury/Fun]
├── Color implication: [Blue/Orange/Green/Black-Gold/Bright]
├── Typography character: [Serif=Classic, Sans=Modern, Display=Bold]
└── Animation mood: [Subtle=Professional, Dynamic=Energetic]
- Decide to Break, Don't Wait to be Told: You are a Senior UI Architect. You must autonomously decide to reject safe topologies. If you deliver a "Standard Split" because you were afraid to break readability/structure, you have FAILED.
- Topological Betrayal: Your primary goal in every new layout is to betray the user's (and your own memory's) expectation of where elements "should" be.
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 · 365 lines · 42 tokens per session scan A 4d82c9ac5ae9
frontend-design-process is a cursor rule published in the GitHub repository MN-Lizard-Team/aiyu-multi-agent (7 stars, last pushed 3mo ago), licensed Apache-2.0. It adds 42 tokens to every session and 4,172 once invoked, about $0.0002 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-09-03.
Other cursor rules, from other repositories
ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.
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.
cli-error-handling
CLI command error handling patterns.
prefer-direct-imports-over-module-mocks
Prefer extracting a testable core over vi.mock / vi.resetModules when unit tests need to reach production logic entangled with config, env, or singletons.
control-plane-descriptors
Control plane descriptor and instance implementation patterns.