Visit Logger — Development skill for Claude Code

visit-logger

[](https://agentskills.io) [](https://www.skills.sh) [](https://docs.claude.com/en/docs/claude-code/skills) [](https://developers.openai.com/codex/skills) [](https://github.com/google-gemini/gemini-cli/blob/main/docs/cli/skills.md)

An [Agent Skill](https://agentskills.io) that teaches an agent to log, server-side, **who opened what, from where and on what** in a **Next.js App Router** app: an IP, edge-geolocation and parsed-browser fingerprint for every real page view of a shared resource, the same fingerprint at the lifecycle moments before a resource exists (sign-in link requested, account created, signed in), storage in Postgres/Supabase or Firestore, and the output a salesperson reads: sittings, a first-open announcement, admin history panels.

**A request is not a visit.** Prefetches, assets, mail scanners, staff previews and reloads all arrive as requests, and every rule in the module exists to keep them from becoming "the customer opened it" in someone's Slack. That is also what separates this from analytics: the log is attributed to one resource and one person, it is read one customer at a time, and the cost of a wrong row is a phone call made on a fact that was never true.

This skill was written by the engineer who has shipped this module. The earlier implementation it was audited against was a visit log on a sales site, behind the shared links a team sends customers and on its sign-in routes. The templates hold the properties such a log has to hold: every stored page view is a document navigation or an App Router client navigation, never a prefetch, an asset or a Server Action;