Loading...
Loading...
Found 61 Skills
Guides product management for human data platforms—annotation and labeling products, workforce workflows, task design, quality systems (gold sets, adjudication, inter-annotator agreement), customer ML-team project delivery, contributor experience, and privacy-safe handling of human-generated training data. Use when prioritizing roadmap for labeling/RLHF/eval data platforms, writing PRDs for annotation or QA features, defining success metrics for throughput and quality, scoping enterprise customer workflows, or balancing cost-quality-speed tradeoffs—not for hands-on model training (data-scientist), warehouse/analytics pipelines (data-warehouse-engineer), generic BRD workshops without product lens (business-analyst), AI solution architecture for copilots (applied-ai-architect-commercial-enterprise), or control implementation for audits (compliance-engineer). UX flows: product-designer. Eval harnesses: prompt-engineer-agent-prompts-evals. Pricing/packaging for platform: product-management-monetization.
Write a PRODUCT.md spec for a significant user-facing feature in Warp, focused on detailed behavior and validation. Use when the user asks for a product spec, desired behavior doc, or PRD, wants to define feature behavior before implementation, or when the feature is substantial or behaviorally ambiguous enough that a written spec would improve implementation or review.
Audits existing surface against lower-layer decisions and produces a surface decision inventory — vocabulary, object consistency, completeness, feedback, hierarchy, accessibility
Critical-thinking brainstorming partner that acts as a requirements analyst. Use when users present ideas, feature requests, or problems they want to solve. Triggers include "I want to build", "help me validate", "users need", "I'm thinking of creating", or any request involving problem/solution validation. This skill aggressively challenges assumptions, questions perceived problems, demands evidence, and ensures solutions address genuine needs before exploring implementation.
Apply when facing a novel UI interaction or architectural decision with no precedent in the codebase. Build 2-3 competing prototypes and compare side by side before committing.
Apply Apple's 8 foundational design principles (from WWDC26) to review, critique, score, or generate UI/UX decisions. Use this skill whenever the user wants to evaluate a design, review a screen or flow, audit a feature for design quality, decide what to build or cut, check if a UI feels right, or think through how to design something for iPhone/Mac/Apple platforms. Also trigger when the user asks "is this good design?", "what's wrong with this UI?", "how should I design X?", or "review this from a design perspective." Don't wait for the user to explicitly say "Apple design principles" — invoke whenever the conversation is clearly about design quality, UX decisions, or product design critique.
Create wireframes and interactive prototypes to visualize user interfaces and gather feedback early. Use tools and techniques to communicate design ideas before development.
Builds features based on Jobs-to-be-Done theory using Bob Moesta's frameworks. Use when designing features, identifying customer jobs, understanding push/pull forces, or uncovering hidden needs beyond stated feature requests.
Motivation science framework based on Daniel Pink's "Drive". Use when you need to: (1) design features that leverage intrinsic motivation, (2) create progress systems that support mastery, (3) craft purpose-driven messaging and missions, (4) audit if product mechanics undermine autonomy, (5) design team structures and incentives with AMP principles (Autonomy, Mastery, Purpose), (6) understand why gamification fails, (7) replace carrot-and-stick approaches with intrinsic motivation.
Create detailed user personas based on research and data. Develop realistic representations of target users to guide product decisions and ensure user-centered design.
Guides structured ideation through Socratic questioning to explore problems, opportunities, and solutions. Use when brainstorming features, exploring use cases, or thinking through new ideas.
Improve unclear UX copy, error messages, microcopy, labels, and instructions to make interfaces easier to understand. Use when the user mentions confusing text, unclear labels, bad error messages, hard-to-follow instructions, or wanting better UX writing.