Total 52,912 skills, Product & Design has 2010 skills
Showing 12 of 2010 skills
Designs interactive AR/VR experiences using 3D modeling, spatial computing, and user interface optimization.
Market positioning strategy using the April Dunford framework, enriched with JTBD discovery, Moore positioning statement, and Neumeier's Onliness Test. Produces a complete positioning document, positioning statement, competitive alternatives map, and market category analysis. Use when the user wants to define or refine their market positioning, find their unique position, differentiate from competitors, craft a positioning statement, choose a market category, or figure out "how should we position this product." Triggers for "positioning", "how to position", "market position", "differentiation strategy", "positioning statement", "competitive positioning", "category strategy", "where do we fit in the market", "how are we different", "unique value proposition", or any request to define, sharpen, or rethink positioning. Works standalone — no prior startup-design or startup-competitors session needed, but leverages their output if available.
Opinionated, evolving constraints to guide agents when building interfaces. Useful for keeping output coherent across many small UI pieces.
Color science expert skill with 286K words of reference material covering OKLCH/OKLAB, palette generation, accessibility/contrast, color naming, pigment mixing, and historical color theory.
两页跨页电子指南, 封面 + 课程页 + pull-quote + 步骤列表
Cream background + Soft light blob + Macaron rounded-corner card + Playfair italic numbering
Access and work with Keychron's production-grade CAD files for keyboards and mice to design compatible accessories and modifications
Guides product support specialist work—customer tickets about how the product works, configuration, permissions, workflows, and expected behavior; empathetic replies, triage and routing, macro and KB guidance, feature-request capture, and escalation to technical support or product when needed. Use when answering "how do I…" questions, clarifying plan limits, drafting support responses, deciding bug vs education vs config issue, or documenting feedback—not for deep log/API debugging and engineering repro (support-engineer), billing/dunning programs (customer-ops-specialist), exec/VIP escalation programs (community-executive-escalations-program-manager), or public API reference authoring (tech-writer-researcher), or structured developer training programs (developer-education-lead).
Apply the Doherty Threshold — keep system response times under 400ms to maintain user flow and perceived performance.
Decompose a game concept into individual systems, map dependencies, prioritize design order, and create the systems index.
Apply Hick's Law to reduce decision time by limiting the number of simultaneous choices presented to users.
Critique a screen's typography — scale usage, readability, consistency, and token compliance.