ux-general
Skill21 starsChanged 5 months agoMITView on GitHub
General app quality: app store presence, launch experience, splash screen, force update, cloud sync, backup and restore, OS integrations, widgets, orientation, monetization surfacing, and versioning. Use when reviewing overall app health, preparing for store submission, or evaluating cross-platform consistency.
In this repository17 other files it gives its agents.
- ux-accessibilitySkill
- ux-ai-automationSkill
- ux-contentSkill
- ux-error-handlingSkill
- ux-formsSkill
- ux-help-onboardingSkill
- ux-information-architectureSkill
- ux-navigationSkill
- ux-networkSkill
- ux-notificationsSkill
- ux-reviewSkill
- ux-safety-privacySkill
- ux-searchSkill
- ux-settingsSkill
- ux-user-accountSkill
- ux-utilitySkill
- ux-visual-designSkill
The file
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 2 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
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
- Distinctive: line 67
Follow each platform's own guidelines rather than porting one platform's patterns to another.
- Distinctive: line 79
When applying this checklist to a screen, flow, or codebase:
≈ “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.
Files
General App Quality
These are the fundamentals every app needs regardless of domain. Reviewers, users, and store guidelines all expect them.
Each item carries a priority:
- Required — launch blocker. Failing this means the app is not production-ready.
- Recommended — strong quality signal. Most successful apps have it.
- Optional — differentiator. Valuable for specific audiences, not universal.
Checklist
| Item | Priority | Guidance |
| App name | Required | Memorable, spellable, searchable. Check for trademark conflicts before launch. |
| App icon | Required | Recognizable at 29x29pt. No text inside the icon. Works on both light and dark backgrounds. |
| App icon (PWA) | Recommended | Appropriate icon configured for PWA installation and homescreen display. |
| Installation guide | Recommended | User is clearly informed about the install or activation process. |
| ASO | Recommended | Keyword-rich title, subtitle, and description. A/B test screenshots regularly. |
| What's new | Recommended | Changelog or release notes are shown to the user after an update. |
| Splash screen | Required | Brand-colored background with a centered logo. Keep it under 2 seconds. |
| Force update | Required | Mandatory update dialog blocks old versions with a clear store link. |
| Cloud sync | Recommended | Data syncs across devices. Has a defined conflict resolution strategy. |
| Backup and restore | Recommended | User can back up and fully restore data on reinstall. |
| OS language sync | Recommended | App language updates automatically when the OS language changes. |
| Dark mode sync | Recommended | App follows the OS dark mode setting without requiring manual change. |
| Background mode | Required where applicable | App continues working in the background where needed (audio, timers). |
| Widget support | Optional | Homescreen widget is available for quick access to core actions. |
| Storage location | Optional | User can move data between internal storage and SD card (Android). |
| In-app rating prompt | Recommended | Store rating prompt appears at the right moment — after a clear user win. |
| Contact support | Required | A clear way to reach the support team is available inside the app. |
| App integrations | Optional | App can connect to third-party services where relevant. |
| Cross-platform parity | Recommended | Core functionality is consistent across all supported platforms. |
| Version number | Required | App version is visible in Settings or About. |
| Trial mode indicator | Required where applicable | Users on a trial see their trial status and expiry clearly. |
| Status bar activity | Required where applicable | Background activity (music, recording) is visible in the system status bar. |
| Multitasking support | Recommended | App handles split screen and simultaneous actions without breaking. |
| Orientation support | Recommended | App works correctly in both portrait and landscape orientations. |
| In-app operation status | Required | Progress of ongoing actions (downloading, uploading) is visible while they run. |
| Cancel any action | Recommended | Every async operation shows a cancel option while it is in progress. |
| Pull-to-refresh | Recommended | Pulling down a list refreshes the content with a standard spinner animation. |
| Ad removal option | Optional | User can pay to remove ads where applicable. |
| Purchasable features | Recommended where applicable | In-app purchases and upgrades are clearly surfaced at the right moment. |
Key Principles
Ship-ready baseline: Required items are table stakes — if any of them fail, the app is not ready for production. Recommended and Optional items are quality and retention levers, not launch blockers.
Platform conventions matter: iOS and Android users have different mental models. Follow each platform's own guidelines rather than porting one platform's patterns to another.
Test on real devices: Simulators miss orientation bugs, performance issues, and real-world storage behavior. Always test the final build on physical hardware before submission.
Update cadence: A "What's new" section only works if updates are meaningful and communicated in plain language — not "Bug fixes and performance improvements."
How to Review
When applying this checklist to a screen, flow, or codebase:
- Go through every checklist item and mark it Pass, Fail, or N/A — never skip items silently.
- Cite specific evidence for each finding: the screen, component, file, or line it applies to.
- Tag each failure with a severity: Blocker (breaks the experience), Major (hurts usability), or Minor (polish).
- End the review with the top 3 recommended fixes, ranked by user impact.
Related Skills
ux-settings— in-app language, cache clearing, and preference organizationux-navigation— deep links, back stack, and screen hierarchyux-notifications— push permission timing and notification qualityux-review— entry point for a full multi-category UX audit
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
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.