Frontend State And Interaction Design
Designs predictable states for loading, empty, error, partial, long-running and approval workflows. Use when implementing async UI, agent tasks, or multi-step forms.
Install
$ agentstack add skill-mmccalla-coding-agent-skill-library-frontend-state-and-interaction-design ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Links to your public security report.[](https://agentstack.voostack.com/security/report/skill-mmccalla-coding-agent-skill-library-frontend-state-and-interaction-design) Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
Frontend State and Interaction Design
When to use
Use this skill when implementing async flows, long-running jobs, background workflows, forms, dashboards, approval flows, optimistic updates, error recovery, retry actions, partial success states or agent task execution.
Objective
Make frontend behaviour predictable, recoverable and transparent across all meaningful states.
Procedure
- Identify all relevant states.
- Define state transitions explicitly.
- Make the current state visible.
- Provide recovery actions for errors where possible.
- Preserve user input during recoverable failures.
- Distinguish empty, loading, error, denied, partial and complete states.
- For long-running jobs, show progress, status, timestamps and next update behaviour.
- For destructive or high-risk actions, require confirmation.
- For optimistic updates, provide rollback or reconciliation.
- Test transitions, not just final rendered output.
Required states
Consider idle, loading, validating, submitting, running, awaiting_approval, success, partial_success, empty, warning, error, denied, cancelled, retrying and stale.
Rules
- Do not show a spinner with no context for long-running work.
- Do not collapse policy denial, validation failure and system error into the same message.
- Do not lose user-entered data on validation failure.
- Do not use optimistic updates for irreversible or high-risk operations.
- Do not allow double submission unless the action is idempotent.
- Do not hide partial success where some records, rules or batches failed.
Optional overlay
For product-specific DataOps/MCP examples, load skills_docs/overlays/mas-dataops-mcp-overlay.md.
References
Verification
- [ ] States and transitions implemented listed.
- [ ] Recovery options and high-risk controls documented.
- [ ] Tests or manual checks performed.
- [ ] Residual interaction risks stated.
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: mmccalla
- Source: mmccalla/coding-agent-skill-library
- License: Apache-2.0
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.