# Website launch prompt pack Morten A. Giraffe · Website launch field guide https://www.mortenagiraffe.com/journal/website-launch-checklist Fill in the scope and supply redacted evidence. Choose the prompt for the decision you need to make. ## Investigate a launch check Work in [site or repository] using [stack], limited to [approved pages or features]. Read the project instructions first. Use synthetic inputs and redact personal data and credentials. Ask before any live submission, provider change, push or deployment. Investigate check [number] on [representative route]. Name the visitor’s task and the expected behavior. Trace the actual implementation and reproduce the suspected failure locally. Use existing evidence when it covers the same build and behavior. Return the observed symptom, reproduction steps, relevant file or URL, and the limits of the test. Mark the check verified, partial, unverified or not applicable and explain why. ## Repair a confirmed issue Work in [site or repository] using [stack], limited to [approved pages or features]. Read the project instructions first. Use synthetic inputs and redact personal data and credentials. Ask before any live submission, provider change, push or deployment. Use the confirmed finding for check [number] and its reproduction [evidence]. Make the smallest local fix in [approved files]. Follow the existing design and validation patterns. Preserve consent, form data, error recovery and working navigation. Repeat the original reproduction and one nearby success or failure case. Report changed files, commands, results and a specific rollback step. Identify any release or operator decision still needed. ## Verify the release evidence Work in [site or repository] using [stack], limited to [approved pages or features]. Read the project instructions first. Use synthetic inputs and redact personal data and credentials. Ask before any live submission, provider change, push or deployment. Review [candidate build or commit] against the approved launch checks. Identify the environment and sample for each claim. Compare the built page with the expected behavior using authorized read-only requests or local fixtures. Record a fresh result when the change invalidates old evidence. Return a table with check number, status, actual result, evidence, known limit and next owner. Distinguish local results, preview behavior, deployment state and observed production behavior. Leave any unapproved live verification open. ## 1. Trace one submission through the privacy policy Work in [site or repository] using [stack], limited to [approved pages or features]. Read the project instructions first. Use synthetic inputs and redact personal data and credentials. Ask before any live submission, provider change, push or deployment. Trace one synthetic form’s fields through the code without sending it. Compare the recipients, purpose, retention and contact details with the policy. List any fact only the operator can confirm. Return a read-only finding with the page or file, what you observed, what remains unknown and the smallest justified change. ## 2. Measure the image that actually arrives Work in [site or repository] using [stack], limited to [approved pages or features]. Read the project instructions first. Use synthetic inputs and redact personal data and credentials. Ask before any live submission, provider change, push or deployment. Compare one hero and one thumbnail at two widths. Trace currentSrc, rendered size, device pixel ratio, format and cold-cache transfer bytes. Suggest a change only where delivery or visible quality warrants it. Return a read-only finding with the page or file, what you observed, what remains unknown and the smallest justified change. ## 3. Make the terms fit the actual offer Work in [site or repository] using [stack], limited to [approved pages or features]. Read the project instructions first. Use synthetic inputs and redact personal data and credentials. Ask before any live submission, provider change, push or deployment. Compare the actual forms, tools, downloads and payment paths with the terms. Flag unsupported promises or missing usage boundaries. Identify which decisions require the owner or legal advice. Return a read-only finding with the page or file, what you observed, what remains unknown and the smallest justified change. ## 4. Separate a slow test from a slow audience Work in [site or repository] using [stack], limited to [approved pages or features]. Read the project instructions first. Use synthetic inputs and redact personal data and credentials. Ask before any live submission, provider change, push or deployment. Read existing lab and field reports. For the slowest page, name the LCP element and its critical requests. Separate field data from lab metrics and propose one reproducible comparison. Return a read-only finding with the page or file, what you observed, what remains unknown and the smallest justified change. ## 5. Inspect what ships to the browser Work in [site or repository] using [stack], limited to [approved pages or features]. Read the project instructions first. Use synthetic inputs and redact personal data and credentials. Ask before any live submission, provider change, push or deployment. Trace one privileged integration from its form to its server entry point. Inspect environment variable names and scan the built client files with values redacted. If a candidate appears, report its location without printing or testing it. Return a read-only finding with the page or file, what you observed, what remains unknown and the smallest justified change. ## 6. Read the quietest text on its real background Work in [site or repository] using [stack], limited to [approved pages or features]. Read the project instructions first. Use synthetic inputs and redact personal data and credentials. Ask before any live submission, provider change, push or deployment. Inspect the least prominent text on the approved pages. Capture its actual foreground and background, size, state and unrounded contrast ratio. Identify an existing color treatment that would correct any measured failure. Return a read-only finding with the page or file, what you observed, what remains unknown and the smallest justified change. ## 7. Follow the request all the way to HTTPS Work in [site or repository] using [stack], limited to [approved pages or features]. Read the project instructions first. Use synthetic inputs and redact personal data and credentials. Ask before any live submission, provider change, push or deployment. Trace the HTTP-to-HTTPS redirect for one approved public URL. Inspect static and runtime resource schemes on a representative template, including the form action without submitting it. Report the originating file for any insecure request. Return a read-only finding with the page or file, what you observed, what remains unknown and the smallest justified change. ## 8. Finish the task with less room Work in [site or repository] using [stack], limited to [approved pages or features]. Read the project instructions first. Use synthetic inputs and redact personal data and credentials. Ask before any live submission, provider change, push or deployment. Walk the primary task at a narrow viewport with a keyboard. Inspect overflow, touch target spacing, error visibility, menu focus and Escape return. Record which native-device or zoom checks remain open. Return a read-only finding with the page or file, what you observed, what remains unknown and the smallest justified change. ## 9. Try every consent choice in a clean session Work in [site or repository] using [stack], limited to [approved pages or features]. Read the project instructions first. Use synthetic inputs and redact personal data and credentials. Ask before any live submission, provider change, push or deployment. Compare consent copy with local intercepted traffic and storage before a choice, after decline, after allow and after withdrawal. Check delayed sends and cross-tab behavior. Identify exactly what a choice counter represents. Return a read-only finding with the page or file, what you observed, what remains unknown and the smallest justified change. ## 10. Give a lost visitor a real way back Work in [site or repository] using [stack], limited to [approved pages or features]. Read the project instructions first. Use synthetic inputs and redact personal data and credentials. Ask before any live submission, provider change, push or deployment. Check one nonexistent path and one known moved path. Record each HTTP chain, visible recovery option and destination. Distinguish an intentional 404 from an incorrect success response. Return a read-only finding with the page or file, what you observed, what remains unknown and the smallest justified change. ## 11. Tell similar pages apart in a search result Work in [site or repository] using [stack], limited to [approved pages or features]. Read the project instructions first. Use synthetic inputs and redact personal data and credentials. Ask before any live submission, provider change, push or deployment. Compare the title, description and heading across three page types. Flag duplication or misleading copy and propose a distinct description that fits the page and the team’s stated budget. Return a read-only finding with the page or file, what you observed, what remains unknown and the smallest justified change. ## 12. Follow links to the promised destination Work in [site or repository] using [stack], limited to [approved pages or features]. Read the project instructions first. Use synthetic inputs and redact personal data and credentials. Ask before any live submission, provider change, push or deployment. Follow a bounded sample of internal links and fragments. Verify the final page and visible target, including after client rendering where needed. Separate confirmed broken links, redirects and unavailable external checks. Return a read-only finding with the page or file, what you observed, what remains unknown and the smallest justified change. ## 13. Read the page as a link preview Work in [site or repository] using [stack], limited to [approved pages or features]. Read the project instructions first. Use synthetic inputs and redact personal data and credentials. Ask before any live submission, provider change, push or deployment. Inspect one shareable page’s returned Open Graph metadata and image response. Compare the artwork at card size with the visible page. State which platform-specific previews were actually checked. Return a read-only finding with the page or file, what you observed, what remains unknown and the smallest justified change. ## 14. Make a failed form worth retrying Work in [site or repository] using [stack], limited to [approved pages or features]. Read the project instructions first. Use synthetic inputs and redact personal data and credentials. Ask before any live submission, provider change, push or deployment. Identify the essential delivery for one form. With fixture recipients, inspect client-invalid, server-invalid, delivery-failure, partial-success and retry paths. Verify focus, retained values and send counts. Return a read-only finding with the page or file, what you observed, what remains unknown and the smallest justified change. ## 15. Look at the icon at tab size Work in [site or repository] using [stack], limited to [approved pages or features]. Read the project instructions first. Use synthetic inputs and redact personal data and credentials. Ask before any live submission, provider change, push or deployment. Trace the declared favicon family to the actual files. Check the smallest icon and a larger square at native size. If a size is missing, identify the approved source and existing generation path. Return a read-only finding with the page or file, what you observed, what remains unknown and the smallest justified change. ## 16. Test abuse protection and a genuine retry Work in [site or repository] using [stack], limited to [approved pages or features]. Read the project instructions first. Use synthetic inputs and redact personal data and credentials. Ask before any live submission, provider change, push or deployment. Map the form’s rate limit, duplicate marker and outage behavior. Use local stubs for timing, repeated requests and delivery failures. Report whether a legitimate retry reaches the essential send. Return a read-only finding with the page or file, what you observed, what remains unknown and the smallest justified change. ## 17. List the pages you actually want discovered Work in [site or repository] using [stack], limited to [approved pages or features]. Read the project instructions first. Use synthetic inputs and redact personal data and credentials. Ask before any live submission, provider change, push or deployment. Compare intended public routes with the sitemap, robots rules, canonical tags and index directives. Inspect a small representative sample. Explain each intentional omission and keep actual indexing observations separate. Return a read-only finding with the page or file, what you observed, what remains unknown and the smallest justified change. ## 18. Count the outcome the report claims Work in [site or repository] using [stack], limited to [approved pages or features]. Read the project instructions first. Use synthetic inputs and redact personal data and credentials. Ask before any live submission, provider change, push or deployment. Trace one page view and one lead from the UI to an intercepted collector. Check duplicate navigation, invalid input, accepted requests, retries and consent changes. Report event counts and safe property names without personal values. Return a read-only finding with the page or file, what you observed, what remains unknown and the smallest justified change. ## 19. Describe what the image contributes here Work in [site or repository] using [stack], limited to [approved pages or features]. Read the project instructions first. Use synthetic inputs and redact personal data and credentials. Ask before any live submission, provider change, push or deployment. Classify a representative content image, decorative image and linked image. Compare each image with its surrounding text and accessible name. Propose only the descriptions or empty alternatives that improve meaning. Return a read-only finding with the page or file, what you observed, what remains unknown and the smallest justified change. ## 20. Make the next action predictable Work in [site or repository] using [stack], limited to [approved pages or features]. Read the project instructions first. Use synthetic inputs and redact personal data and credentials. Ask before any live submission, provider change, push or deployment. Follow the primary task on one landing page at desktop and mobile widths. Compare the action label with the destination and test keyboard reachability. Suggest a clearer verb only if the present promise is ambiguous. Return a read-only finding with the page or file, what you observed, what remains unknown and the smallest justified change.