Menu
Open the app in Cursor's browser at multiple viewport sizes, screenshot each, and report any layout breakage.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Generate or edit images using the OpenAI Image API (gpt-image-2). Use when the user asks to generate, create, draw, render, illustrate, mock up, or edit an image, icon, logo, mockup, illustration, OG image, blog hero, marketing asset, or similar visual. Also use when the user supplies a reference image and asks to modify, restyle, or remix it. Triggers on: "generate an image", "create an image", "make a picture of", "edit this image", "restyle this", "make a mockup of", "draw a", "render a", "illustration of".
When the same multi-step workflow repeats in Cursor (user corrections or agent redos), capture it as a new SKILL.md under .cursor/skills/ so future sessions load it automatically.
After navigating and interacting in Cursor's built-in browser, use browser_network_requests to audit every fetch/XHR for failures, slowness, duplicate calls, and suspicious payloads. Use for API-heavy pages and after backend or client networking changes.
When GitHub Actions fails, fetch failing job logs and assign each failing job to a separate subagent that fixes its slice of the problem in parallel. Use for multi-job CI failures where jobs are independent.
Run four parallel read-only subagents that each review the same diff from a different lens — security, performance, correctness, and readability — then merge findings into one report. Use before merging large or risky PRs.
Execute a user flow step-by-step in Cursor's built-in browser while documenting each action, then emit a Playwright test that replays the same flow using stable selectors derived from the accessibility tree.
| name | responsive-testing |
| description | Open the app in Cursor's browser at multiple viewport sizes, screenshot each, and report any layout breakage. |
| user-invocable | true |
After a UI change, verify the app looks correct at all standard breakpoints.
| Name | Width | Tailwind |
|---|---|---|
| Mobile (small) | 375px | default |
| Mobile (large) | 428px | default |
| Tablet | 768px | md: |
| Desktop | 1280px | xl: |
| Ultrawide | 1536px | 2xl: |
Use browser_navigate to open the target URL (usually http://localhost:3000 or whatever the dev server is running on).
For each viewport size:
browser_navigate with viewport parameters, or use browser_snapshot to inspect the layoutbrowser_take_screenshotbrowser_snapshot for the aria tree — look for:
Responsive Test Results:
375px (mobile): PASS — layout stacks correctly
428px (mobile): PASS
768px (tablet): WARN — nav items overlap, need hamburger menu
1280px (desktop): PASS
1536px (ultrawide): WARN — content not centered, stretched too wide
Fix any issues found, then re-test the affected viewports.