More screenshots

    Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIMuseMuseDotsDots+21 more

    Fitcheck: every screen size, checked and fixed

    1

    Audits a page at 320 to 1440 px against ten responsive rules, reports each break with file:line and the width, and fixes it with the smallest change.

    Free

    2 usesSecurity scanned
    Fitcheck: every screen size, checked and fixed

    Fitcheck: every screen size, checked and fixed

    Example session with this skill installed

    Check the responsiveness of app/pricing/page.tsx. It looks broken on small phones.

    • Read your context and instructions
    • Compiled the fitcheck
    • Generated the UI component

    I have audited app/pricing/page.tsx across the five target widths. I found a critical overflow issue at 320px and a touch target violation on the CTA buttons.

    Responsive audit: app/pricing/page.tsx

    Widths checked: 320, 375, 768, 1024, 1440

    🔴 Breaks (content lost, overflow, unusable)

    • app/pricing/page.tsx:42 at 320px: plan cards overflow, page scrolls sideways
      fix: changed grid-cols-3 to grid-cols-1 md:grid-cols-3 and added min-w-0 to card wrappers.

    🟡 Degraded (works, but hard to use)

    • components/PricingCard.tsx:112 at 375px: "Select Plan" button target is 32px height
      fix: increased vertical padding to py-3 to ensure a 44px touch target.

    🟢 Polish

    • app/pricing/page.tsx:12: pricing header uses text-4xl
      fix: implemented fluid type using text-[clamp(1.5rem,5vw,2.25rem)].

    Summary: 1 breaks, 1 degraded, 1 polish. Fixed: 3. Re-checked at all widths.

    Next steps

    1. Review the layout on the 320px simulated device to confirm the grid stack.
    2. Verify that the larger touch targets do not crowd the desktop layout.
    3. Deploy to staging and test on a physical iOS device to confirm the safe-area padding.

    page.tsx

    TSX · React component

    Generated

    Example file from a real run - the skill writes it into your workspace.

    Connects securely to your tools. The creator never sees your data.

    About this skill

    Web pages often break on small screens because of fixed widths, hidden content, or poor touch targets. This skill audits your components across five specific viewport widths to find and fix responsive layout failures.

    What it does

    • Multi-viewport testing checks layouts at 320, 375, 768, 1024, and 1440 px widths.
    • Mobile-first enforcement refactors max-width overrides into layered min-width breakpoints.
    • Touch target validation ensures interactive elements meet the 44px minimum for mobile usability.
    • Visual stability fixes replaces vh with dvh units to prevent layout shifts from mobile browser bars.
    • Overflow prevention identifies and resolves horizontal scrolling issues caused by long strings or rigid grid items.
    • Form optimization scales input text to at least 16px to prevent intrusive iOS auto-zoom.

    How it works

    1. Scope definition identifies the target route or component and its associated layout files.
    2. Visual audit captures screenshots or analyzes code at five specific breakpoints.
    3. Rule validation checks the implementation against ten core responsive principles including safe areas and fluid typography.
    4. Issue reporting generates a severity-ranked list of bugs with specific file:line references.
    5. Applied fixes implements the minimal CSS or class changes required and re-verifies across all widths.

    Frameworks & tools

    This skill is framework-neutral. It works with Tailwind CSS, vanilla CSS, and modern web frameworks like React or Next.js. It utilizes Playwright or browser device toolbars for visual capture when available.

    Why this beats prompting it yourself

    Generic prompts often ignore the "small mobile" 320px width or suggest heavy JavaScript listeners for layout. This skill enforces a strict CSS-first approach and follows a systematic 10-point checklist that covers edge cases like env(safe-area-inset) and clamp() for fluid type.

    Use cases

    • Auditing a pricing page before shipping to ensure grid cards do not overflow on small phones.
    • Fixing "broken" mobile navigation menus where touch targets are too small for thumbs.
    • Migrating a legacy desktop-centric component to a modern mobile-first structure.
    • Preventing horizontal scroll on blog layouts containing long URLs or wide tables.

    Known limitations

    Requires the application to be runnable locally for screenshot-based audits; otherwise, it performs a code-only static analysis. Does not add responsive libraries; CSS media and container queries cover it.

    Requires local execution for screenshot audits. Cannot add new libraries. Static code analysis used if app is not running.

    How to use

    1. 1

      Connect your agent to the Agensi MCP

      Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup

    2. 2

      Sign in to Agensi

      Your agent shows a sign-in link. Sign in and click Allow.

    3. 3

      Ask for what you need

      Your agent loads this skill and uses it on your task. It always asks before any payment.

    Reviews

    No reviews yet

    Be one of the first to try it. Every listed skill goes through the trust checks below.

    Security scanned

    Checked by our 8-point scan before listing

    2 uses

    Times used to date

    Free forever

    No account required to browse

    Trust & safety

    Security scan

    Security scan passed 29 days ago

    • Free with an Agensi account

    Permissions

    Browser
    Listed29 days ago

    What's inside

    Frequently Asked Questions

    Audits a page at 320 to 1440 px against ten responsive rules, reports each break with file:line and the width, and fixes it with the smallest change.

    This skill uses the open SKILL.md standard. Use it through an MCP-compatible agent connected to Agensi, and check the compatibility information on this page for confirmed agents and required capabilities.

    Connect your AI agent to Agensi through MCP, then ask it to use Fitcheck: every screen size, checked and fixed on your task. Your agent loads the latest approved version each time. Paid skills require a purchase or active subscription. Skill files are not available for download; your licence does not allow you to save, copy or export any part of a skill.

    New in Frontend & Web Apps