Plan a unit using backwards design from desired outcomes through assessment evidence to learning activities. Use when starting a new unit or redesigning an existing one from standards.
日本語の概要は準備中です。原文の説明を表示しています。
1.1万 件 ・ 関連度順
概要と使いどころ
Plan a unit using backwards design from desired outcomes through assessment evidence to learning activities. Use when starting a new unit or redesigning an existing one from standards.
日本語の概要は準備中です。原文の説明を表示しています。
Redesign a learning space using biophilic design principles to improve focus, calm, and wellbeing. Use when classroom environment contributes to restlessness, poor attention, or stress.
日本語の概要は準備中です。原文の説明を表示しています。
Design system reasoning. Maps product domain to style, palette, typography, and platform-specific patterns. Generates .rune/design-system.md as the shared design contract for all UI-generating skills.
日本語の概要は準備中です。原文の説明を表示しています。
Design and plan iOS animations with structured specs covering transitions, micro-interactions, gesture-driven motion, and loading states. Use when the user asks to plan, design, or spec out animations for an iOS app — including screen transitions, navigation animations, interactive gestures, onboarding flows, or any motion design work. Also use when the user wants animation recommendations or wants to decide between animation approaches before writing code.
日本語の概要は準備中です。原文の説明を表示しています。
Act as a product-manager copilot that turns evidence into product decisions and artifacts: backlogs and prioritization, PRDs and user stories, metrics and OKRs, experiments, launch plans, feedback triage, and pricing/packaging, kept in a per-product workspace. Use whenever the user wants to decide what to build, spec it, or ship it: "write a PRD for…", "prioritize our backlog", "what should we build next", "plan OKRs", "define our north star metric", "design an A/B test", "plan the launch", "triage this customer feedback", "platform or feature?", in any language ("viết PRD", "ưu tiên tính năng nào", "quản lý sản phẩm", "プロダクト管理", "产品经理"), even when they never say "product manager". Also use when the user returns to a product workspace this skill created (a directory holding `product.md`, `state.md`, and `decisions.md`). Not for deep user discovery (design-thinking), desk market facts (market-researcher), or company-level bets (strategy-board).
CSS design tokens and color system for vehicle insurance platform. Use when defining colors, spacing, typography, or design variables. Keywords: eye-care colors #5B8DEF/#8B95A5/#C5CAD3, CSS variables, spacing system, color palette, typography scale, design tokens, variables.css, theme colors.
日本語の概要は準備中です。原文の説明を表示しています。
Design a multi-cloud or cloud portability strategy — provider selection, workload placement, and lock-in management. Use when asked "should we go multi-cloud", "design for cloud portability", or "where should this workload run".
日本語の概要は準備中です。原文の説明を表示しています。
Design a service mesh deployment — technology selection, mTLS policy, and traffic management config. Use when asked "should we use a service mesh", "Istio or Linkerd", or "design our mTLS policy".
日本語の概要は準備中です。原文の説明を表示しています。
Design guardrail layers — input classifiers, output validators, PII scrubbers, policy rule engines. Use when asked to "add safety filters", "scrub PII from LLM output", or "design content moderation".
日本語の概要は準備中です。原文の説明を表示しています。
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 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 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".
日本語の概要は準備中です。原文の説明を表示しています。
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".
日本語の概要は準備中です。原文の説明を表示しています。
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 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 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".
日本語の概要は準備中です。原文の説明を表示しています。
Analyzes and reverse-engineers website designs directly from a target URL, extracting layout structures, design tokens (colors, typography, spacing), component hierarchies, visual assets, and responsive behaviors to enable full 1:1 duplication into modern code (Tailwind CSS v4, React/Next.js, HTML/CSS). / Mempelajari dan merekayasa balik desain situs web langsung dari URL target, mengekstrak struktur layout, design token (warna, tipografi, spacing), hierarki komponen, aset visual, dan perilaku responsif untuk duplikasi 1:1 penuh ke kode modern.
日本語の概要は準備中です。原文の説明を表示しています。
Design and analysis of combinational and sequential digital circuits using Boolean algebra, truth tables, K-maps, CMOS gate implementation, flip-flops, registers, counters, and finite state machines. Covers De Morgan's theorems, canonical sum-of-products and product-of-sums forms, minimization techniques, propagation delay, setup and hold times, metastability, synchronous design discipline, and FSM encoding. Use when designing, minimizing, verifying, or debugging any circuit whose signals take only discrete logic values.
日本語の概要は準備中です。原文の説明を表示しています。
Create distinctive, production-grade frontend interfaces with high design quality that avoids generic AI aesthetics. Use when the task involves `build web components`, `create frontend interface`, `build web page`, `build web application`, `frontend design`, `create UI component`, or `design web interface`.
日本語の概要は準備中です。原文の説明を表示しています。
Create beautiful visual art in .png and .pdf documents using design philosophy. Use when the user asks to create a poster, piece of art, design, or other static visual piece. Creates original visual designs.
日本語の概要は準備中です。原文の説明を表示しています。
Purpose: Standardize how stakpak designs and optimizes AWS architectures. Scope: Greenfield: design new infrastructure. Brownfield: analyze existing architectures and propose improvements.
日本語の概要は準備中です。原文の説明を表示しています。
Interviews a researcher in rounds (idea, design, or defend stage) until no decision in a research idea, design, or draft is left assumed, recommending an answer to each question and writing settled decisions to a file. Use for 'grill me', stress-testing a design, or an idea not yet a design; --plan for software or process plans.
日本語の概要は準備中です。原文の説明を表示しています。
Designs conjoint and factorial-vignette experiments, covering attribute architecture and randomization restrictions, effective-N power, treatment realism, the choice among AMCE, marginal-mean, and AMIE estimands, forced-choice versus rating designs, and PAP tiers. Use when the user is planning a conjoint, drafting or critiquing an attribute table, asking how many respondents or tasks are needed, whether to report AMCEs or marginal means, or how to test interactions. Reviewing an existing design goes to conjoint-diagnostics, cleaning the export to conjoint-cleaning.
日本語の概要は準備中です。原文の説明を表示しています。
Reviews an existing conjoint study for threats to inference and returns severity-ranked findings on design integrity, estimation, measurement error, external validity, and interpretation, including the guardrail against reading an AMCE as majority preference. Use when the user asks whether a conjoint design or analysis holds up, has referee comments on a conjoint, or wants a second opinion on estimation or interpretation. New designs go to conjoint-design, reshaping to conjoint-cleaning.
日本語の概要は準備中です。原文の説明を表示しています。