verify-ui
Automate repetitive workflows and reduce manual effort
Example: Generate reports, summarize documents, draft communications
Save 3-5 hours per week on routine tasks
Learn new skills, understand complex topics, get expert guidance
Example: Explain concepts, provide examples, suggest learning resources
Accelerate learning and skill development by 2x
Enhance output quality through reviews, suggestions, and refinements
Example: Review drafts, suggest improvements, catch errors
Improve work quality by 30-40% with less effort
Time estimate: 15-45 minutes depending on use case complexity
Prerequisites
Submit your Claude Code skill and start earning
epx add whyashthakker/estack --skill verify-uiCompatible with
Supported agents
Check a UI change in a real browser before calling it done.
Starts or finds the dev server, opens the changed pages, takes screenshots at phone and desktop widths in light and dark mode, reads console errors, and looks for layout bugs that typecheck and curl miss.
Use after any change to pages, components, or styles, or when the user says "check it visually", "screenshot it", "does it look right", or "verify the UI".
| name | verify-ui |
| description | Check a UI change in a real browser before calling it done. Starts or finds the dev server, opens the changed pages, takes screenshots at phone and desktop widths in light and dark mode, reads console errors, and looks for layout bugs that typecheck and curl miss. Use after any change to pages, components, or styles, or when the user says "check it visually", "screenshot it", "does it look right", or "verify the UI". |
Goal: you saw the change working before the user does. A clean typecheck does not prove a page looks right.
package.json scripts, README). If a dev server already runs, use it. Do not start a second one on another port without telling the user.Use what the session has: Playwright, a browser automation tool, or a headless browser script. For each route take screenshots at:
Read every screenshot. Do not only save it.
Fix what you found, take new screenshots, and compare. Stop after three rounds and report what remains.
Pages checked, widths and modes, the problems found and fixed, and anything still open. Attach or link the final screenshots. Delete temporary screenshots that are not useful to keep, and never commit them unless asked.
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versionverify-uiExecute the skills CLI command in your project's root directory to begin installation:
epx add whyashthakker/estack --skill verify-uiFetches verify-ui from whyashthakker/estack and configures it for Cursor.
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Confirm successful installation by checking the skill directory location:
.cursor/skills/verify-ui
Restart Cursor to activate verify-ui. Access via /verify-uiin your agent's command palette.
Learn more:View source on GitHubSkills CLI docsAbout CursorWhat are agent skills?
Steps
Common Pitfalls
✓ Do
✗ Don't
💡 Pro Tips
✓ Use when
Use when skill capabilities match your task, clear ROI on time saved, and you can validate outputs. Best for repetitive tasks, learning, and quality improvement.
✗ Avoid when
Avoid when task requires deep expertise you can't validate, involves sensitive decisions, or when learning process is more valuable than speed of completion.
I recommend verify-ui for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
verify-ui fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
verify-ui is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
Keeps context tight: verify-ui is the kind of skill you can hand to a new teammate without a long onboarding doc.
Solid pick for teams standardizing on skills: verify-ui is focused, and the summary matches what you get after install.
Registry listing for verify-ui matched our evaluation — installs cleanly and behaves as described in the markdown.
We added verify-ui from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
verify-ui has been reliable in day-to-day use. Documentation quality is above average for community skills.
verify-ui reduced setup friction for our internal harness; good balance of opinion and flexibility.
Registry listing for verify-ui matched our evaluation — installs cleanly and behaves as described in the markdown.
showing 1-10 of 70