- Home
- Skills
- Frontend & Web Apps
- responsive ui review assistant
responsive ui review assistant
Evidence-first responsive UI review agent for diagnosing layout constraints and component behavior across viewports.
Free
Works with the AI Agents you already use
responsive ui review assistant
Example session with this skill installed
Run a FULL review on this navigation component code. It's a horizontal bar with 6 links and a logo. How should it behave on mobile? [CSS/HTML attached]
- Read your context and instructions
- Compiled the responsive ui review
- Generated the UI component
I have completed a FULL responsive review of the navigation component based on the provided HTML and CSS.
Responsive Navigation Analysis
| Viewport | State | Layout Strategy | Observed Constraint |
|---|---|---|---|
| Desktop (>1024px) | Expanded | Horizontal Flex | OBSERVED: Total width of links (620px) + Logo (120px) fits container. |
| Tablet (768px-1024px) | Compressed | Flex Wrap / Justify | CALCULATED: Gap reduces to 8px to prevent overflow. |
| Mobile (<767px) | Disclosure | Hamburger Menu | RECOMMENDATION: Links exceed 320px width; switch to vertical drawer. |
Component Behavior Matrix
- Logo: Remains fixed-width (120px) but shifts to center-aligned on mobile (RECOMMENDATION).
- Links: 6 items transition from
display: flextodisplay: blockwithin a hidden checkbox-triggered drawer.
Touch Targets: Current links are 14px high.
RISK: Mobile targets must increase to 44px height for ergonomic compliance.
Implementation Recommendations
- ID-01 (Priority: P0): Implement a CSS media query at 768px to hide the horizontal list and show a toggle button.
- ID-02 (Priority: P1): Use
overflow-y: autoon the mobile drawer to prevent content cutoff on short viewports.
Next steps
- Apply the suggested 768px breakpoint in your
nav.css. - Increase link padding for mobile view to ensure 44px touch targets.
- Verify the drawer toggle works with keyboard navigation (Tab/Enter).
nav.css
TSX · React component
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
The problem
Static design handoffs and raw CSS often fail to account for how layouts actually break under pressure. Developers frequently rely on "device folklore" breakpoints that don't fit the actual content constraints, leading to overflow issues and broken user flows on mobile.
What it does
- Analyzes HTML, CSS, and screenshots to identify layout failure points where content no longer fits.
- Maps component state transitions across desktop, intermediate, and compact viewports.
- Audits content priority to ensure critical user tasks aren't buried or hidden on smaller screens.
- Diagnoses risks in touch targets, typography wrapping, and grid behavior.
- Generates implementation-ready handoff requirements with explicit acceptance criteria.
Why this beats prompting it yourself
Generic prompts often hallucinate browser behavior or suggest arbitrary breakpoints. This skill uses a structured evidence-first model that separates observed facts from inferences, ensuring recommendations are grounded in your actual code and design constraints rather than generic best practices.
Use cases
- Conducting a pre-deployment responsive QA audit to find edge-case overflow issues.
- Translating a desktop-only design into a mobile-first implementation plan.
- Reviewing legacy CSS to identify rigid layout constraints preventing modern responsiveness.
- Generating precise technical requirements for component behavior across different screen sizes.
Known limitations
Cannot prove actual runtime rendering, browser-specific engine differences, or real-time animation performance without live browser access.
Find more skills like this on the Claude Skills Marketplace, the Codex Skills Marketplace and the Gemini Skills Marketplace, or browse Claude Skills for Frontend & Web Apps.
Does not replace live browser testing, assistive technology audits, or real-time performance monitoring. Structural analysis cannot prove visual rendering or animation behavior.
How to use
- 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
Sign in to Agensi
Your agent shows a sign-in link. Sign in and click Allow.
- 3
Ask for what you need
Your agent loads this skill and uses it on your task. It always asks before buying a skill.
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
9 uses
Times used to date
Free to use
No account required to browse
Trust & safety
Security scan
Security scan passed 1 month ago
- Free with an Agensi account
Permissions
No special permissions declared or detected