Total 43,865 skills, Product & Design has 1646 skills
Showing 12 of 1646 skills
Convert a public brand URL into a practical DESIGN.md file and optional single-file HTML demo. Use when the user asks to extract, distill, compile, generate, or validate a DESIGN.md/design system from a website, brand page, press kit, or public visual identity.
Strict slide-style extraction skill. Converts one or more reference slide images into a reusable DESIGN.md for future deck generation. Focuses on presentation design, not semantic content.
Persuasive deck-planning skill. Uses extracted DESIGN.md, user files, and the user's goal to decide slide ordering, page count, evidence placement, and narrative flow in JSON.
Analyze Sentry session replays to surface UX patterns, pain points, and user journeys for a given product area. Use when asked to "show me how users use", "day in the life", "UX research", "replay research", "how do customers use", "what's the user experience like for", "watch replays of", "analyze replays for", "user behavior on", or "replay UX audit" for any Sentry product surface.
Pendo platform help — product analytics, in-app guides, session replay, NPS/CSAT surveys, feature adoption tracking, Leo AI. Use when Pendo guides aren't showing, feature tagging is tedious, analytics data looks wrong, users aren't completing onboarding, NPS scores are flat, need help with Pendo API or aggregation queries, setting up Pendo for the first time, or comparing Pendo to Appcues or WalkMe. Do NOT use for in-app messaging strategy across platforms (use /sales-in-app-messaging) or general customer feedback strategy (use /sales-customer-feedback).
Build the initial design structure from a vague or partially formed idea. Use when the task lacks a clear design tree, scope boundaries, core objects, key flows, or explicit decision points. Trigger when the user has an idea, feature request, or system goal that needs to be turned into a structured design skeleton before deeper refinement. Do not use when the design tree already exists and the main need is to deepen or validate it.
Internal/shared core rules for design-tree skills. Use only when maintaining the design-tree system itself or when another design skill needs shared governance rules for derivation, handoff, boundaries, or anti-bloat controls. Do not trigger for ordinary user design requests, and do not use as a replacement for design-orchestrator, design-structure, or design-refinement.
Check whether a design is complete enough to move into implementation planning. Use when a design appears mostly done and needs a final readiness review for missing branches, weak assumptions, unresolved risks, failure handling, validation gaps, or non-functional omissions. Trigger before invoking writing-plans or when the user asks whether the current design is ready to implement. Do not use as a general design-document audit for external docs or as a replacement for initial design work.
Coordinate design-stage work across specialized design skills. Use when a task needs structured design before implementation, including design decomposition, design clarification, decision routing, or readiness checks. Trigger whenever the user wants to turn an idea into an implementation-ready design, refine a partially formed design, or determine the next design step. Do not use for direct execution, implementation planning, or single-step coding tasks.
Refine an existing design tree until key branches become implementation-ready. Use when the high-level structure already exists but important branches remain vague, shallow, or unresolved. Trigger when the user needs deeper decomposition, edge-case coverage, failure-path clarification, interface detail, or validation criteria for a partially designed system. Do not use to create the initial design skeleton from scratch or to compare options for a single explicit decision node.
Scroll areas inside a layout should be avoided wherever possible. When unavoidable, allow only one scroll axis at a time and always keep the user in control. Use when designing layouts, data tables, panels, or any component that might introduce an inner scroll container.
Use when designing motion paths, character movement trajectories, gesture animations, or any motion that should feel natural rather than robotic.