Interactive demo
The public page covers input, pipeline, scoring, issues, recommendations, and backlog
Projects
An AI product prototype that turns page input into diagnosis and redesign backlog
A page analysis tool for product, marketing, and design discussions, using structured scoring and evidence-based recommendations to reduce subjective redesign debates.
Verifiable entry points
Public demo
Try the no-fetch-by-default Safe Mock flow, browser-side mock modes, and the structured result interface.
Try the public demoSource evidence
Review URL validation, capture limits, request gating, and Safe Mock result generation.
The public page covers input, pipeline, scoring, issues, recommendations, and backlog
Off by default; when enabled, every hop is pinned to a validated public IP with redirect, size, timeout, and global concurrency limits
Chinese root routes and English /en routes share one locale-aware client component
Asset status
Only repository-backed product mocks, public documentation, or an explicit no-public-image explanation appear here.
Asset type: Product mock
Asset type: Documentation
The public spec records URL validation, SSRF protection, error codes, output schema, and model boundaries.
Page redesign decisions often depend on personal taste and scattered comments, without a shared evidence chain tied to audience, business goals, and page structure.
URL mode does not request the target site by default and returns a controlled Safe Mock. An administrator can explicitly enable bounded public-HTML capture, but scores, issues, and backlog still come from the Safe Mock. Screenshot notes and briefs stay in the browser.
The client owns the three input modes and interaction state. URL mode calls a Next.js API for reproducible Safe Mock output without requesting the target by default. Only an explicit server flag enables bounded public capture; screenshot notes and briefs stay in the browser.
Step 01
One client experience owns URL, screenshot-note, and product-brief input plus pipeline state.
Step 02
URLs call POST /api/analyze; screenshot notes and briefs use the fixed client-side mock.
Step 03
Off by default; when enabled, the server resolves and pins every hop to a validated public IP, rejects private and metadata addresses, and bounds size, time, and concurrency.
Step 04
The URL, brief, and optional captured title feed deterministic scores, issues, recommendations, and backlog without calling a live model.
Step 05
The client presents progress, explicit failures, and structured delivery output.
Decision 01
Decision 02
Decision 03