coreyhaines31/makerskills / skills/product-manager
product-manager
VerifiedWhen you want to plan, build, or check an app from idea through launch readiness — web, Apple, mobile, or extensions. Writes the brief, picks the stack (Next.js + TypeScript + Prisma by default, Swift on Apple), designs complete UX states, defines roles and agent access, measures performance before optimizing, and produces a readiness report where missing evidence is never a pass. Four modes: spec (plan v1), check (launch readiness), audit (ranked improvements, including what a new model changes), fleet (a named list of apps). Triggers on "/product-manager," "act as my product manager," "PM this app," "build me an app," "plan v1," "spec this app," "is this app ready to launch," "launch readiness," "audit my apps," "what's missing before we ship," "do a comprehensive audit," "how could we improve my app," "a new model just came out." Not for launch marketing or growth (see launch), integration plumbing (see toolify), CI cost (see ci-audit), or managing a project backlog/kanban (see project-manager).
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 16.5 KB |
| references/audit.md | markdown | 11.8 KB |
| references/defensibility.md | markdown | 5.6 KB |
| references/performance.md | markdown | 5.4 KB |
| references/readiness.md | markdown | 6.2 KB |
| references/standards.md | markdown | 7.0 KB |
| references/trust.md | markdown | 11.0 KB |
| references/ux.md | markdown | 9.7 KB |
references/ux.md
View on GitHub# UX: happy paths, recovery and contextual help
## Rules
1. **Minimize total effort, not raw clicks.** Count navigation, repeated input, choices, memory burden and waiting. Two clear steps beat one confusing screen. Keep safeguards whose risk reduction earns them.
2. **One clear primary action per decision.** Familiar labels, visible reversible defaults. No optional setup before first value.
3. **Reveal advanced options when needed, but never hide costs, permissions, errors or core capability.**
4. **Preserve work.** Keep input across retry and navigation. Switching account/tenant or logging out must clear the previous audience's private data and cached entitlements.
5. **Honest states.** Pending, processing, saved, failed and complete are different. Progress isn't success.
6. **Design every state:** empty, invalid, denied, offline, partial, failure, recovery. Safe retry and undo where possible. Explicit confirmation for irreversible actions.
7. **Accessible by default.** Semantic controls, keyboard paths, visible focus, labels, contrast, zoom and text scaling, touch targets, non-color cues, reduced motion.
8. **Reuse components, vocabulary and platform patterns.** A new interaction has to justify what it costs to learn. No universal house style.
9. **No fake activity, urgency, traction or consent.** Label sample data. No dark-pattern cancellation.
10. **Light and dark means the user picks.** If the app or its marketing site ships both, give a visible Light / Dark / System control. Default to System (`prefers-color-scheme`, or the OS appearance on native). Save the choice to the account when signed in, otherwise locally, and apply it before first paint so the page doesn't flash the wrong theme. A marketing site gets the same override, in the header or footer. A product that ships one theme needs no toggle.
11. **Heuristics propose, observation proves.** Walk through first-use, return, keyboard and recovery journeys with realistic fixtures.
## Contextual help: use it aggressively
Use tooltips, helper text and inline status cues wherever a user might hesitate:
- **Unfamiliar metrics:** what it means, its range, and how fresh it is.
- **Settings:** what changes, and for whom.
- **Permissions:** who can do this.
- **Requirements:** what's missing.
- **Unavailable actions:** why, and what to do next.
- **Status:** what happened and what happens next.
Put help where the decision happens, not in a distant docs page. Keep it short. Don't restate the label.
**But essentials stay inline.** Required-field markers, validation errors, essential instructions and irreversible consequences are always visible. Tooltips supplement labels. Anything interactive (links, settings) belongs in a popover or dialog, not a tooltip.
Tooltip mechanics:
- Opens on hover *and* keyboard focus, and has an accessible description relationship.
- Escape dismisses it. Content stays open while the pointer is over it. There's a touch alternative.
- It doesn't cover the trigger or essential content.
- **Disabled buttons:** native disabled elements can't receive focus, so a tooltip on one is unreachable by keyboard. Put the explanation next to the button, or add a focusable help trigger beside it. `aria-disabled` can work if activation is actually blocked.
## Worked example: invite a collaborator (synthetic)
Happy path: org context visible → email → role (safe default) → access summary → **Send invitation** → pending row appears. Keep the review step, because access consequences justify the extra click. The button says "Send invitation", not "Continue".
| State | UI | Guidance |
|---|---|---|
| Empty list | "No collaborators yet" + Invite as primary | Says invites apply to the current org |
| Invalid email | Inline error, input kept, focus moves to first error | Visible without hovering |
| Already a member | Explain, link to member management if permitted | No duplicate send. Don't leak other-tenant membership |
| Role not allowed | Server denies; UI shows allowed choices | Tooltip isn't the only explanation |
| Plan limit | Inline reason + next step | Disabled button has nearby help |
| Sending | Block double-submit, show pending, announce to screen readers | No premature success |
| Timeout | "Delivery status unknown". Check status before retrying | Same idempotency key, never a blind resend |
| Role changed mid-flow | Revalidate on send | Stale UI isn't approval |
| Offline | Keep draft, clearly marked not sent | No silent queued external send |
Role tooltip copy: "Editors can change project content. They can't manage billing or invite admins." The actual policy decides what the copy says.
## Design workflow
Brief → current patterns and constraints → reference links and what to borrow from each → chosen direction → flow plus component, token and state spec → small prototype if novel → acceptance checks → review. Preserve good existing design. Use real or clearly labeled synthetic data. Don't copy unlicensed assets.
## Design skills to route to
Route to a specialized design skill rather than inventing a new method here. All of these are external. Use one if it's installed. If it isn't, name it to the user with its install link and carry on with this file. Never install one without asking.
| Job | Skill | Source |
|---|---|---|
| The app has no brand yet, or the brand is weak: audit it, pick colors, type and visual language, design the mark | **brand** → **creative-direction** → **logo-design** (Zach Stevens' design skills) | [zstvns/design-skills](https://github.com/zstvns/design-skills) |
| Why a design feels off: hierarchy, restraint, contrast, coherence | **design-principles** (same pack) | [zstvns/design-skills](https://github.com/zstvns/design-skills) |
| Visual direction, plus polish/critique passes on web UI | **impeccable** (Paul Bakaus): design vocabulary and commands like `/polish`, `/audit`, `/critique` | [pbakaus/impeccable](https://github.com/pbakaus/impeccable) |
| Avoid generic AI-looking UI | **hallmark** (Nutlope) | [Nutlope/hallmark](https://github.com/Nutlope/hallmark) |
| Intentional visual direction (the original Anthropic skill impeccable builds on) | **frontend-design** | [anthropics/skills](https://github.com/anthropics/skills) |
| UI craft and interaction details: easing, transitions, review | **Emil Kowalski's skills** | [emilkowalski/skills](https://github.com/emilkowalski/skills) |
| Interaction and accessibility review of web UI | **web-design-guidelines** (Vercel) | [vercel-labs/agent-skills](https://github.com/vercel-labs/agent-skills) |
| SwiftUI review | **swiftui-pro** (Paul Hudson) | [twostraws/SwiftUI-Agent-Skill](https://github.com/twostraws/SwiftUI-Agent-Skill) |
| Motion principles: timing, easing, choreography | **motion-design** (Zach Stevens), **motion-design-skill** (LottieFiles), **claude-motion** | [zstvns/design-skills](https://github.com/zstvns/design-skills), [LottieFiles/motion-design-skill](https://github.com/LottieFiles/motion-design-skill), [whaleyxbt/claude-motion](https://github.com/whaleyxbt/claude-motion) |
| Building animation timelines | **gsap-skills** (official GSAP) | [greensock/gsap-skills](https://github.com/greensock/gsap-skills) |
| 3D in the product (three.js / React Three Fiber) | **threejs-skills** | [CloudAI-X/threejs-skills](https://github.com/CloudAI-X/threejs-skills) |
| The app *is* a game | **awesome-gamedev-agent-skills** (Godot, Unity, Unreal, Phaser, three.js) | [gamedev-skills/awesome-gamedev-agent-skills](https://github.com/gamedev-skills/awesome-gamedev-agent-skills) |
**Read the brand first.** If the repo has `.agents/brand.md` or `.agents/design.md`, written by Zach's design skills, read them before choosing a direction. Use their colors, type, tokens and logo files, and never redraw the mark. If neither file exists and the product needs an identity, route to **brand** first.
**Theme tooling (an app, not a skill).** On a shadcn stack, **[Graphical](https://graphicalui.com)** (Josh Puckett) turns a chosen direction into a full theme: colors with light and dark values, type, spacing, icons, radii and shadows, component states, and motion. It installs through shadcn and can import the app's existing theme. If the repo has a `GUI.md` from it, read that before building UI, the same as `.agents/design.md`. It's an outside product, so name it and never install it or sign up without asking.
**Picking typefaces.** When the brand has no type yet, or the direction calls for a new face, shortlist from **[FaceTypes](https://facetypes.xyz)** (Tony McGuigan): a curated library of free and open-source fonts, sorted by classification and linked to each designer or official source. Before shipping one, confirm the licence at that source, download from there (not a mirror), and record the font, licence and source in the design record. Brand docs win: if `.agents/brand.md` names the type, use it.
**Order for a new web UI:** brand docs if any → impeccable or frontend-design for direction → Graphical for the theme, if the user uses it → hallmark to check it doesn't look generated → Emil's skills for interaction craft → web-design-guidelines for the accessibility review. For SwiftUI, use swiftui-pro instead of the last step.
**Motion is earned.** Add it when it explains a state change (saved, moved, expanded). Always respect reduced-motion settings. Motion is never the only cue that something happened.
**Not for app UI:** product demo stills and launch videos (benjitaylor/skills, Remotion), marketing pages (Zach's **web-design**, **marketing-website-design**) and decks, OG images and social posts (Zach's **collateral-design**) are launch assets. Hand them to the marketing skills.
If these recipes conflict (e.g. title case vs sentence case, or how much motion to use), resolve it in the brief and record the choice in the design record. A vendor checklist isn't accessibility certification.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| rea-analysis-optimizationmorluto/reaOptimize REA providers and shared analysis workflows for agent context, latency, CPU, and memory while preserving correctness and Evidence. Use for analysis bottlenecks and cache or query design; CI/test-suite optimization belongs to rea-ci-tests-audit. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| rea-ci-tests-auditmorluto/reaAudit REA CI and test suites for correctness, fixture drift, false passes, and measured performance; use for suite or workflow investigations and efficiency changes, rather than ordinary feature testing or a single test failure. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| rea-tool-designmorluto/reaAudit, investigate, design, or change REA investigation tools, CLI/MCP contracts, provider capabilities, and Evidence semantics. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-auditDietrichGebert/ponytailQuality audit of the whole repo: bugs, security, real load, missing tests, speed, and what to delete. Most important first. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |