mismagent-run-app-smoke

Launches the app and records render-check evidence for UI blocks.

Updated Jun 12, 2026
One-click install
npx skills add https://github.com/lucolucus/mismagent --skill mismagent-run-app-smoke-lucolucus
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: mismagent-run-app-smoke
Source: https://github.com/lucolucus/mismagent/tree/main/codex/skills/mismagent-run-app-smoke
Command: npx skills add https://github.com/lucolucus/mismagent --skill mismagent-run-app-smoke-lucolucus

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Presenter tests can be fully green while real runtime UI bugs (clipped layouts, overflow, invisible controls) go undetected. This Skill closes that gap by actually launching the application and recording visual render evidence for each UI block, replacing an honor-system manual check with mechanized proof. ## Core Features & Use Cases - Real app launch: Starts the side's application using the active profile's sides.<side>.run command, respecting the configured toolchain, and refuses to fake proof when no run binding 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 smoke check to catch a clipped keypad or white-on-white button before the block is marked done, or run it across the whole slice before confirming a release. ## Quick Start Run the app smoke check on the current UI block and record the render evidence before marking it done.

Frequently Asked Questions about mismagent-run-app-smoke

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I verify UI rendering beyond unit tests?

Launch the real application with the profile's run command and walk each UI block's screens against a render checklist covering sizing, overflow, contrast, state rendering, and recomposition. Record screenshots or dated observation notes per checklist item as evidence.

What render bugs do presenter tests miss?

Presenter tests miss runtime layout bugs such as clipped keypads, wrapped rows, and invisible white-on-white buttons. These only surface when the actual app runs and screens are visually inspected against the render checklist.

What happens if the profile has no run command?

The check stops and reports NOT-RUNNABLE instead of faking proof. The render check stays owed, and the block cannot pass a manual ui_render_check until real evidence is recorded.

Where is the render proof evidence stored?

Evidence is written under <output_dir>/features/<feature>/render-proof/<block-id>/, with one screenshot or dated observation note per checklist item. The skill writes evidence only and never modifies app code or block state.

When should the render smoke check run in the workflow?

Run it at D1 of a UI block, where the worker-composer invokes it automatically when ui_render_check is manual and proof is missing, or across the whole slice before confirming the release.