菜单
Add loading, empty, error, and success feedback states to StyleSeed components and pages with practical mobile-first rules.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
ALWAYS use this skill when committing code changes — never commit directly without it. Creates commits following Sentry conventions with proper conventional commit format and issue references. Trigger on any commit, git commit, save changes, or commit message task.
Create a git branch following Sentry naming conventions. Use when asked to "create a branch", "new branch", "start a branch", "make a branch", "switch to a new branch", or when starting new work on the default branch.
Alias for sentry-skills:pr-writer. Use when users explicitly ask for "create-pr" or reference the legacy skill name. Redirects to the canonical PR writing workflow.
Use the `gh` CLI for issues, pull requests, Actions runs, and GitHub API queries.
Use when executing implementation plans with independent tasks in the current session
Coordinate quota-aware parallel subagents for large, multi-file Antigravity tasks.
| name | ux-feedback |
| description | Add loading, empty, error, and success feedback states to StyleSeed components and pages with practical mobile-first rules. |
| category | design |
| risk | safe |
| source | community |
| source_repo | bitjaru/styleseed |
| source_type | community |
| date_added | 2026-04-08 |
| author | bitjaru |
| tags | ["ux","states","loading","error-handling","styleseed"] |
| tools | ["claude","cursor","codex","gemini"] |
Part of StyleSeed, this skill ensures data-dependent UI does not stop at the happy path. It adds the four core feedback states every serious product needs: loading, empty, error, and success.
Use skeletons that match the final layout. Avoid spinners inside cards unless the pattern genuinely requires them. Delay skeletons slightly to avoid flashes on fast responses.
Provide a friendly explanation and a next action. Zero values should still render meaningfully instead of disappearing.
Use plain-language failure messages and always offer recovery where possible. Localize failures to the affected card or section if the rest of the page can still work.
Use toasts or equivalent lightweight confirmation for completed actions. Add undo for reversible destructive changes.
Return:
