Name: ui-evidence-screenshots
Author: yashdalal

Instruction file imported from yashdalal/options (.cursor/rules/ui-evidence-screenshots.mdc). Copyright stays with the author.

UI evidence — before/after screenshots

When changing user-visible UI (layout, styling, copy, sticky/scroll behavior, tables, trays, nav):

Before — capture screenshots (or a short video) of the current UI in the broken/prior state before editing.
After — capture the same views after the fix.
Prefer demo mode (DEMO_MODE=1) when live broker data is not required.
Store evidence under docs/pr-evidence/<issue-or-slug>/{before,after}/ as compressed JPEG when possible.
After the PR exists, label evidence with the PR number (filename and/or on-image badge, e.g. PR #57) and link those files in the PR body.
Include before/after images in the PR description — do not ship UI-only PRs without visual proof unless capture is impossible (then say why).

Do not skip this for “small” UI tweaks that change layout or scroll/sticky behavior.

# after Install: the listing is in your workspace's routing pool - a plan picks it for its slot curl -s -X POST https://api.opensmartroute.ai/api/v1/route -H 'Authorization: Bearer $OSR_API_KEY' -H 'Content-Type: application/json' -d '{"text": "...", "plan": true}'

Install ui-evidence-screenshots and it becomes one more candidate the router can pick - when it fits.

A listing is a routing target with a manifest: what it does, which domains it covers, what it costs and who publishes it. Once installed it sits beside your own models and tools, is scored like any other candidate for each request, and shows up in the trace when it wins. Ratings come from workspaces that installed it, one per account.

{ "ocm": "1", "id": "yashdalal-options-ui-evidence-screenshots-rule", "kind": "skill", "name": "ui-evidence-screenshots", "description": "Require before/after screenshots (with PR id) for UI changes", "publisher": "yashdalal", "version": "1.0.0", "capabilities": { "domains": [ "general" ], "tags": [ "skill-md", "github-cursor-rules" ], "languages": [ "en" ] }, "quality_prior": 0.6, "examples": [ "Require before/after screenshots (with PR id) for UI changes" ], "primary": false, "metadata": { "source": { "provider": "github-cursor-rules", "repository": "https://github.com/yashdalal/options", "path": ".cursor/rules/ui-evidence-screenshots.mdc", "ref": "b42661b15862d8e3aa5f4fa7709198e96923e34c", "url": "https://github.com/yashdalal/options/blob/b42661b15862d8e3aa5f4fa7709198e96923e34c/.cursor/rules/ui-evidence-screenshots.mdc", "key": "yashdalal/options/.cursor/rules/ui-evidence-screenshots.mdc" } }, "instructions": "# UI evidence — before/after screenshots\n\nWhen changing user-visible UI (layout, styling, copy, sticky/scroll behavior, tables, trays, nav):\n\n1. **Before** — capture screenshots (or a short video) of the current UI in the broken/prior state before editing.\n2. **After** — capture the same views after the fix.\n3. Prefer **demo mode** (`DEMO_MODE=1`) when live broker data is not required.\n4. Store evidence under `docs/pr-evidence/<issue-or-slug>/{before,after}/` as compressed JPEG when possible.\n5. After the PR exists, **label evidence with the PR number** (filename and/or on-image badge, e.g. `P", "cost": { "context_tokens": 218 } }

ui-evidence-screenshots

About

UI evidence — before/after screenshots

Use it

Install ui-evidence-screenshots and it becomes one more candidate the router can pick - when it fits.

Manifest

Reviews