## 1. Define entry points, scope and stopping conditions

Read site-fixture.json and create scope.md: entries, internal links, images, anchors and planned evidence. Separate file inspection from real HTTP checks. Do not access external sites, submit forms, log in or edit pages.

Expected: A page/resource/anchor plan.
Check: Scope does not expand; evidence origins are explicit.

## 2. Extract every referenced target from source

Using uploaded HTML/resource lists only, map href, src and fragment targets. Check resource presence and actual ids, retaining source snippets. Label results simulated; do not claim network requests or read expected-findings.csv yet.

Expected: Source → target → evidence mapping.
Check: Pricing, banner and contact can be located in source; external links are not followed.

## 3. Verify status and rendering where accessible

Only in a confirmed accessible local environment, check scoped fixture targets read-only. Record HTTP status and browser evidence for missing image/anchor. Distinguish404, network, authentication and content errors with URLs/times. If inaccessible, analyze uploaded files and state the limit.

Expected: Dated actual evidence or an access blocker.
Check: HTTP200 is not site health; simulation and actual requests remain separate.

## 4. Report faults, impact and unchecked scope

Write scope, normal items, issues, unchecked areas, evidence and recheck methods. Each issue needs source page, target, observation, possible impact and minimal suggestion. Do not estimate revenue loss or assert causes without evidence. Do not edit/deploy.

Expected: A report with three intentional issues.
Check: Each finding has an evidence type and reproducible target.

## 5. Review repair intent and recheck the same list

Propose minimum repairs with files/targets, missing correct addresses/assets and rechecks. Ask for missing evidence instead of deleting links or changing production. Implement only after later specific authorization and validate the same targets.

Expected: Three repairs with matching rechecks.
Check: Suggestions preserve the original purpose and are not called completed repairs.

## 6. Save the method and notify on differences

Draft a site-check Skill with authorized scope, read-only checks, limits, timeouts/rate limits, evidence, diffs and recovery notices. Propose once-daily Routine with user-confirmed time zone only. Stay quiet unchanged; report inability to inspect. Do not edit, open PRs, deploy or contact Bots.

Expected: A reusable inspection method and schedule proposal.
Check: Each run has a new timestamp; no-change, failure and recovery differ.