Menü
Use when reviewing an app for launch-readiness — Product Hunt polish, first impression, visual hierarchy, onboarding, empty states, screenshots, positioning, and the tiny details that make it feel premium.
Mit Codex oder Claude installieren Kopieren Sie diesen Prompt, fügen Sie ihn in Codex, Claude oder einen anderen Assistant ein und lassen Sie die Skill-Seite prüfen und installieren.
Use when shipping a macOS app outside the App Store — Developer ID signing with hardened runtime, notarization with notarytool, stapling, building a clean drag-to-Applications DMG, and verifying the result launches on a stranger's Mac.
Use when reading, writing, or watching the macOS clipboard — NSPasteboard types and multiple representations, the changeCount polling pattern, the transient/concealed pasteboard conventions clipboard tools must respect, and the Sequoia paste-privacy alerts.
Use when adding or reviewing keyboard shortcuts in a macOS app — in-app vs global, RegisterEventHotKey vs the KeyboardShortcuts package vs NSEvent monitors, user-configurable recording, conflict handling, and which defaults won't collide with the system.
Use when adding, reviewing, or debugging Launch at Login in a macOS app — SMAppService registration, the requiresApproval state, a Settings toggle that reflects reality, and migration off deprecated login-item APIs.
Use when adding or reviewing macOS user notifications — UNUserNotificationCenter permission flow, categories and action buttons, click routing through the delegate, foreground presentation, and rules that keep notifications from becoming spam.
Use when a macOS app needs a TCC permission or touches private data — the map of which API, Info.plist key, and entitlement each permission needs, pre-prompt explanation patterns, denied-state recovery with System Settings deep links, and honest privacy copy.
Basierend auf der SOC-Berufsklassifikation
| name | product-hunt-polish-review |
| description | Use when reviewing an app for launch-readiness — Product Hunt polish, first impression, visual hierarchy, onboarding, empty states, screenshots, positioning, and the tiny details that make it feel premium. |
Review an app for launch-readiness so it feels useful, clear, trustworthy, and polished in the first 30 seconds. Be direct and critical, prioritize clarity over decoration, and end with a concrete pre-launch checklist.
Use this skill when reviewing an app for launch-readiness, Product Hunt polish, first impression, visual quality, onboarding, screenshots, positioning, and tiny details that make the app feel premium.
A launch-ready app must feel useful, clear, trustworthy, and polished in the first 30 seconds.
Use when the user says:
Do not use this skill for:
1. First impression
2. Core value clarity
3. Visual hierarchy
4. Onboarding
5. Empty states
6. Feedback/status
7. Performance feel
8. Trust/privacy
9. Screenshots
10. Launch copy
A new user should understand:
What is this?
Why do I need it?
What should I click first?
What happens after I click?
Can I trust it?
If not, simplify.
[ ] App name is clear
[ ] One-sentence value proposition exists
[ ] Primary action is obvious
[ ] No dense dashboard on first launch
[ ] Empty state helps user start
[ ] Visual style feels intentional
[ ] No broken or placeholder content
[ ] No confusing technical jargon for non-technical users
[ ] Consistent spacing
[ ] Consistent typography
[ ] Consistent SF Symbols
[ ] Calm color system
[ ] Main content has breathing room
[ ] Few competing elements
[ ] Clear selected states
[ ] Clear hover/focus states
[ ] Loading/error/success states exist
[ ] Dark and light mode are both checked
Good format:
[Product] helps [user] do [job] without [pain].
Examples:
HubApp helps vibe coders run agent projects from one calm Mac workspace without losing track of tasks, skills, and active runs.
SkillPilot helps builders choose the right skills for each task without digging through folders.
For launch screenshots:
1. Hero screen showing main value
2. Command palette / fast workflow
3. Active run / status tracking
4. Skills/project organization
5. Settings/local AI/privacy
Rules:
Every empty state should sell the product gently.
Example:
No Active Runs
The agent is not working on anything right now.
Start a task, open the queue, or run a saved skill.
Especially for AI/local apps:
[ ] Explain what stays local
[ ] Explain when cloud is used
[ ] Do not silently send private prompts to cloud
[ ] Show model/provider status
[ ] Show folder permissions clearly
[ ] Store secrets securely
[ ] Add export/delete data options if relevant
Good buttons:
New Task
Run Skill
Open Queue
Generate Report
Connect Ollama
Bad buttons:
Go
Submit
Do Magic
Proceed
Rate each 1–5:
Clarity
Visual polish
Speed feel
Onboarding
Empty states
Error states
Trust/privacy
Screenshot quality
Positioning
Retention hook
Launch only when the average is 4+ and no category is below 3.
Beautiful UI but unclear value
Too many features on first screen
No onboarding
No empty states
Fake progress
Placeholder content in screenshots
No trust/privacy explanation
Inconsistent icons/spacing
Product Hunt copy too vague
Drop this into any coding agent (Claude Code, Codex, Cursor, …) to apply the skill:
Use the product-hunt-polish-review skill to review this app for launch polish.
Goal:
Make the app feel premium, clear, useful, and launch-ready in the first 30 seconds.
Review:
- First impression
- Value proposition
- Primary action
- Visual hierarchy
- Empty states
- Feedback/status
- Onboarding
- Trust/privacy
- Screenshot readiness
- Microcopy
Rules:
- Be direct and critical.
- Identify what feels unfinished.
- Suggest concrete UI/content fixes.
- Do not add more features unless they improve first-time value.
- Prioritize clarity over decoration.
Output:
1. Launch readiness score / 10
2. Top 5 issues
3. Top 5 fixes
4. Screenshot plan
5. Product Hunt tagline options
6. Final pre-launch checklist