2,452 件 ・ 関連度順
概要と使いどころ
Design an animation spec for a component or interaction — timing, easing, and keyframes. Use when asked to "animate this component", "spec the transition", or "define easing and timing for this interaction".
日本語の概要は準備中です。原文の説明を表示しています。
Design an asset library structure — naming conventions, formats, and delivery specs. Use when asked to "organize our brand assets", "define asset naming conventions", or "spec logo delivery formats".
日本語の概要は準備中です。原文の説明を表示しています。
Design a vulnerability management program — SLAs, asset tiers, escalation, and metrics. Use when asked to "design a patching program", "set vulnerability SLAs", or "define our patch cadence".
日本語の概要は準備中です。原文の説明を表示しています。
Analytics reconnaissance for takeover — find all analytics tools, inventory what's tracked and dashboarded, assess data freshness and metric definitions, and present a coverage map. Use when asked "what analytics exist", "BI assessment", or "what do we track".
日本語の概要は準備中です。原文の説明を表示しています。
Design a color palette with semantic tokens for a brand or product. Use when asked to "design a color palette", "what colors should we use", or "define semantic color tokens".
日本語の概要は準備中です。原文の説明を表示しています。
Design a type scale and hierarchy — sizes, weights, line-heights, and named tokens. Use when asked to "design a type scale", "set up type hierarchy", or "define typography tokens".
日本語の概要は準備中です。原文の説明を表示しています。
Audit or redesign responsive behavior of a layout — breakpoints, reflow, and content priority. Use when asked to "fix responsive behavior", "define breakpoints", or "how should this reflow on mobile".
日本語の概要は準備中です。原文の説明を表示しています。
Design a customer health scoring model — define signals, weights, thresholds, and action triggers. Use when asked to "build health scoring", "how do we predict churn", "what signals indicate a customer is at risk", or "design our health model".
日本語の概要は準備中です。原文の説明を表示しています。
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 a hyperparameter tuning strategy for a model — search space, method, and budget. Use when asked to "tune hyperparameters", "define a search space", or "set a tuning budget".
日本語の概要は準備中です。原文の説明を表示しています。
Translate a design brief — structured I-Lang or plain English — into a concrete DESIGN.md and optional HTML token preview. Resolves 8 dimensions (palette, accent, typography, display font, layout, mood, density, constraints) to specific CSS tokens. Use when asked to "create a design brief", "write a DESIGN.md", "define the design system", "design brief for X", "what tokens should we use", or "I-Lang brief".
日本語の概要は準備中です。原文の説明を表示しています。
Document and strengthen company culture - values articulation, team norms, communication protocols, and culture health diagnostics. Use when asked to "define our values", "document how we work", "diagnose culture health", or "write team norms".
日本語の概要は準備中です。原文の説明を表示しています。
User segmentation and persona creation from mixed data sources — analytics, CRM, support tickets, reviews, or any combination. Use when asked to "build personas", "who are our users", "segment our users", "create user profiles", "define user archetypes", or "who is the target user".
日本語の概要は準備中です。原文の説明を表示しています。
Revenue reconnaissance — audit current sales pipeline, deal patterns, ICP definition, and revenue motion to understand what's working and where the constraint is. Use when asked to "audit our sales", "where is revenue stuck", "what's our pipeline state", "before designing a playbook".
日本語の概要は準備中です。原文の説明を表示しています。
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".
日本語の概要は準備中です。原文の説明を表示しています。
Design a data validation pipeline — schema checks, range validation, and quality metrics. Use when asked to "validate incoming data", "add schema checks", or "define data quality metrics".
日本語の概要は準備中です。原文の説明を表示しています。
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 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".
日本語の概要は準備中です。原文の説明を表示しています。
Define semantic type detectors in detectors.js for auto-detecting column data meaning
日本語の概要は準備中です。原文の説明を表示しています。
Light, dark or both, and when a theme selector is worth it. Use when defining a base palette or deciding on dark mode support.
日本語の概要は準備中です。原文の説明を表示しています。
rem, px or relative units for each kind of value. Use when defining spacing and sizing tokens, control heights or media queries, or when a layout breaks under enlarged text.
日本語の概要は準備中です。原文の説明を表示しています。
Ratio-based type scale where every size relates to the others. Use when defining font sizes or type tokens, or when typography feels arbitrary.
日本語の概要は準備中です。原文の説明を表示しています。
Conducts a systematic related-work / literature-survey / state-of-the-art review for a research question by defining survey dimensions, searching each axis, building a taxonomy of prior work, identifying the gap, and producing a positioning narrative for a paper's Related Work section. Goes beyond a flat paper list to deliver structured analysis. Use when the user is starting a new research project and needs to map the landscape, asks "what's been done on X?" or "how does my idea compare to existing work?", needs to write or revise a Related Work / Background / Prior Art section, wants to identify a research gap or position their contribution, or asks to build a taxonomy of approaches in a research area.
日本語の概要は準備中です。原文の説明を表示しています。
Provides Site Reliability Engineering best practices for SLOs, SLIs, SLAs, error budgets, toil reduction, reliability reviews, and capacity planning. Use when defining service objectives, measuring reliability, reducing toil, planning capacity, or when user mentions 'SRE', 'SLO', 'SLI', 'SLA', 'error budget', 'toil', 'reliability', 'on-call', 'capacity planning'.
日本語の概要は準備中です。原文の説明を表示しています。