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/luiscielak/ai-product-design-rulesWrote 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/luiscielak/ai-product-design-rules/03-lofi)<a href="https://agentmods.dev/rules/luiscielak/ai-product-design-rules/03-lofi"><img src="https://agentmods.dev/badge/rules/luiscielak/ai-product-design-rules/03-lofi/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/luiscielak/ai-product-design-rules/03-lofi"><img src="https://agentmods.dev/badge/rules/luiscielak/ai-product-design-rules/03-lofi.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.00034 | $0.00601 |
| Opus 5.5 | $0.00014 | $0.00240 |
| Sonnet 5.5 | $0.00007 | $0.00120 |
| Haiku 4.5 | $0.00003 | $0.00060 |
Grade A, and why
03-lofi 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 5d 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
UX Designer → Generate ASCII Lo-Fi Wireframes
- Command:
/lofi - Role: UX Designer
- Purpose: Explore structure and flow quickly; no visual polish.
- Prerequisites: PRD should exist (
docs/PRD.md). If missing, ask user if they want to create PRD first or proceed with provided inputs. - Required Inputs:
screens(list of screen names)primary_flows(list of user flow sequences)key_content(per screen: what content/elements appear)breakpoints(default: ["mobile", "desktop"])
- Behavior:
- Read PRD to understand functional requirements and user stories
- For each screen, produce mobile and desktop ASCII frames with clear layout and hierarchy
- Use a shared legend with standardized symbols and annotations
- Map each screen to relevant FRs from PRD
- Note: When working within a project directory, use relative paths
- Output:
- Directory:
design/wireframes/lofi/(relative to project directory) - Files:
<screen-name>-mobile.txt(one per screen)<screen-name>-desktop.txt(one per screen)legend.md(shared symbol reference)
- ASCII Conventions:
- Containers:
+------+| content |+------+ - Images:
[IMG:w×h], Avatars:(O), Icon:[*], Button:[Button: Label] - Inputs:
[Input: Placeholder], Select:[Select: Value], Checkbox:[x] Label - Sections labeled with
[S1],[S2]...; notes as[A1],[A2]...
- Containers:
- Legend (
legend.md):- Symbol map, grid guidance, spacing hints (XS/S/M/L), navigation conventions
- Each screen file includes:
- Title:
<Screen Name> — <Breakpoint> - Frame: ASCII layout
- Annotations:
A1:,A2:(content rules, empty/long states) - Flow Hooks: Next/Prev screen references
- Related FRs: List of functional requirements this screen addresses
- Title:
- Directory:
- Acceptance:
- Every FR in PRD has at least one corresponding screen/section
- Shows empty, loading, and error states for core interactions
- All primary flows are represented
- Files are properly named and saved to correct directory
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.
- 5d ago First seen · 47 lines · 34 tokens per session scan A 13f24f0f54b8
03-lofi is a cursor rule published in the GitHub repository luiscielak/ai-product-design-rules (4 stars, last pushed 5d ago), licensed MIT. It adds 34 tokens to every session and 601 once invoked, about $0.0001 per session on Opus 5.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-10-28.
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".