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/omergulcicek/omergulcicek.comWrote 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/omergulcicek/omergulcicek.com/ui-components)<a href="https://agentmods.dev/rules/omergulcicek/omergulcicek.com/ui-components"><img src="https://agentmods.dev/badge/rules/omergulcicek/omergulcicek.com/ui-components/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/omergulcicek/omergulcicek.com/ui-components"><img src="https://agentmods.dev/badge/rules/omergulcicek/omergulcicek.com/ui-components.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.00000 | $0.00622 |
| Opus 5.5 | $0.00000 | $0.00249 |
| Sonnet 5.5 | $0.00000 | $0.00124 |
| Haiku 4.5 | $0.00000 | $0.00062 |
Grade A, and why
ui-components 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 1mo 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 — 57 lines — stays where its author put it; the contents beside it link to each section on GitHub.
UI Components
Constraints
- Hierarchy: Organize by
ui(stateless),shared(common), andfeature(domain logic). - Atomic: Keep
src/components/uipure; forbid API/Store dependencies. - Separation: Separate data (container) from UI (presentation).
- Composition: Prefer children-based composition over large prop objects.
- States: Implement Skeleton (matching dimensions), EmptyState, and ErrorState for data-driven parts.
- UX: Avoid empty screens; always provide meaningful states.
- Styling: Use Tailwind CSS,
cn(), and Design Tokens. No Hex/RGB or arbitrary values (use Tailwind scale strictly) - Link & card SSOT: Prose links →
ProseLink/ProseIconLink/ProseRouterLink(src/components/shared/prose-link.tsx). Typography →proseParagraphClass,ProseEmphasis,SectionHeading(src/components/shared/prose.styles.ts). Interactive card surfaces →getInteractiveCardClassName+FeaturedProjectCard. Seedocs/UI-PATTERNS.md. - A11y: Enforce semantic HTML,
ariaattributes, and keyboard accessibility. - Exports: Use Named exports only.
Bans
- AI Aesthetic: Default purple/indigo palettes, excessive gradients, overuse of
rounded-2xl, generic card/grid layouts. - Magic Numbers: Arbitrary values (e.g.,
p-[13px]); use Tailwind’s spacing scale strictly. - UX/A11y:
divsoup, "Lorem Ipsum", oronClickon non-interactive elements without keyboard support. - Logic: Default exports or data fetching inside atomic components.
Correct Implementation
Incorrect Implementation
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.
- 1mo ago First seen · 57 lines · 0 tokens per session scan A 355a8fa754cf
ui-components is a cursor rule published in the GitHub repository omergulcicek/omergulcicek.com (15 stars, last pushed 11d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 622 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-09-01.
Other cursor rules, from other repositories
styling-conventions
Provides comprehensive guidelines for writing CSS Modules specifically for UI components within the @vibe/core library (under packages/core/src/components/). This rule covers file naming conventions (e.g., ComponentName.module.scss), CSS nesting, mandatory browser compatibility, strategies for adopting newer CSS APIs…
color-token-management
Comprehensive guide for adding, modifying, and managing color tokens in the @vibe/style package. Covers SCSS theme files, build process, naming conventions, and special handling for hacker theme.
react-sot-storybook-parity
SOT component CSS ownership — Storybook preview must match live routes without per-page token overrides.
self-hosted-fonts-vite
Self-hosted fonts in Vite/TanStack Start — file location, @font-face import order, Webflow legacy family names.
widget-iframe-overlay
Floating widgets with iframes — z-index doesn't work, reserve layout space instead.
webflow-css-preservation
Keep Webflow class names and compiled CSS verbatim during migration; don't refactor to Tailwind utilities until visual parity is confirmed.