ux-utility
Skill21 starsChanged 5 months agoMITView on GitHub
Utility and productivity features: favorites, bookmarks, native share sheet, in-app browser, personalization, and clipboard integration. Use when designing or reviewing features that help users get things done faster or customize their experience.
In this repository17 other files it gives its agents.
- ux-accessibilitySkill
- ux-ai-automationSkill
- ux-contentSkill
- ux-error-handlingSkill
- ux-formsSkill
- ux-generalSkill
- 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-visual-designSkill
The file
We split this skill into the rules it gives an agent
3 rules. About 0 are common, 3 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
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 36
Never fail silently. Show a fill animation on save as confirmation.
- Distinctive: line 40
Personalization strategies: Start with an explicit onboarding step where users select their interests.
- Distinctive: line 60
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
Utility Features
Utility features are what keep power users loyal. They reduce repetitive work and let users shape the app around their own habits and preferences.
Checklist
| Item | Guidance |
| Favorites and bookmarks | Save icon visible on content cards. Saved list is easy to find from the main navigation. |
| Share feature | Uses the native share sheet. Never a custom share UI. Includes a shareable URL. |
| In-app browser | External links may open in an in-app browser, but always with a visible "Open in browser" action. Respect the user's default browser for external destinations — never trap users in the in-app view. |
| Personalization | User can choose interests, layout, or notification frequency, starting at onboarding. |
| Clipboard integration | Copied URLs are detected on app launch and offered to the user as a quick action — using privacy-safe detection APIs (see pattern below). |
Patterns
Share sheet: Pre-populate the share text with a useful message, not a bare URL. Include UTM parameters for tracking. Support sharing images, text, and URLs through the same entry point.
Favorites architecture: Save to local storage first, then sync to the server. Never fail silently. Show a fill animation on save as confirmation. Empty state for the saved list should invite the first save action. Optionally allow organizing saved items into folders for power users.
Personalization strategies: Start with an explicit onboarding step where users select their interests. Refine over time with behavioral signals (views, time spent, taps). Always show a "Why am I seeing this?" explanation so recommendations feel trustworthy rather than arbitrary.
Clipboard detection: Show a subtle, non-intrusive banner when a link is detected on the clipboard: "We noticed a link — open it in [App]?" Dismiss automatically after a few seconds if the user ignores it. Never open the link automatically.
Platform constraints: on iOS 16+, reading the clipboard directly triggers a
system paste permission prompt — use UIPasteboard.detectPatterns to check
whether a URL is present without reading the contents and without triggering
the prompt. Android 12+ shows a system toast whenever an app reads the
clipboard, so read it only at the moment of use, never speculatively.
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-general— widgets, integrations, and cross-platform parityux-safety-privacy— clipboard and permission privacy expectationsux-ai-automation— personalization driven by recommendations
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.