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/Kevin-Liu-01/LoopWrote 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/kevin-liu-01/loop/frontend-10x-prompting)<a href="https://agentmods.dev/rules/kevin-liu-01/loop/frontend-10x-prompting"><img src="https://agentmods.dev/badge/rules/kevin-liu-01/loop/frontend-10x-prompting.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.00000 | $0.00270 |
| Opus 5 | $0.00000 | $0.00135 |
| Sonnet 5 | $0.00000 | $0.00054 |
| Haiku 4.5 | $0.00000 | $0.00027 |
Grade A, and why
frontend-10x-prompting 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 8d 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
Frontend Prompting Rules
When asked to design or generate frontend work, prompts should specify:
- product and audience
- methodology lens
- art-direction thesis
- palette
- type pairing
- material language
- component inventory
- tactic families
- motion budget
- runtime stack
- performance constraints
- banned defaults
Good prompts ask for proposals first.
Default exploration pattern:
- propose 3 distinct directions
- explain type, palette, layout, and motion thesis for each
- choose one direction
- implement with tokens and constraints
When using screenshots:
- decompose into background, UI, and texture layers
- recreate assets separately
- recompose in code
Useful bans:
- no generic SaaS gradients
- no Inter/Roboto unless requested
- no default shadcn look
- no plain CSS animation architecture as the default
- no motion without hierarchy
- no centered-by-habit layouts
When generating video or image backgrounds:
- first frame must work as a poster
- motion must loop cleanly
- preserve negative space for copy
- avoid noisy movement behind text
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.
- 8d ago First seen · 54 lines · 0 tokens per session scan A 3f61aefb8a73
frontend-10x-prompting is a cursor rule published in the GitHub repository Kevin-Liu-01/Loop (18 stars, last pushed 1mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 270 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-30.
Other cursor rules, from other repositories
hatch3r-design-system-detection
Mandatory detection of existing design tokens, theme primitives, and component library before AI agents author new UI components.
hatch3r-component-conventions
Component structure, styling tokens, loading/error/empty states, form validation timing, and accessible label patterns for Vue, React, and JSX.
reexamine_keyboard
Re-examine keyboard efficiency — skip links, shortcuts, tab order, focus traps.
motion-design
Motion design rules — context-aware animation principles drawn from Emil Kowalski, Jakub Krehel, and Jhey Tompkins. Covers timing, enter/exit recipes, motion gaps, accessibility, performance, and anti-patterns.
66-stack-shadcn
USE WHEN: working with Shadcn UI, Tailwind CSS, Lucide icons, or Sonner toasts.
ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.