# Lazyweb Lite Design Research > Find app screenshots and UI references quickly. Embeds Lazyweb results by storage-backed URL and groups them by pattern. Use when the user wants to see examples of a specific screen, UI element, or flow without a full research report. Trigger on: "show me examples of", "how do other apps do", "design inspiration for", "UI reference for", "what does X's app look like", "find screenshots of", "show me how", "references for". - Skill: `igrlebed/lazyweb-lite-design-research` (Agent Skill) - Install (CLI): `npx skillmds@latest add igrlebed/lazyweb-lite-design-research` - Raw SKILL.md: https://api.skillmd.com/api/skills/igrlebed/lazyweb-lite-design-research/raw - Safety review: pending - Works with: Claude Code, Claude.ai, OpenAI Codex - Category: Docs & Writing - Author: igrlebed (https://skillmd.com/u/igrlebed) - Updated: 2026-09-21 - Page: https://skillmd.com/skills/igrlebed/lazyweb-lite-design-research --- # Lazyweb Lite Design Research Find real app screenshots fast, embed Lazyweb images by URL, and group by pattern. Lighter than deep design research — no competitive analysis, no anti-patterns. Just find → group → show. ## CRITICAL: Output Behavior **This skill produces FILES, not a plan.** Regardless of whether you are in plan mode or not, ALWAYS: 1. Write the HTML report to `.lazyweb/lite-design-research/{topic}-{date}/report.html` 2. Embed Lazyweb references directly with their returned `imageUrl`/`image_url`; save only current-state and web-captured screenshots under `.lazyweb/lite-design-research/{topic}-{date}/references/` 3. Do NOT create `report.md` or any other Markdown report artifact 4. Do NOT write research content into a plan file 5. Publish a shareable link (see "Publish a Shareable Link" below) — automatic, non-blocking 6. After saving, show the user a summary, where the files are, and the shareable link if publishing succeeded 7. Ask the user if the references look good 8. If in plan mode, exit plan mode after the user confirms 9. Suggest next steps: "You can now use these references to inform your design, ask `/lazyweb` for deeper design research, or start building." ## Publish a Shareable Link (always, right after writing report.html) Every report is auto-published to lazyweb.com so the user can share it with teammates. Run this with `$REPORT_DIR` set to `.lazyweb/lite-design-research/{topic}-{date}`: ```bash IDEMPOTENCY_KEY="${REPORT_DIR#.lazyweb/}" # stable per-report key (e.g. lite-design-research/{topic}-{date}); send the SAME value every attempt so retries dedupe to one link LAZYWEB_TOKEN=$(cat "$HOME/.lazyweb/lazyweb_mcp_token" 2>/dev/null || true) if [ -n "$LAZYWEB_TOKEN" ]; then # Tier 1 - local install: direct POST (idempotency_key dedupes a re-run) python3 - "$REPORT_DIR" "$LAZYWEB_TOKEN" "lite-design-research" "$IDEMPOTENCY_KEY" <<'PUBLISH_EOF' import base64, json, pathlib, sys, urllib.error, urllib.request report_dir, token, skill, idem = pathlib.Path(sys.argv[1]), sys.argv[2], sys.argv[3], sys.argv[4] version_file = pathlib.Path.home() / ".lazyweb" / "VERSION" version = version_file.read_text().strip() if version_file.exists() else "0.0.0" html = (report_dir / "report.html").read_text(encoding="utf-8") refs = report_dir / "references" assets = [ {"name": p.name, "b64": base64.b64encode(p.read_bytes()).decode()} for p in (sorted(refs.iterdir()) if refs.is_dir() else []) if p.is_file() ] body = json.dumps({"skill": skill, "version": version, "html": html, "assets": assets, "idempotency_key": idem}).encode() req = urllib.request.Request( "https://www.lazyweb.com/api/reports", data=body, headers={"Content-Type": "application/json", "Authorization": f"Bearer {token}"}, ) try: resp = json.loads(urllib.request.urlopen(req, timeout=90).read()) print(f"SHAREABLE_URL: {resp['url']}") except urllib.error.HTTPError as exc: print(f"PUBLISH_FAILED: {exc.code} {exc.read().decode()[:500]}") except Exception as exc: print(f"PUBLISH_SKIPPED: {exc}") PUBLISH_EOF else # Tier 2 - no local token (hosted/cloud agent): publish via the MCP tool (see below) echo "PUBLISH_VIA_MCP_TOOL idempotency_key=$IDEMPOTENCY_KEY report_dir=$REPORT_DIR" fi ``` **Exactly one tier runs - never both.** - Tier 1 `SHAREABLE_URL:` - include the link: "Shareable link: {url} (unlisted - anyone with the link can view)". - Tier 1 `PUBLISH_FAILED: 400 ...` - the body names what is unhostable (e.g. `missing_assets`). Fix the report and re-run the publish ONCE. - Tier 1 `PUBLISH_SKIPPED:` - say nothing; the local report stands (the user has the file). - Tier 2 `PUBLISH_VIA_MCP_TOOL ...` - you have no local token (hosted session), so publish with the Lazyweb MCP tool instead: 1. Size-check first: if `report.html` plus the `references/` files together exceed ~7MB, do NOT call the tool - tell the user the report was too large to publish from a hosted session (it is saved locally) and stop. 2. Otherwise call `lazyweb_publish_report` with: `html` = the contents of `report.html`; `assets` = each `references/` file as `{"name": , "b64": }`; `report_skill` = "lite-design-research"; `idempotency_key` = the value printed after `idempotency_key=`. 3. On `{ ok: true, url }` -> show "Shareable link: {url} (unlisted - anyone with the link can view)". 4. On `{ ok: false }` -> tell the user publishing failed and why (the `error` field); the report is saved locally. If `code` is `REPORT_VALIDATION_ERROR` and `detail` names missing assets, fix and call ONCE more; otherwise do not retry. Unlike Tier 1, do NOT stay silent on a Tier-2 failure - a hosted user has no local file to fall back on, so they need the link or the reason. ### Hosting-safe HTML (the template already complies — keep it that way) The hosted copy is served byte-for-byte, so the report must only use: - inline CSS and inline `