pm-error-scenarios

Name: pm-error-scenarios
Availability: InStock
Author: Kwon

Define UI states and error messaging schemas for web and mobile apps.

Updated Aug 27, 2026

Search Tags:#edge-cases #error-handling #ux-design #user-messages #ui-states #state-definition

Ready to run

npx skills add https://github.com/Kwondongkyun/claude-code-settings --skill pm-error-scenarios

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: pm-error-scenarios
Source: https://github.com/Kwondongkyun/claude-code-settings/tree/main/skills/pm-error-scenarios
Command: npx skills add https://github.com/Kwondongkyun/claude-code-settings --skill pm-error-scenarios

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

UI features often suffer from inconsistent error states, loading indicators, empty states, and edge-case handling that degrade user experience. This Skill provides a structured approach to define and communicate states and errors consistently across a product.

Core Features & Use Cases

Define the five essential UI states for every screen (Default, Loading, Empty, Error, Success) with clear criteria and UX expectations.
Specify error-type schemas (Validation, System, Permission, Business Logic) including field rules, messages, and timing for when each should appear.
Include a reusable state-definition template and practical guidance for common edge-cases (offline mode, long text, simultaneous edits, navigation away from forms).

Quick Start

Define your feature's UI states and error messages by completing the state-definition template and writing consistent user-facing messages.

Frequently Asked Questions about pm-error-scenarios

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I standardize UI state handling across web and mobile app features?▼

Standardize UI state handling by applying a prescriptive schema that defines Default, Loading, Empty, Error, and Success states for every screen. This enforces consistent UX expectations and state definitions across your software features.

What is the best way to define error messages for edge cases in UX design?▼

Defining error messages for edge cases requires specifying error-type schemas for Validation, System, Permission, and Business Logic errors. You can use a reusable state-definition template to write consistent user-facing messages and field rules.

How do I handle offline mode and simultaneous edits in front-end state definitions?▼

Handle offline mode and simultaneous edits by following practical edge-case guidance included in the state-definition schema. This provides specific behavioral rules for navigation away from forms, long text, and simultaneous edits to prevent inconsistent UI.

Can I use a single state-definition template for both web and mobile apps?▼

Yes, you can use a single reusable state-definition template for both web and mobile apps. The schema applies universally across platforms to define the five essential UI states and standardize all error messaging guidelines.

When should I display validation errors versus system errors to the user?▼

Display validation errors versus system errors based on specified error-type schemas that dictate field rules and timing. The schema separates Validation, System, Permission, and Business Logic errors to ensure correct message timing and UX expectations.