← ArezCONTENT HISTORYWHAT CHANGED · RULE-BASED ANALYSIS
Update to Arez
Snapshot Sep 30, 2026 · 22:58 UTC · version 1.0.0
Collection source: not recorded for this historical snapshot.
First saved snapshot
No earlier snapshot is available to establish a change.
Compare saved observations
Download comparison JSONFull technical diff · 0 changed fields
Full snapshot data
{
"name": "building-mcp-apps",
"description": "Use when a Noodle Seed MCP App, widget, interactive card, visual interaction, or host-visible UI is the primary requested outcome.",
"included_files": [],
"skill_md_contents": "---\nname: building-mcp-apps\ndescription: \"Use when a Noodle Seed MCP App, widget, interactive card, visual interaction, or host-visible UI is the primary requested outcome.\"\n---\n\n<!-- noodle-skill version:0.62.1 hash:f7fa54992c8d7692 -->\n\n# building-mcp-apps\n\nDeliver an MCP App whose visual interaction earns its place and preserves useful model-visible fallback.\n\n## Use when\n\n- Build an MCP App or widget.\n- Add a host-visible interactive workflow.\n\n## Do not use when\n\n- Do not use when concise text fully serves the user.\n- Do not use for headless server work with no UI outcome.\n\n## Required inputs\n\n- Target user and explicit UI benefit.\n- Primary interaction and states.\n- Model-visible result and text fallback.\n\n## Workflow\n\nRead and follow the canonical playbook `references/build-an-mcp-app.md` at `../noodle-seed/references/build-an-mcp-app.md`. It owns the workflow; do not recreate it here or load the command catalog speculatively.\nLoad `references/experience-design.md` at `../noodle-seed/references/experience-design.md` only when the playbook or observed evidence names that concern.\nLoad `references/widgets-and-apps.md` at `../noodle-seed/references/widgets-and-apps.md` only when the playbook or observed evidence names that concern.\n\n## Verification evidence\n\nThe App passes validation, local smoke, app checks, and the requested preview or host evidence level.\n\n## Recovery paths\n\nDistinguish data-contract, widget-runtime, rendering, host, and deployment failures.\n\n## Stop conditions\n\nStop before deployment or publication unless that distinct outcome was requested.\n\n## Handoff contract\n\nPass the selected outcome, explicit target, changed files, commands run, passing evidence, first unproven evidence layer, sanitized failure, remaining authority, and exact next action. The receiving skill continues from that layer; do not restart discovery or discard prior proof.\n"
}SHA-256: def31dc04fdfb97ebe45a9a730cd4d263bf091ceb0072613db5540daec2a5b0d