[wladpaiva]

Summary

Adds .cursor/skills/verify-website, a project-local skill that launches an isolated Astro instance and drives the visitor-facing website.

The primary surface is apps/website. Day-to-day vp run website#dev shares one portless host, so verification starts astro dev directly on 127.0.0.1 with VARLOCK_ENV=test and no PostHog key. The React Email preview and the notifications library are out of scope.

The feature map covers the home page, the missing page, the server error page, document metadata, and the test-build crawl files (robots.txt and sitemap).

Proof

Ran the missing-page recipe end to end on run id missing-page-proof:

• launch reached a complete homepage (title Blockbase, shared button present) at http://127.0.0.1:4321
• doctor reported ok: yes, mode: dev, homepage: complete, analyticsKey: unset
• Opened /verify-missing-page (status 404, title Pagina nao encontrada | Blockbase) and /404 (same page)
• Followed Voltar para o inicio from both entries back to / (status 200, button Button from @workspace/ui)
• Request logs did not contact posthog.com
• cleanup removed /tmp/verify-website-missing-page-proof and left the evidence in .cursor/skills/verify-website/evidence/missing-page-proof/

Missing page for an unknown address
Home page after following the return link

No application code changed. A cold dev start can log Invalid hook call and return an incomplete homepage once; launch retries until the document contains the button.

Unverified

• The other mapped features were not part of this proof run
• https://website.blockbase.localhost via portless
• PostHog with a real POSTHOG_KEY
• A production crawl file (Disallow is / only because VARLOCK_ENV=test)
• Cloudflare deploy, and the React Email preview

_{To show artifacts inline, enable in settings.}

  

---

^{Need help on this PR? Tag @codesmith-bot with what you need.}