Web Reference Research

Purpose

Convert taste references into concrete, verifiable design decisions.

Scoped execution

Apply the shared web contract once when execution crosses phases; reuse it if already read. Load only the specialist guidance relevant to the requested surface and deliverable.

Detailed Guide

Read web reference research guide for the selected workflow. Apply only the requested surface; review-only work reports findings, while authorized changes continue through implementation and relevant verification.

For item-level motion references, also read references/reconstruction-manifest.md and validate the research record with python3 "<skill-root>/scripts/verify-reference-record.py" <record.json>.

Scope and evidence

Resolve source fidelity mode before extraction. Exact authorized/supplied-source work preserves requested details; original work needs an originality delta. Motion-specific phase extraction belongs to $reference-motion-reconstruction. Empty unavailable-evidence is legitimate when nothing is missing.

For helper-driven evidence, use the typed record schema. The helper validates structure only; use actual inspection/test results for claims.

Resolve <skill-root> to this skill folder's actual absolute location; preserve project-local module resolution for Node capture tools.

Optional specialists

reference-motion-reconstruction is optional. Without it, use the bundled reconstruction-manifest guide to record observed phases, trigger, timing, responsive/reduced-motion behavior and missing evidence; do not invent unseen motion.