Web Reference
Core Principle
A rendered website is evidence. The current project's requirements and runtime
behavior remain acceptance authority. Capture only what answers the active
question, preserve provenance, and separate observed facts from adoption choices.
When to Use / NOT
- Use when: the user provides visual inspiration, design direction needs
evidence, or implementation depends on current rendered behavior.
- NOT when: project source already answers the question, the task is backend
only, or a normal web search is sufficient.
Workflow
- Inspect the current project's tokens, components, accessibility rules, and
requirements first.
- Choose the smallest useful capture mode from
references/capture.md.
- Capture through available native HTTP or browser capabilities. Respect auth,
rate limits, destructive-route exclusions, and the user's authorized session.
- Store source URL, capture time, scope, paths, and known gaps in
manifest.json; keep REFERENCE.md concise and evidence-linked.
- Inspect the manifest with native JSON and filesystem tools. Confirm exact
field types, enum values, path containment, referenced files, and credential
hygiene. The optional
web-reference-manifest.py maintainer tool checks only
these hard contracts.
- Judge coverage and trust from the actual question and evidence. Record ADOPT,
ADAPT, or OMIT only when implementation makes that decision.
- Verify resulting work in the browser and against project tests.
Red Flags
- Unbounded crawling, auth bypass, destructive routes, or stored credentials.
- Treating a scope label as proof that evidence is sufficient.
- Mechanically deciding trust, visual quality, or ADOPT / ADAPT / OMIT.
- Copying brand assets or promoting a capture automatically.
Verification
The manifest parses; declared paths stay inside the bundle and exist; capture
identity and credentials satisfy the exact contract. The model separately
reports substantive coverage, evidence limits, and implementation decisions.
References
references/capture.md, capture modes and capability ladder.references/scope.md, crawl boundaries and exclusions.references/extraction.md, DOM and style extraction.references/media.md, media roles and provenance.references/storage.md, bundle structure and manifest fields.
1---2name: web-reference3description: Use when a live website or web page should be captured and studied as frontend, visual, layout, interaction, or design-system prior art for implementation.4---56# Web Reference78## Core Principle910A rendered website is evidence. The current project's requirements and runtime11behavior remain acceptance authority. Capture only what answers the active12question, preserve provenance, and separate observed facts from adoption choices.1314## When to Use / NOT1516- **Use when:** the user provides visual inspiration, design direction needs17 evidence, or implementation depends on current rendered behavior.18- **NOT when:** project source already answers the question, the task is backend19 only, or a normal web search is sufficient.2021## Workflow22231. Inspect the current project's tokens, components, accessibility rules, and24 requirements first.252. Choose the smallest useful capture mode from `references/capture.md`.263. Capture through available native HTTP or browser capabilities. Respect auth,27 rate limits, destructive-route exclusions, and the user's authorized session.284. Store source URL, capture time, scope, paths, and known gaps in29 `manifest.json`; keep `REFERENCE.md` concise and evidence-linked.305. Inspect the manifest with native JSON and filesystem tools. Confirm exact31 field types, enum values, path containment, referenced files, and credential32 hygiene. The optional `web-reference-manifest.py` maintainer tool checks only33 these hard contracts.346. Judge coverage and trust from the actual question and evidence. Record ADOPT,35 ADAPT, or OMIT only when implementation makes that decision.367. Verify resulting work in the browser and against project tests.3738## Red Flags3940- Unbounded crawling, auth bypass, destructive routes, or stored credentials.41- Treating a scope label as proof that evidence is sufficient.42- Mechanically deciding trust, visual quality, or ADOPT / ADAPT / OMIT.43- Copying brand assets or promoting a capture automatically.4445## Verification4647The manifest parses; declared paths stay inside the bundle and exist; capture48identity and credentials satisfy the exact contract. The model separately49reports substantive coverage, evidence limits, and implementation decisions.5051## References5253- `references/capture.md`, capture modes and capability ladder.54- `references/scope.md`, crawl boundaries and exclusions.55- `references/extraction.md`, DOM and style extraction.56- `references/media.md`, media roles and provenance.57- `references/storage.md`, bundle structure and manifest fields.
ryan-brosas