agentleFS
ScinoScino/fstack/skills/customer-lens/SKILL.md

customer-lens

Skill18 starsChanged 53 days agoMITView on GitHub

Audits UI flows, onboarding funnels, error messages, and landing page copy from the perspective of a skeptical, distracted customer. Identifies cognitive friction, confusing jargon, and drop-off risks. Use for /customer-lens, "audit UX", or customer friction review.

The file

We split this skill into the rules it gives an agent

3 rules. About 0 are common, 3 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    When an existing feature is seeing unexpected drop-off or confusion.

    line 20
  2. Distinctive:

    When things go wrong, does the app give the user a way out?

    line 46
  3. Distinctive:

    Every error message must contain:

    line 47

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Customer Lens

Founders and engineers have "curse of knowledge": we know exactly how the app works, where to click, and why that cryptic error message appeared. Real customers have 10 browser tabs open, zero patience, and will bounce in 5 seconds if something is confusing.

customer-lens simulates a critical, distracted user inspecting your product to catch friction before customers bounce.


When to Invoke

  • Reviewing a new onboarding or signup flow before launching.
  • Auditing a landing page hero section and pricing table.
  • Reviewing error messages and empty states in your application.
  • When an existing feature is seeing unexpected drop-off or confusion.

The 4 Audit Lenses

1. The 5-Second Comprehension Test (Landing Page & Hero)

  • Can a first-time visitor answer these 3 questions in under 5 seconds?
    1. What is this?
    2. Who is it for?
    3. What do I do next?
  • Common fails: Abstract taglines like "Redefining the frontier of intelligent workflows" (tells the user nothing).

2. Time-to-Value (The Onboarding Funnel)

  • How many steps/clicks between "Sign up" and the "Aha! moment"?
  • Does the app force unnecessary onboarding steps (e.g. asking for phone number, team size, or company URL before showing any value)?
  • Does the empty state explain what to do, or is it a barren white screen?

3. Jargon & Internal Language Check

  • Are you using internal engineering terms on user-facing screens?
    • Bad: "Synchronizing replica node 3..."
    • Good: "Saving changes..."
    • Bad: "Payload validation failed on schema #2"
    • Good: "Please enter a valid email address."

4. Error State & Recovery Audit

  • When things go wrong, does the app give the user a way out?
  • Every error message must contain:
    1. Plain-English explanation of what happened.
    2. The exact single action to fix it (e.g. "Try refreshing," "Check your API key," "Contact support").

The Deliverable Report

# 🔍 Customer Lens Audit: [Feature / Page Name]

## Overall Verdict: [Pass / High Friction / High Drop-off Risk]

### 🚨 Critical Friction Points (Fix Before Launch)
1. **Empty State on First Login**:
   - *Observation*: After signup, the user lands on an empty dashboard with no guidance.
   - *User Reaction*: "Is it broken? What am I supposed to do?"
   - *Fix*: Add a single primary button: *"Create your first project (+ template)"*.

2. **Hero Copy Ambiguity**:
   - *Current*: "The unified intelligence layer for enterprise operations."
   - *Customer Confusion*: Sounds like generic AI hype.
   - *Recommended*: "Automate database backups and restore testing in 1 click."

### 💡 High-ROI Polish Items
- Add tooltips to the 3 advanced export options in Settings.
- Replace technical 401 error with: *"Your session expired. Click here to sign back in."*

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.