UI/UX, 로고, 슬라이드, 이미지 생성 (7.4천건)
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 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 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".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Motion design — produce HTML animations and export MP4/GIF with optional BGM. Use when asked to "animate this", "create a motion design", "make an intro animation", "product launch animation", "promo video", "export MP4", "export GIF", "60fps animation", "animated logo", or "motion graphics". Delivers a self-contained HTML animation plus rendered video exports. Not for micro-interactions in production code — use /prism-ui for that.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Design performance management system - review cycles, calibration process, career ladder, and PIP framework. Use when asked to "build a performance review process", "design career levels", "how do we handle underperformers", or "run a review cycle".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Design or review org structure - spans of control, reporting lines, role clarity, headcount plan, and team topology. Use when asked to "design our org", "should we restructure", "what is the right team structure", or "plan headcount for next year".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Build a hiring pipeline - job description, sourcing strategy, interview scorecard, and offer process. Use when asked to "write a job description", "build an interview process", "design our hiring funnel", or "what should we look for in a [role]".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Design a reservation and savings plan strategy — commitment level, term, and coverage targets. Use when asked "should we buy reserved instances", "design a savings plan strategy", or "what commitment coverage do we need".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Design a model training pipeline — algorithm selection, cross-validation, and serialization. Use when asked to "train a model for this", "design a training pipeline", or "which algorithm should we use".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
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".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Design direction advisor — generates 3 differentiated visual directions with live HTML demos for selection. Use when the brief is vague ("make something nice", "pick a style", "explore directions"), when no design system exists, or when the user wants to compare visual approaches before committing. Richer than /form-style: produces actual visual demos, not just recommendations. Trigger words: "design direction", "style exploration", "pick a direction", "what should this look like", "give me options", "explore styles", "design philosophy".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
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".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
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 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".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
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".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
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 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".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
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".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
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"
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
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".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
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".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
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".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.