「design」の検索結果

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".

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

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.

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

Design a drift monitoring system for a production ML model. Use when asked to "monitor this model in production", "detect data drift", or "set up ML monitoring".

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

Spec or critique custom illustrations — style, composition, and brand alignment. Use when asked to "spec an illustration", "critique this illustration", or "define an illustration style".

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

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"

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

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".

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

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".

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

Audit existing icons and illustrations in a codebase — find inconsistencies, unoptimized SVGs, and accessibility gaps. Use when asked to "audit our icons and illustrations", "find unoptimized SVGs", or "find inconsistent assets".

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

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"

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

Hi-fi interactive HTML prototype — single-file, double-click-to-open, Playwright-verified. Use when asked to "make it clickable", "build a prototype", "hi-fi mockup", "interactive demo", "iOS prototype", "app mockup", "ui demo", or "prototype this". Goes beyond wireframes into visually finished, state-driven HTML with device frames and real images. Not production code — a design artifact for testing flows and pitching ideas.

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

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".

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

Usability review — evaluate an existing flow or UI against usability heuristics, flag friction points, and recommend fixes. Use when asked to "review the UX", "usability audit", "what's wrong with this flow", "UX feedback", "critique this design", or "why are users dropping off here".

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

Design eval harnesses — task schemas, metrics, dataset versioning, eval-as-code patterns. Use when asked to "build an eval harness", "set up eval-as-code", or "version our eval datasets".

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

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.

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

Audit existing caching implementation — find cache misses, stampedes, and key design issues. Use when asked to "audit our caching", "why is our hit rate low", or "find cache stampedes".

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

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 SBOM generation pipeline — format, tooling, and integration into CI/CD. Use when asked to "generate an SBOM", "build an SBOM pipeline", or "add CycloneDX to CI".

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

Write UX copy for a feature, flow, or component — buttons, errors, empty states, tooltips. Use when asked to "write the copy for this flow", "word this error message", or "write empty state copy".

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

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 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 game day — simulated failure scenario, runbook, and post-event review. Use when asked to "run a game day", "plan a failure drill", or "simulate an outage".

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

Design a data cleaning and transformation pipeline — missing values, outliers, and deduplication. Use when asked to "clean this dataset", "handle missing values", or "deduplicate this data".

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

Design and implement an AI feature integration — model selection, architecture pattern, system prompt, data flow, error handling, cost estimate. Use when asked to "add AI to this", "LLM integration", "add Claude/GPT", or "AI-powered feature".

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

Survey all user-facing strings in a codebase — map coverage and find gaps. Use when asked "what user-facing strings do we have", "map our copy coverage", or "find hardcoded strings".

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