# Audit Long-Running Web App Waiting States

Long-running web operations can feel stalled and cause users to abandon important tasks. This skill captures timed states, evaluates waiting feedback, and produces prioritized improvements.

## Install

```bash
npx skillstore add bayramannakov/ux-waiting-audit
```

## Metadata

- Status: approved
- Slug: bayramannakov-ux-waiting-audit
- Skillstore revision: r2
- Version status: missing
- Tree hash: 357d273c7ee9b9d55c3ffb64fa84d6102fc7aa5903b73a36dd75adadba069e3b
- Author: BayramAnnakov
- GitHub username: BayramAnnakov
- License: MIT
- Repository: https://github.com/BayramAnnakov/ux-waiting-audit/tree/main/
- Ref: 8c3e20bba512c392d9b02ee748b18e0b09d4982c
- Supported tools: Claude, Codex, Claude Code
- Audit status: complete
- Agent install advisory: confirmation\_required
- Manual install advisory: allowed
- Artifact signature: available
- Audit attestation: unavailable
- Human verification: not\_verified
- Risk factors: network, filesystem, external\_commands
- Quality score: 38
- Quality tier: warning
- Public page: https://skillstore.pages.dev/skills/bayramannakov-ux-waiting-audit
- Manifest: https://skillstore.pages.dev/api/skills/bayramannakov-ux-waiting-audit/manifest

## Capabilities

- Navigates to a supplied web application using compatible browser automation tools.
- Captures screenshots at operation start, timed intervals, and completion.
- Inspects visible text and DOM signals for spinners, progress bars, counters, and partial results.
- Evaluates progressive value, heartbeat indicators, time estimates, interruption options, and anxiety reduction.
- Compares waiting states across a timestamped timeline.
- Produces a Markdown audit with strengths, gaps, quick wins, and prioritized recommendations.

## Use Cases

- Review AI Task Feedback: Assess whether research, generation, or analysis workflows communicate progress during waits longer than 30 seconds.
- Validate Release Readiness: Capture a repeatable waiting-state timeline before shipping a slow report, export, or deployment workflow.
- Prioritize Loading Improvements: Convert observed waiting problems into clear priorities for progress, cancellation, partial results, and completion feedback.

## Prompt Templates

### Audit One Waiting State

```
Audit the waiting experience at [URL] for [operation]. Ask before interacting, capture start and completion, then list the three highest-impact improvements.
```

### Capture a Timed Timeline

```
Review [operation] at [URL]. After I trigger it, capture states at start, 10 seconds, 30 seconds, and completion. Compare visible feedback.
```

### Score a Complete Workflow

```
Audit [operation] in the approved test environment. Evaluate progress, time estimates, partial value, cancellation, errors, and completion. Produce prioritized recommendations.
```

### Compare Normal and Failure States

```
Audit [operation] in staging under normal, slow, interrupted, and timeout conditions. Confirm each consequential action. Compare timelines and propose measurable acceptance criteria.
```

## Limitations

- Requires compatible browser automation and permission to access the target application.
- Depends on user guidance when navigation, authentication, or operation triggers are unclear.
- Cannot guarantee reliable timing or error simulation in production environments.
- Referenced checklist, report template, and capture helper files are absent from this package.

## Best Practices

- Use a staging environment, temporary account, and disposable test data.
- Confirm the operation, expected duration, capture scope, and sensitive areas before starting.
- Redact screenshots and connect every recommendation to timestamped visual evidence.

## Anti Patterns

- Do not request passwords, tokens, production credentials, or unrelated customer data.
- Do not submit forms, click destructive controls, or simulate failures without explicit confirmation.
- Do not treat a spinner alone as sufficient evidence of a usable waiting experience.

## Security Audit

- Audited at: 2026-07-23T10:52:05.345\+00:00
- Summary: All 34 static findings are false positives caused by example URLs, a standard installation path, Markdown formatting, and screenshot comments without upload behavior. Semantic review found real privacy and interaction risks in requesting login credentials, capturing authenticated screens without redaction guidance, and submitting forms without explicit confirmation.

## Stats

- Views: 301
- Downloads: 24
- Favorites: 1
- Popularity score: 0