When you're building an app, you already know where every button leads and what the user is supposed to do next.

Your first-time visitors don't.

That's why I built First User Audit — an open-source Agent Skill that helps coding agents explore your application from four different first-time-user perspectives.

It focuses on one question:

Can someone reach the first useful result without getting stuck?

Four perspectives, one app

The skill uses four simulated user behaviors:

  • Impatient — Skims the page, clicks the obvious button, and quickly gives up when things get confusing.
  • Skeptic — Checks pricing, privacy, and terms before trusting the product.
  • Mobile — Explores the experience at a 375px viewport.
  • Breaker — Tries invalid inputs, retries, back navigation, and double submissions.

Four first-time-user perspectives

What does the skill actually do?

It guides your coding agent through a simple process:

  1. Identify what first success means for your app.
  2. Explore the onboarding journey through four different behaviors.
  3. Record blockers with browser evidence and reproduction steps.
  4. Prioritize issues and propose safe technical fixes.
  5. Verify changes through fresh sessions when supported.

First User Audit workflow

The idea is to catch friction that can be easy to overlook when you're already familiar with your product.

Try it with your coding agent

You can install it using the skills CLI, or simply copy this prompt into Claude Code, Codex, or another compatible coding agent:

Install the first-user-audit Agent Skill from: https://github.com/BarganConstantin/agent-skills Use the skills CLI: npx skills add BarganConstantin/agent-skills --skill first-user-audit Verify that the skill is installed. Inspect my application and identify the first useful outcome a new user should reach. If a safe local or isolated preview environment and browser automation are available, run the four first-user personas with fresh browser sessions. Collect evidence, identify friction, propose bounded technical fixes, and verify changes with fresh agent contexts when supported. Do not use production data or live payments. Ask before sensitive changes or reduced-isolation runs. If anything is missing, explain how to set it up. Never invent test results.

The skill requires connected browser tooling for the audit. Independent subagents depend on your coding environment, and simulated personas don't replace real usability testing.

It's open source under the MIT license.

Explore First User Audit on GitHub

Give it a try

If you use it on your own project, I'd love to hear what happens.

Did it catch an issue you hadn't noticed? Did it miss something obvious? Was the setup straightforward?

Share your experience in the comments. Feedback, ideas, and contributions are always welcome.