Launches the app and records render-check evidence for UI blocks.
npx skills add https://github.com/lucolucus/mismagent --skill run-app-smoke-lucolucus
Please help me install this Agent Skill. Skill: run-app-smoke Source: https://github.com/lucolucus/mismagent/tree/main/plugins/mismagent/skills/run-app-smoke Command: npx skills add https://github.com/lucolucus/mismagent --skill run-app-smoke-lucolucus
run binding, and refuses to fake the proof when no run command exists. - Render Checklist Walkthrough: Applies realize-ui's five-point checklist (sizing, overflow, contrast/visibility, state rendering, recomposition) to each UI block's screens. - Recorded Evidence: Writes screenshots or dated observation notes per checklist item into <output_dir>/features/<feature>/render-proof/<block-id>/, producing the proof the verifier's step 8 requires for a manual ui_render_check. - Use Case: At D1 of a UI block, run the app, walk the block's screens, and record a RENDER-OK verdict with evidence — or a RENDER-FAIL with named findings routed back to the worker for rework. ## Quick Start Run the app for this feature and record the render proof for all UI blocks before I confirm the release.High-intent search queries and answers about installing and using this skill.
Launch the real application with the profile's run command and walk each screen against a render checklist covering sizing, overflow, contrast, state rendering, and recomposition. Record screenshots or observation notes per item as evidence of what was actually seen.
A render proof is recorded evidence that a UI block's screens were checked in the running app against the realize-ui checklist. It lives under the feature's render-proof directory and is what the verifier accepts for a manual ui_render_check.
The skill stops and reports NOT-RUNNABLE instead of faking the proof. The render check stays owed, and the block cannot pass a manual ui_render_check until the app can actually be launched and evidenced.
No, it proves rendering only. Presenter behavior is covered by the worker's tests and acceptance-criteria coverage is the verifier's job, so the skill deliberately avoids duplicating those checks.
Run it at D1 of a UI block, where the worker-composer invokes it when the side's ui_render_check is manual and proof is missing, or across the whole slice before confirming the release.
AppsVortexGenerate multiple visual-direction briefs with CSS variables and manifests for UI sketches.
GonkaGateAudits repository compatibility against the latest stable upstream hermes-agent release and official docs.
timcsyWrite human-executable acceptance checklists for requirements that cannot be tested automatically.
TeamSloppyAutomate UI visual verification with screenshot capture and visual diff comparisons.