More screenshots
Works with the AI Agents you already use
UI Finish Pass — Polish One Screen
Polish one existing screen, keep its design language and behavior, and compare the result at compact and wide sizes.
Free
UI Finish Pass — Polish One Screen
Example session with this skill installed
Polish this Parcel Studio delivery card. Keep its typography, colors and actions, and make the spacing and hierarchy clearer on phones and desktop. Check ordinary and long delivery descriptions.
- Read your context and instructions
- Compiled the ui finish pass
Delivery card finish — synthetic task result
Updated styles.css with a local responsive width, clearer content spacing and aligned action spacing. The component factory and original application entrypoint are unchanged. Existing colors and system typography are preserved; no animation was added.
| Same input / viewport | Before document width | After document width | Observed result |
|---|---|---|---|
| Ordinary text / 390 × 844 | 436px | 390px | Card fits; right edge changes from 436px to 374px |
| Long description / 390 × 844 | 436px | 390px | Full description wraps; both actions remain visible |
| Ordinary text / 1280 × 900 | 1280px | 1280px | Card retains its 420px desktop width |
| Long description / 1280 × 900 | 1280px | 1280px | Text and actions remain accessible |
An additional 320px case with a long title and unbroken reference fits the page after the patch. Pointer and Enter activation both produce the original local tracking feedback. Tab order remains the action button followed by Delivery help; visible focus remains. Loading and empty phases ignore disabled-action activation; the error phase still invokes its Try again callback.
Deliverables: the focused CSS patch, repeatable ordinary/long/stress fixture URLs, paired compact/wide screenshots, geometry observations and behavior receipts. These observations come from a fictional vanilla-JavaScript task trial. They cover these inputs and checks, not every framework, accessibility criterion or production condition. No conversion or time-saving result was measured.
Next action: review the paired screenshots and apply the focused patch to the supplied surface; broaden coverage only where the actual product requires it.
Connects securely to your tools. The creator never sees your data.
About this skill
Your screen works, but the details compete: cramped spacing, heavy surfaces, uneven icons or motion that gets in the way.
UI Finish Pass helps your coding agent turn those visible problems into a focused patch. It reads the screen's existing components and tokens, chooses local changes, and repeats the same states and viewports after editing. Your product keeps its identity while the finish becomes more coherent.
You get the source changes, a short before/after explanation, matching screenshots when rendering is available, and a record of the actions, keyboard path and states checked. Long content and compact widths are included in the comparison. Motion changes also get a reduced-motion check.
What you supply
- The screen or component to polish, with source access.
- A working local preview and representative data or fixtures for visual verification.
- Your existing design conventions and any behavior that must be preserved.
The host coding agent needs file-editing and project-command tools. Capturing and checking the rendered result also requires a browser. Use the project's established setup; this package adds no runtime dependency or hosted service.
Use it
“Use UI Finish Pass on the account settings card. Keep our typography, colors and actions. Make the spacing and hierarchy clearer, then compare normal and long content at compact and wide sizes.”
Scope and limits
This is a focused pass on an existing surface. A shared design-system refactor or whole-application audit needs a broader task. If the preview cannot run, the result identifies source-level proposals and the visual checks still needed. Its evidence covers the states actually inspected; it does not establish conversion gains, time savings or comprehensive accessibility compliance.
Included
- A concise
SKILL.mdworkflow. - A decision reference for common visible finish problems.
- Source attribution and an MIT license for the original package.
Worked example
In a retained synthetic Parcel Studio trial, the 390px phone page changed from 436px of content width to 390px, while the checked actions and keyboard path continued to work. Ordinary and long content were compared at 390 × 844 and 1280 × 900. This is a local fictional example, not measured customer impact.
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 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
Fresh listing
Recently published to Agensi
Free forever
No account required to browse
Trust & safety
Security scan
Security scan passed 19 days ago
- Free with an Agensi account
Requires
Permissions
Local project source and fictional fixtures. Browser network access is limited to the local preview; no production service, credentials or external account is required. Changes the requested screen/component source.