UI/UX、ロゴ、スライド、画像生成（7,400 件）
Cold outbound sequence builder — produces multi-touch email + LinkedIn sequences (5-7 touchpoints) personalized by persona type (technical buyer, economic buyer, champion). Use when asked to "write cold emails", "build an outbound sequence", "create prospecting emails", "write my LinkedIn outreach", or "design a cold email campaign".
日本語の概要は準備中です。原文の説明を表示しています。
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"
日本語の概要は準備中です。原文の説明を表示しています。
Design an LLM eval — task schema, scoring rubric, dataset composition, and pass/fail thresholds. Use when asked to "design an LLM eval", "write a scoring rubric", or "how do we measure this model".
日本語の概要は準備中です。原文の説明を表示しています。
Design a CDN configuration — caching rules, TTLs, and origin shield setup. Use when asked to "configure the CDN", "set cache headers", or "set up an origin shield".
日本語の概要は準備中です。原文の説明を表示しています。
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"
日本語の概要は準備中です。原文の説明を表示しています。
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".
日本語の概要は準備中です。原文の説明を表示しています。
Wireframe a screen — text/ASCII by default, or hand-drawn HTML when the user says "sketch", "hand-drawn", "lo-fi HTML", "whiteboard", "graph paper", or "visual wireframe". Text mode produces a buildable ASCII spec Form and Prism can act on. HTML mode produces a single self-contained file with graph-paper background, marker headlines, sticky-note annotations, and hatched chart placeholders — looks like a designer's whiteboard, commits to nothing.
日本語の概要は準備中です。原文の説明を表示しています。
Close a specific deal — diagnose why a deal is stalling, answer an objection reply, write a tailored proposal, design the closing sequence, or navigate procurement. Use when a specific deal is stuck, "how do I close this", "write a proposal for this customer", "help me get to yes", or "how do I answer this objection".
日本語の概要は準備中です。原文の説明を表示しています。
Design an A/B test — power analysis, randomization, and success metrics. Use when asked to "design an A/B test", "how many users do we need", or "run a power analysis".
日本語の概要は準備中です。原文の説明を表示しています。
Design an edge routing and geo-distribution strategy — latency routing, failover, and edge logic. Use when asked to "geo-route our traffic", "reduce global latency", or "design edge failover".
日本語の概要は準備中です。原文の説明を表示しています。
Design drift alerts and escalation — thresholds, runbooks, and retrain triggers. Use when asked to "alert on model drift", "when should we retrain", or "write a drift escalation runbook".
日本語の概要は準備中です。原文の説明を表示しています。
UX designer — user flows, information architecture, wireframes, and interaction design. Use when asked to "design a user flow", "map the IA", "wireframe this screen", or "review UX before shipping".
日本語の概要は準備中です。原文の説明を表示しています。
UI and UX reconnaissance — scan existing frontend routes, components, navigation, and flows to understand the current UX state before designing. Use when asked to "understand the current UI", "what UX patterns exist", "map the navigation", "what screens exist", or before starting any flow or wireframe work.
日本語の概要は準備中です。原文の説明を表示しています。
Information architecture — design navigation structure, content hierarchy, sitemap, and taxonomy for a product or feature set. Use when asked to "organize the navigation", "information architecture", "how should content be structured", "sitemap", "nav redesign", "where should X live", or "content hierarchy".
日本語の概要は準備中です。原文の説明を表示しています。
Design pricing strategy and packaging — tiers, value metrics, enterprise pricing, freemium design, and pricing page copy. Use when asked to "design our pricing", "should we change our price", "how do we package the product", or "what should we charge enterprise".
日本語の概要は準備中です。原文の説明を表示しています。
Write sales playbooks — outbound sequences, discovery call guides, objection handling scripts, and demo frameworks. Use when asked to "write a sales playbook", "build an outbound sequence", "help me handle objections", or "design a discovery call".
日本語の概要は準備中です。原文の説明を表示しています。
Design embedding pipelines — model selection, batching, normalization, index refresh strategy. Use when asked to "design an embedding pipeline", "which embedding model should we use", or "how should we batch embeddings".
日本語の概要は準備中です。原文の説明を表示しています。
OKR design — create objectives and key results with a North Star metric, input metrics tree, and cadence. Use when asked to "set OKRs", "define our objectives", "what should we measure this quarter", "design our OKR framework", "build a metrics tree", or "what's our North Star".
日本語の概要は準備中です。原文の説明を表示しています。
Design a caching strategy for an application — pattern selection, key design, TTL, and eviction policy. Use when asked to "add caching to this", "design a cache strategy", or "what should we cache".
日本語の概要は準備中です。原文の説明を表示しています。
Design and execute a launch plan — Product Hunt, HN Show HN, newsletter coordination, social posts, and community launch moment. Use when asked to "launch [feature/product]", "plan a launch", "help us do a Product Hunt launch", or "coordinate the announcement".
日本語の概要は準備中です。原文の説明を表示しています。
Design an API compatibility and deprecation policy — stability tiers, sunset timelines, and CI gates. Use when asked to "define an API stability policy", "set our deprecation timeline", or "write semver rules".
日本語の概要は準備中です。原文の説明を表示しています。
Design an API versioning and deprecation policy — semver rules, sunset timelines, and communication channels. Use when asked to "design a deprecation policy", "how should we version the API", or "set a sunset timeline".
日本語の概要は準備中です。原文の説明を表示しています。
Design a dependency scanning program — CVE detection, license checks, and CI gates. Use when asked to "scan our dependencies", "set up CVE detection", or "add a dependency CI gate".
日本語の概要は準備中です。原文の説明を表示しています。
Design a chaos engineering experiment — hypothesis, blast radius, steady state, and abort conditions. Use when asked to "design a chaos experiment", "inject a failure", or "test the resilience of this service".
日本語の概要は準備中です。原文の説明を表示しています。