mobile

mobile is a skill for Claude Code from dkadts/landing-kit-building. It costs 88 tokens per session (2,250 once invoked), scanned A, original, MIT.

A mobile-adaptation guide for extending a completed desktop website to phones and small screens.

In plain words
What is it for?
Use it after the desktop build and audit are complete. It defines mobile and small-phone breakpoints, responsive layout rules, cache-refresh guidance, and a headless-browser safety check.
Why use it?
It prevents common mobile problems such as broken composition, overflowing text, unsafe padding, horizontal scrolling, and controls that are too small to tap.

Skill for Claude Code

Written for Claude Code: installed under .claude/.

Good fit Use it after the desktop build and audit are complete. It defines mobile and small-phone breakpoints, responsive layout rules, cache-refresh guidance, and a headless-browser safety check.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/dkadts/landing-kit-building/mobile
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.

Any agent
npx skills add dkadts/landing-kit-building --skill mobile
Clone the repo
git clone --depth 1 https://github.com/dkadts/landing-kit-building

Made for: Claude Code.

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 mobile

README.md
[![agentmods](https://agentmods.dev/badge/skills/dkadts/landing-kit-building/mobile.svg)](https://agentmods.dev/skills/dkadts/landing-kit-building/mobile)
Your own site
<a href="https://agentmods.dev/skills/dkadts/landing-kit-building/mobile"><img src="https://agentmods.dev/badge/skills/dkadts/landing-kit-building/mobile.svg" alt="Measured on agentmods" height="20"></a>
Per session 88 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,250 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.00088 $0.02250
Opus 5 $0.00044 $0.01125
Sonnet 5 $0.00018 $0.00450
Haiku 4.5 $0.00009 $0.00225

Measured 8d ago against content hash c756f536b3bb, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-08, from the pricing page.

Security

Grade A, and why

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

.claude/skills/mobile/SKILL.md · 213 lines

How it starts

The opening of the file, as written. The whole thing — 213 lines — stays where its author put it; the contents beside it link to each section on GitHub.

/mobile

Skill hardened by real iterations. All rules below come from projects where mobile ate weeks and hundreds of fixes.

When to use

  • brief/00-priority.md = desktop-first.
  • After /build (desktop version ready).
  • Edits to an existing mobile version.

If mobile-first — this skill does not apply. Mobile is built directly in /build, desktop is extended via expansion.css.

Requirements

  • Desktop version exists and works.
  • All sections assembled, /audit shows desktop = pass.
  • site/css/responsive.css exists (empty template).

Rules (must-follow)

1. Breakpoints

  • ≤ 768px = mobile (hamburger active, layout adapted).
  • ≤ 480px = small-phone (targeted fixes where general mobile rules are insufficient).

2. Preserve desktop composition

Do NOT restructure blocks. Do not change element order inside a section. Do not swap layouts (grid → stack without reason). Scale proportionally in the same positioning.

Exception: if an element physically does not fit (e.g. a horizontal-timeline of 6 steps does not work at 390px) — make an explicit decision to restructure and log it in DESIGN.md.

3. Uniform scale factor per block

Within one block — one multiplier for all sizes (card:phone ratio, gap, margin, height). Otherwise proportions break.

Example: if desktop .card { width: 20vw; } → mobile .card { width: 45vw; } (×2.25). Then gap, phone-mockup, and everything inside — also ×2.25.

4. Preserve JS-driven carousels

Never turn a JS carousel into CSS scroll-snap on mobile. Never set transform: none !important on .track — it will kill the JS.

If a different visual is needed — change sizes/gap, but not the behavior type.

5. Text in collapsed cards — nowrap + ellipsis

When a card is scaled down, inner text must:

white-space: nowrap;
overflow: hidden;
text-overflow: ellipsis;

Otherwise lines spill sideways or wrap to new lines.

6. Font-size via clamp()

font-size: clamp(min_px, Nvw, max_px) instead of raw Nvw. Guarantees text does not collapse to invisibility at 320px.

Read the full file on GitHub · 213 lines

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. 8d ago First seen · 213 lines · 88 tokens per session scan A c756f536b3bb

Subscribe to this mod's changes

mobile is a skill published in the GitHub repository dkadts/landing-kit-building (2 stars, last pushed 19d ago), licensed MIT. It adds 88 tokens to every session and 2,250 once invoked, about $0.0004 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.

Related

Other skills, from other repositories

flutter-patterns

Flutter/Dart: widgets, state mgmt (Riverpod/Bloc), navigation, platform channels. Triggers: Flutter, Dart, widget, Riverpod, Bloc, pubspec, hot reload.

softspark/ai-toolkit · 44 tokens

next-upgrade

Upgrade Next.js to the latest version following official migration guides and codemods.

agustinusnathaniel/nextarter-tailwind · 19 tokens

flutter-development

Cross-platform development with Flutter and Dart for iOS, Android, Web, Desktop, and embedded. Use when building Flutter apps, implementing Material/Cupertino design, or optimizing Dart code.

travisjneuman/.claude · 41 tokens

react-native

React Native and Expo patterns for building performant mobile apps. Covers list performance, animations with Reanimated, navigation, UI patterns, state management, platform-specific code, and Expo workflows. Use when building or reviewing React Native code. Triggers: 'react native', 'expo', 'mobile app', 'react native…

jezweb/claude-skills · 91 tokens

react-native-expert

Expert in React Native, cross-platform mobile development, native modules, and performance optimization. Use when the user mentions mobile, JavaScript, TypeScript, cross platform, iOS, or Android, or when the task involves React Native Architecture, Component Types, Hooks Essentials, or Navigation.

personamanagmentlayer/pcl · 62 tokens

regenerate-api

Regenerate the AppointMe frontend API client (orval/TanStack Query hooks + TypeScript schemas) after the backend OpenAPI surface changes. Use this whenever backend endpoints, request/response DTOs, or other contract-affecting types are added, removed, or modified — e.g. after editing files under src/AppointMe.Api…

bravodev-hub/appointme · 136 tokens