Responsive Check logo

Responsive Check

Community
dev-ik
responsive-check

Use when a screen must be checked across mobile, tablet, laptop, or desktop sizes for overflow, wrapping, sticky overlaps, collapsed navigation, unreachable actions, sheets, dialogs, tables, filters, or charts. Skip non-UI maintenance.

Overview

Publisherdev-ik
Repositoryai-design-rules
Skill nameresponsive-check
Stars
3
Forks
0
Bundled files
Instructions only
LicenseMIT
Links
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • Self-contained

    Everything the model needs lives in the instructions — no extra files to sync.

  • Open source

    Published by dev-ik on GitHub. Read the source before you install it.

Installation

Install the Responsive Check AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
    https://github.com/dev-ik/ai-design-rules/tree/main/skills/responsive-check
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/dev-ik/ai-design-rules.git /tmp/ai-design-rules
mkdir -p .claude/skills
cp -r /tmp/ai-design-rules/skills/responsive-check .claude/skills/responsive-check
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Responsive Check in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Responsive Check on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Responsive Check is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

Responsive Check

Verify adaptation through browser behavior and inspected screenshots. This execution skill complements mobile-ux-expert, which guides touch-first product decisions.

Scope and preparation

Identify the target devices, primary task, changed breakpoints, long-content cases, and relevant states. Retrieve focused graph context with --platform mobile and read the applicable research and rules. Use the project's actual breakpoints and device targets. Example CSS viewports for exploratory sampling are 390x844, 768x1024, and 1440x900; include narrower widths and just below/above affected breakpoints when the product supports them. These samples are not universal layout rules or a substitute for actual devices.

Use available browser tools or the project's existing Playwright setup. Record viewport dimensions, scale, theme, data, and state. If browser access is absent, provide a source/screenshot-limited review and mark unseen widths and interactions unverified.

Execute

  1. Load the same flow at each selected width. Exercise capture/navigation, open and close sheets or dialogs, and scroll through long content and sticky regions.
  2. Check horizontal page overflow, broken grids, long labels and entries, clipped text, navigation collapse, hidden primary actions, oversized dialogs, and controls obscured by sticky elements. For tables/charts, distinguish intentional bounded horizontal scrolling from accidental page overflow.
  3. Observe wrapping and control placement before and after state changes, including loading, validation errors, retry, and success. Compare geometry when PERF-001 applies.
  4. Inspect images of each captured state and confirm suspected bounds with DOM measurements. Judge touch targets using the clickable area and the graph's A11Y-001, not icon dimensions alone.
  5. For mobile input flows, record whether a real virtual keyboard was exercised. Desktop viewport emulation does not prove keyboard resizing, safe-area handling, or physical-device touch behavior. Mark those as gaps if relevant and untested.
  6. After authorized fixes, repeat the failing width, relevant neighboring breakpoint, and affected wide layout. Capture before/after evidence under matching conditions.

Output

Return a scoped verdict, then viewport | state/action | observed behavior | screenshot/measurement | checked/unverified/not applicable. Each confirmed issue includes severity, reproduction, user impact, graph/reference basis, focused fix, and verified component/file when known. Report breakpoint behavior and physical-device gaps separately. A screenshot at one size is not a responsive pass.

Sources: CHECK-00001, RULE-00005 / UX-001, RULE-00009 / A11Y-001, RULE-00011 / PERF-001, and their retrieved source research. Use Playwright emulation for tool mechanics; it does not replace device evidence.

Frequently asked questions

What does the Responsive Check AI skill do?

Use when a screen must be checked across mobile, tablet, laptop, or desktop sizes for overflow, wrapping, sticky overlaps, collapsed navigation, unreachable actions, sheets, dialogs, tables, filters, or charts. Skip non-UI maintenance.

Why use Responsive Check on TypingMind?

Because you install it once and use it with any model. Responsive Check is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Responsive Check in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/dev-ik/ai-design-rules/tree/main/skills/responsive-check. TypingMind reads its SKILL.md and installs it as a skill you can enable per chat.

Which AI models can use Responsive Check?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Responsive Check?

As many as you like. As long as a model supports skills, you can use Responsive Check with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Responsive Check AI skill free?

Yes. It is published on GitHub by dev-ik under the MIT license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇