「exam」の検索結果

Use when asked to analyze a funnel, find where users drop off, diagnose low conversion or activation rates, design a metrics framework, set up OKRs, or measure whether a feature is working. Examples: "analyze our funnel", "why is activation low", "where are users dropping off", "design OKRs for this quarter", "is this feature working", "set up metrics for this launch".

日本語の概要は準備中です。原文の説明を表示しています。

Use when asked to write a product brief, turn a feature idea into a spec, define requirements for something to build, or clarify what a product should do and why. Examples: "write a brief for X", "turn this idea into a spec", "what should we build here", "help me define requirements".

日本語の概要は準備中です。原文の説明を表示しています。

Use when asked to build a product roadmap, prioritize a backlog, decide what to build next, or sequence a list of feature ideas. Examples: "what should we build next", "prioritize this backlog", "make a roadmap", "RICE score these features".

日本語の概要は準備中です。原文の説明を表示しています。

Use when a product brief is finalized and ready to hand off to the engineering team, or when asked to send a brief to Apex, kick off engineering work, or start development on a product spec. Examples: "hand this off to engineering", "send brief to Apex", "start building this", "kick off dev on this spec".

日本語の概要は準備中です。原文の説明を表示しています。

Use when asked to design a landing page, marketing website, or any web presence intended to convert or inform. Examples: "design a landing page for X", "create a marketing site", "we need a homepage", "design our website", "build a page for our launch".

日本語の概要は準備中です。原文の説明を表示しています。

Use when asked to generate a color palette, create industry-matched colors, or pick colors for a product type. Examples: "color palette for fintech", "healthcare app colors", "SaaS brand colors"

日本語の概要は準備中です。原文の説明を表示しています。

Use when asked to audit UI for visual quality, check design consistency, review brand alignment, evaluate design system compliance, or find visual issues before a launch. Examples: "audit our UI", "check visual consistency", "review the design for issues", "is our UI on-brand", "find visual bugs", "design QA before launch".

日本語の概要は準備中です。原文の説明を表示しています。

Use when asked to create a logo, design a brand mark, generate a logo concept, or produce any logo asset. Examples: "create a logo for X", "design a brand mark", "make me a logo", "generate logo concepts", "logo for our product".

日本語の概要は準備中です。原文の説明を表示しています。

Use when asked to design a UI component, specify a button, input, card, modal, badge, or any interactive element. Examples: "design a button component", "spec out the input field", "define the card component states", "create a component spec for Prism", "what should the dropdown look like".

日本語の概要は準備中です。原文の説明を表示しています。

Use when asked to design social media graphics, ad creatives, or marketing assets. Examples: "design a LinkedIn post for our launch", "create ad creatives for our campaign", "make an Instagram story", "design a Twitter card", "create a banner ad", "social assets for the product announcement".

日本語の概要は準備中です。原文の説明を表示しています。

Use when asked to define a design token system, create tokens, document tokens, set up CSS custom properties, build a Tailwind token config, establish a spacing scale, define color semantics, or bridge design decisions to code. Examples: "set up design tokens", "define our token system", "create CSS variables for the design system", "document our color tokens", "establish a spacing scale".

日本語の概要は準備中です。原文の説明を表示しています。

Use when asked to design an email template, newsletter, drip campaign email, transactional email, or any HTML email asset. Examples: "design a welcome email", "create a newsletter template", "make an onboarding email sequence", "design a password reset email", "build an email campaign".

日本語の概要は準備中です。原文の説明を表示しています。

Use when asked to select a UI style, choose a design direction, pick a visual approach for a product, or match a style to an industry. Examples: "what style fits a fintech app", "choose between neumorphism and glassmorphism", "design direction for healthcare SaaS"

日本語の概要は準備中です。原文の説明を表示しています。

Use when asked to design a pitch deck, presentation, or slide set. Examples: "design a pitch deck", "create a sales deck", "make a conference presentation", "build an investor deck", "help me present this to the board", "create slides for X".

日本語の概要は準備中です。原文の説明を表示しています。

Use when asked to design iOS or Android mobile app screens, create mobile UI, spec mobile flows, or produce screen designs for a native app. Examples: "design the onboarding screens", "spec the checkout flow for iOS", "design a home screen for Android", "create mobile UI for this feature".

日本語の概要は準備中です。原文の説明を表示しています。

Use when asked to create a brand identity, define visual design direction, generate a color palette or type system, build a style guide, or establish the look and feel for a product. Examples: "create a brand for X", "define the visual identity", "what colors should we use", "build a style guide", "design system foundations".

日本語の概要は準備中です。原文の説明を表示しています。

Use when asked to design a user flow, map how a user moves through a feature, create a wireframe or flow diagram, or document interaction design for a product brief. Examples: "design the flow for X", "map out the user journey", "create a wireframe for this feature", "how should the UX work for this".

日本語の概要は準備中です。原文の説明を表示しています。

Use when asked to structure a landing page, design page layout for conversion, or plan landing page information architecture. Examples: "landing page structure for SaaS", "conversion-optimized layout"

日本語の概要は準備中です。原文の説明を表示しています。

Use when asked about UX patterns, interaction best practices, form design, navigation patterns, or loading states. Examples: "best practice for form validation", "navigation pattern for dashboard", "loading state UX"

日本語の概要は準備中です。原文の説明を表示しています。

Build a production-ready prompt package — system prompt, few-shot examples, output format, edge case handling, eval criteria. Use when asked to "prompt engineering", "build a prompt", "write a system prompt", or "improve this prompt".

日本語の概要は準備中です。原文の説明を表示しています。

Systematic materials selection for engineering design using performance indices, Ashby charts, multi-constraint optimization, and case-based reasoning. Covers the five-step Ashby method — function, objective, constraint, free variable, index — with worked examples for stiffness-limited beams, strength-limited ties, thermally shocked vessels, and minimum-cost components. Use when choosing among metals, polymers, ceramics, and composites under competing objectives.

日本語の概要は準備中です。原文の説明を表示しています。

Catalog of informal fallacies with definitions, canonical examples, and detection heuristics. Covers relevance fallacies (ad hominem, straw man, red herring, appeal to authority, appeal to emotion), presumption fallacies (false dichotomy, complex question, begging the question), ambiguity fallacies (equivocation, amphiboly, accent), causal fallacies (post hoc, slippery slope, correlation-causation), and statistical fallacies (hasty generalization, cherry-picking). Use when evaluating arguments for rhetorical or informal reasoning errors.

日本語の概要は準備中です。原文の説明を表示しています。

Performs initial binary triage by surveying memory layout, strings, imports/exports, and functions to quickly understand what a binary does and identify suspicious behavior. Use when first examining a binary, when user asks to triage/survey/analyze a program, or wants an overview before deeper reverse engineering.

日本語の概要は準備中です。原文の説明を表示しています。

This skill should be used when the user asks to "create an agent", "add an agent", "write a subagent", "agent frontmatter", "when to use description", "agent examples", "agent tools", "agent colors", "autonomous agent", or needs guidance on agent structure, system prompts, triggering conditions, or agent development best practices for Claude Code plugins.

日本語の概要は準備中です。原文の説明を表示しています。