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/rizkyhaksono/portfolio-v3Wrote 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/rizkyhaksono/portfolio-v3/ui-layout-consistency)<a href="https://agentmods.dev/rules/rizkyhaksono/portfolio-v3/ui-layout-consistency"><img src="https://agentmods.dev/badge/rules/rizkyhaksono/portfolio-v3/ui-layout-consistency.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.00903 | $0.00903 |
| Opus 5 | $0.00451 | $0.00451 |
| Sonnet 5 | $0.00181 | $0.00181 |
| Haiku 4.5 | $0.00090 | $0.00090 |
Grade A, and why
ui-layout-consistency 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 7d 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 — 87 lines — stays where its author put it; the contents beside it link to each section on GitHub.
UI Layout & Surface Consistency
Portfolio v3 uses a monochrome, square, hairline-border design language. Keep every new UI on this system.
Tokens (source of truth)
- CSS variables in
src/app/globals.css(semantic colors only:background,foreground,card,border,muted,primary, …) - Radius: all named radii collapse to
0intailwind.config.ts(square). Keeprounded-fullonly for avatars/dots. - Shared class tokens:
src/lib/design-system.ts(SURFACE,PAGE_WIDTH,SECTION_SPACING)
Never use raw palette classes like neutral-*, text-black, hex hovers (#262626, #D9D9D9), or border-white/10 glass stacks on content cards.
Three surface dialects only
| Variant | Use for | Primitive |
|---|---|---|
| solid | Content boxes, lists, feature/platform cards | Card, FeatureCard, Surface variant="solid" |
| glass | Window chrome only (title bar + frosted shell) | MacWindow, Surface variant="glass" / glass-static |
| inset | Nested rows, sidebar blocks, status cells | Surface variant="inset" |
Forbidden on content cards
Do not invent glass content cards:
border-white/10 bg-white/5 backdrop-blur-md hover:shadow-xl hover:-translate-y-1
Use solid + hover:border-foreground/20 instead.
Page shell recipe (visitor / user)
BaseLayout(sidebar?, rightSidebar?)
└─ PageBody width="default" | "prose" | "article" | "wide"
└─ SectionHeading (as="h1" on page routes)
└─ MacWindow? (tools / lists) OR Card / FeatureCard / Surface rows
- Prefer
PageSectionfor home/page blocks (mt-10+ optionalSectionHeading). - Prefer
PageBodyfor width — do not stack extrapx-4 lg:px-0inside BaseLayout (container already pads). - Do not invent
max-w-8xl(undefined). UsePAGE_WIDTHpresets.
Heading & micro-UI
- Section titles: always
SectionHeading(eyebrow + display title + optional serif italic accent). - Labels/tags:
Eyebrow,Chip. - Stat rows:
StatStrip.
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.
- 7d ago First seen · 87 lines · 903 tokens per session scan A e4172c1ad8f6
ui-layout-consistency is a cursor rule published in the GitHub repository rizkyhaksono/portfolio-v3 (6 stars, last pushed today), licensed MIT. It adds 903 tokens to every session, about $0.0045 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".