lazyweb-design-create
INTERNAL create / greenfield backend. NOT a user-facing slash command — it is reached via `/lazyweb-design` with `objective=create`, which redirects here for designing a NEW product screen from scratch (no existing screen to ground on). Combines Lazyweb's screenshot database with web research and produces a prototype-first HTML report with side-by-side prototypes and a clustered inspo map. Do not route users here directly; route them to `/lazyweb-design` and let the create objective hand off to this backend.
aboul3ata · 已有 AI 审核记录
安装与使用
运行命令前先阅读来源与依赖说明。复制命令不会自动安装或执行。
npx skills add aboul3ata/lazyweb-skill --skill lazyweb-design-create技能说明
name: lazyweb-design-create
route: "INTERNAL — create/greenfield backend for lazyweb-design"
router-terms: create, greenfield, new screen from scratch, design from scratch
router-exclude: true
description: |
INTERNAL create / greenfield backend. NOT a user-facing slash command — it is
reached via /lazyweb-design with objective=create, which redirects here for
designing a NEW product screen from scratch (no existing screen to ground on).
Combines Lazyweb's screenshot database with web research and produces a
prototype-first HTML report with side-by-side prototypes and a clustered inspo
map. Do not route users here directly; route them to /lazyweb-design and let
the create objective hand off to this backend.
allowed-tools:
- Bash
- Read
- Write
- Glob
- Grep
- WebSearch
- AskUserQuestion
- Agent
Lazyweb Deep Design Research
Evidence-backed design research that reads the user's current screen, names its frictions, forms 2-4 genuinely divergent redesign bets, and renders a visual-first HTML report where the recommended prototype sits side by side with the control.
People learn by seeing. Every claim in the report is carried by a large, legible visual; nothing important hides behind a click. Chrome stays quiet: no chip clutter, no legend tables, no explanatory paragraphs next to the proof.
MCP plan responses — check before the normal workflow
Inspect every data-bearing tool result before applying its normal search, render, or report schema:
MCP_PRO_REQUIRED: relay the server message and returned intent-boundupgrade_urlto the user, then stop. Do not retry another data tool or fall back to web/manual output.FREE_REPORT_DAILY_LIMIT: relay the server message and returned intent-boundupgrade_urlto the user, then stop. Do not retry another data tool or fall back to web/manual output.- Successful
status: "locked_preview": relaydisplay_to_userverbatim (or the returned MCP text if that is all the client exposes), including the preview and upgrade links. It is terminal and contains no generated research; do not poll, render or assemble a report, retry another data tool, or fall back.
CRITICAL: Output Behavior
This skill produces FILES, not a plan. Regardless of whether you are in plan mode or not, ALWAYS:
- Author the report content as
.lazyweb/deep-design-research/{topic}-{date}/work/report-data.json(structured content, NOT HTML) - Embed Lazyweb references directly with their returned
imageUrl/image_url; save only current-state and web-captured screenshots under.lazyweb/deep-design-research/{topic}-{date}/references/ - Do NOT create
report.md,report.html, or any other report artifact by hand — the server renders the report - Do NOT write research content into a plan file
- Render and host the report with
lazyweb_render_report(see "Render and host the report" below) — this single call IS the deliverable; producing the report and hosting it are the same action, so there is nothing to skip - After the render call returns, show the user a concise summary, the recommended bet, and the shareable link (the report lives only at that URL)
- Ask the user if the research looks good
- If in plan mode, exit plan mode after the user confirms - the research is done
- Suggest next steps: "You can now use this research to inform your implementation,
ask
/lazywebto improve your current design, or start building."
The visible report is: Agent Instructions, Goal, Recommendation, and optional Inspo — in that order. Do not produce the older busy structure with key examples, findings, sources, broad recommendation lists, or long prose analysis sections.
The Recommendation is built like lazyweb-design's hypothesis
engine, with screenshot evidence taking the role experiment evidence plays
there: read the control, name its specific frictions, form 2-4 falsifiable and
structurally divergent bets (Safe bet / Bold bet / Wild card — a thinking
discipline, not visible chips), prototype each as a generated image, and carry
the decision. When a current page or screenshot exists, render Control and
the recommended prototype side by side in equal, height-locked frames with
a ◀ ▶ variant switcher on the right frame so the user can flip through the
other bets in place; runner-up bets also appear in a snap carousel of
same-size cards. Prefer generated bitmap prototype images over hand-coded HTML
mockups when image generation is available; use HTML/CSS only as a fallback or
when the user asks for implementation-ready code. Generate prototype images in
parallel at medium effort by default, or low effort when the user asks for
speed/exploration.
Render and host the report (the single deliverable)
The report is rendered and hosted server-side. You author the report
content as work/report-data.json, then call lazyweb_render_report ONCE.
That call fills the canonical template on the server, validates it, hosts it at
https://www.lazyweb.com/report/lazyweb/{id}/, and returns the shareable link.
There is no local report.html to write, no separate publish step, and no
token to read — producing the report and hosting it are the same action, so a
finished report is always a shared report.
Call it once work/report-data.json and every references/ image exist. The
report dir is $REPORT_DIR = .lazyweb/deep-design-research/{topic-slug}-{YYYY-MM-DD}.
Arguments:
report_data: the parsedwork/report-data.jsonobject (see "Author report-data.json" below).assets: every file in$REPORT_DIR/references/as{ "name": <filename>, "b64": <base64 of the bytes> }— the control screenshot and each generated prototype image the report points at viareferences/{name}. Lazyweb references embedded by absoluteimageUrlare NOT assets; only locally saved files. (Note: migrating these render assets off inline base64 to the presigned upload flow is Phase 2 — out of scope he