responsive-ui

responsive-ui is a cursor rule for Cursor from jaycewalzer1/SilverKey-Inc.. It costs 0 tokens per session (564 once invoked), scanned A, original, MIT.

A set of rules for building interfaces that work across different screen sizes and devices. It covers breakpoints, web and React Native patterns, safe areas, overflow, and touch-target sizing.

In plain words
What is it for?
It is for planning responsive web or React Native layouts, choosing breakpoints, handling device safe areas, controlling overflow, and sizing touch controls.
Why use it?
It helps avoid layouts that break on phones, tablets, or other screen sizes, and reduces problems caused by cramped or unreachable controls.

Cursor rule for Cursor

Written for Cursor: installed under .cursor/.

Good fit It is for planning responsive web or React Native layouts, choosing breakpoints, handling device safe areas, controlling overflow, and sizing touch controls.

Compare 6 cursor rules from other repositories ↓
Install with agentmods
npx agentmods add rules/jaycewalzer1/silverkey-inc./responsive-ui
Install

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.

Clone the repo
git clone --depth 1 https://github.com/jaycewalzer1/SilverKey-Inc.

Made for: Cursor.

Wrote 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.

agentmods badge for responsive-ui

README.md
[![agentmods](https://agentmods.dev/badge/rules/jaycewalzer1/silverkey-inc./responsive-ui/github.svg)](https://agentmods.dev/rules/jaycewalzer1/silverkey-inc./responsive-ui)
Your own site
<a href="https://agentmods.dev/rules/jaycewalzer1/silverkey-inc./responsive-ui"><img src="https://agentmods.dev/badge/rules/jaycewalzer1/silverkey-inc./responsive-ui/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.

agentmods 80×15 button for responsive-ui

Your own site · 80×15
<a href="https://agentmods.dev/rules/jaycewalzer1/silverkey-inc./responsive-ui"><img src="https://agentmods.dev/badge/rules/jaycewalzer1/silverkey-inc./responsive-ui.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 0 Nothing until a file matches its globs; then the whole rule loads.
When invoked 564 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00000 $0.00564
Opus 5.5 $0.00000 $0.00226
Sonnet 5.5 $0.00000 $0.00113
Haiku 4.5 $0.00000 $0.00056

Measured 1mo ago against content hash e44cd8170c00, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

responsive-ui 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.

.cursor/rules/frontend/responsive-ui.mdc · 33 lines

What it actually says

Responsive UI (SilverKey)

Canonical reference: documentation/guides/responsive-ui-standards.md — read it for WEB-1–WEB-8, RN-1–RN-10, BOTH-1–BOTH-5, SilverKey route notes, and the seven-area path map.

Must follow (summary)

  • Mobile-first (web): Base layout for small screens; add sm: / md: / lg: only to enhance. Do not use max-width hacks to bolt mobile onto desktop-first layouts.
  • No accidental desktop changes: Preserve desktop appearance unless fixing a real bug or applying a necessary global rule. Prefer minimal diffs.
  • Overflow: Use min-w-0 on flex children with long text; wrap tables in overflow-x-auto. Do not add overflow-x-hidden to ancestors of position: sticky without checking sticky behavior.
  • Touch targets: ≥44×44px (web: min size / padding; RN: minHeight/minWidth or hitSlop).
  • Forms (web): Inputs use at least text-base on touch devices to reduce iOS zoom-on-focus.
  • React Native: SafeAreaView from react-native-safe-area-context on root screens; keyboard + ScrollView patterns per doc; bounded images (width: '100%' + aspectRatio where appropriate).
  • Design system: Keep using standardized Button, Title, BodyText, etc. from Client/packages/ui/ (or @/components/ui / @ui aliases) — responsive work adjusts layout and primitives, not one-off raw <button>/heading styles.

SilverKey specifics

  • Public landing lives under packages/features/homeauth/.../landing/ (web HomeFeature.web.tsx).
  • Post-login (web): default is /dashboard, not a separate home route.
  • Mobile auth welcome: HomeScreenNative is pre-login; first tab after auth is Dashboard.

After edits

Run pnpm lint and pnpm typecheck in Client/ when touching responsive code (see documentation/reference/linting.md).

Changes

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.

  1. 1mo ago First seen · 33 lines · 0 tokens per session scan A e44cd8170c00

Subscribe to this mod's changes

responsive-ui is a cursor rule published in the GitHub repository jaycewalzer1/SilverKey-Inc. (2 stars, last pushed 3d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 564 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-31.