7,557 件 ・ 関連度順
概要と使いどころ
Build UIs with @nuxt/ui v4 — 125+ accessible Vue components with Tailwind CSS theming. Use when creating interfaces, customizing themes to match a brand, building forms, or composing layouts like dashboards, docs sites, and chat interfaces.
日本語の概要は準備中です。原文の説明を表示しています。
Suite of tools for creating elaborate, multi-component Codex.ai HTML artifacts using modern frontend web technologies (React, Tailwind CSS, shadcn/ui). Use for complex artifacts requiring state management, routing, or shadcn/ui components - not for simple single-file HTML/JSX artifacts.
日本語の概要は準備中です。原文の説明を表示しています。
Provides GKE golden path configuration defaults, production readiness checklists, and cluster default patterns. Use when designing GKE clusters, verifying GKE production readiness, or checking configurations against GKE defaults. Don't use for setting up workload autoscaling specifically (use gke-workload-scaling instead).
日本語の概要は準備中です。原文の説明を表示しています。
Plans, configures, and manages core GKE cluster networking. Covers private clusters, VPC-native configurations, DNS, node egress, Dataplane V2, and IP planning. Use when designing GKE networking layouts, configuring private clusters, setting up Dataplane V2, planning GKE IP ranges, or managing VPC- native cluster modes. Don't use for application ingress, load balancing, or service networking (use gke-service-networking instead).
日本語の概要は準備中です。原文の説明を表示しています。
Suite of tools for creating elaborate, multi-component claude.ai HTML artifacts using modern frontend web technologies (React, Tailwind CSS, shadcn/ui). Use for complex artifacts requiring state management, routing, or shadcn/ui components - not for simple single-file HTML/JSX artifacts.
日本語の概要は準備中です。原文の説明を表示しています。
Design a research study. Use when the user says "study design", "design my research", "what research method should I use", "how do I test this hypothesis", "research plan", "methodology section", "experimental design", "survey design", "qualitative study design", "how to structure my study", "sample size", "data collection plan", or needs to plan how to test a research question or hypothesis - even if they don't explicitly say "study design".
日本語の概要は準備中です。原文の説明を表示しています。
Extract UX tasks from a product spec and save as ux-tasks.md in the same spec folder. Use this skill when: - The user wants to generate UX work items from a spec - The user says "UX tasks", "what does UX need to do", "extract UX work", "UX deliverables" - The user wants to hand off a spec to the UX/design team - The user asks "what screens need designing" or "what UX decisions are open"
日本語の概要は準備中です。原文の説明を表示しています。
Design retention and engagement features using the Hook Model. Use when the user says "improve retention", "reduce churn", "make it habit-forming", "engagement design", "hook model", "trigger action reward", "users aren't coming back", "increase DAU/MAU", or wants to design features that bring users back repeatedly - even if they don't explicitly say "Hook Model".
日本語の概要は準備中です。原文の説明を表示しています。
Design product experiments to test hypotheses. Use when the user says "run an experiment", "A/B test this", "build-measure-learn", "validate this assumption", "test this hypothesis", "we don't know if this will work", "minimum viable test", "lean experiment", or wants to reduce risk before fully building a feature - even if they don't explicitly say "experiment".
日本語の概要は準備中です。原文の説明を表示しています。
Design clean and consistent APIs. Use when the user says "design an API", "API design review", "design these endpoints", "REST API for X", "GraphQL schema", "API contract", "how should this endpoint work", "review my API design", or wants to create or improve an API interface - even if they don't explicitly say "API design".
日本語の概要は準備中です。原文の説明を表示しています。
Rewrite UI copy directly on Figma files to be simpler, jargon-free, and terminologically consistent. Trigger when: user says "rewrite copy", "simplify copy", "fix the text", "copy audit", "UX copy review", "clean up the wording", shares a Figma URL and mentions copy/text/wording, or asks to make text simpler/clearer/more consistent on a Figma file.
日本語の概要は準備中です。原文の説明を表示しています。
Document a design system component. Use when the user says "design system docs", "document this for the design system", "add this to the design system", "design token", "component library docs", "style guide", "design system entry", or wants to formally document a pattern, component, or token for team-wide use - even if they don't explicitly say "design system".
日本語の概要は準備中です。原文の説明を表示しています。
Build interactive "living workflow" flowcharts in the visual style of https://statuesque-starship-49757d.netlify.app/revenue-engine - vanilla HTML/CSS/JS files with a horizontal step bar, a vertical trunk that grows per step, tool-to-tool columns with animated payload pills between brand-marked tool nodes, alternating left/right step descriptions, and per-step outputs. Use whenever the user says "build a flowchart", "interactive flowchart", "living workflow", "revenue engine flowchart", "demand gen flowchart", "GTM workflow diagram", "process diagram with animations", "Nebor-style flowchart", or asks to recreate the workflow visual from the Nebor site. Always asks which flowchart to build (Revenue Engine / Demand Gen / CRM & RevOps / Custom) and waits for explicit approval of the step + tool + edge table before generating any files.
日本語の概要は準備中です。原文の説明を表示しています。
Critique a design for usability, hierarchy, and accessibility. Use when the user says "critique this design", "review this screen", "what's wrong with this UI", "design feedback", "UX review", "how can I improve this", "review my mockup", "is this good UX", or shares a design and wants structured feedback - even if they don't explicitly say "design critique".
日本語の概要は準備中です。原文の説明を表示しています。
Design a 100-day customer onboarding plan with phase gates based on Never Lose a Customer Again by Joey Coleman. Use when user says "onboarding plan", "new customer onboarding", "customer kickoff", "first 90 days", "activation plan", "customer launch plan", "new customer journey", or "implementation plan" - even if they don't say "100 days" explicitly. Applies to CSMs designing structured onboarding programs that move customers from signed contract to full adoption.
日本語の概要は準備中です。原文の説明を表示しています。
Write a component spec for engineering handoff. Use when the user says "component spec", "design handoff", "spec this component", "document this component for engineering", "Figma handoff", "component documentation", "how do I hand this off", or needs to communicate a UI component design to developers - even if they don't explicitly say "component spec".
日本語の概要は準備中です。原文の説明を表示しています。
Use when a task needs the judgment of an Emergency Management Director — activating and staffing an EOC for a developing hazard, sequencing a disaster declaration and FEMA Public Assistance/Individual Assistance request, sizing shelter and resource needs against real population and capacity numbers, designing or critiquing a tabletop exercise, or writing an after-action report and improvement plan.
日本語の概要は準備中です。原文の説明を表示しています。
Use when a task needs the judgment of an Economics Teacher, Postsecondary — designing an intro micro/macro sequence for a mostly-terminal non-major audience, diagnosing a miskeyed or poorly discriminating exam item, calibrating TA grading on graphical or free-response problem sets, or investigating a spike in homework answers matching an online solution bank.
日本語の概要は準備中です。原文の説明を表示しています。
Use when a task needs the judgment of an Environmental Restoration Planner — screening or comparing CERCLA/RCRA remedial alternatives against the nine evaluation criteria, building a life-cycle cost estimate for a Feasibility Study, scoping a stream or wetland restoration design against a reference reach, sizing compensatory mitigation credits, drafting a Statement of Work or Remedial Action Work Plan, or scoping a Five-Year Review for a site with land-use controls in place.
日本語の概要は準備中です。原文の説明を表示しています。
Use when a task needs the judgment of a drywall and ceiling tile installer — specifying a fire-rated wall/ceiling assembly to a UL design number, hitting an STC target on a demising wall, choosing board type for a wet area, placing control joints on a long run, or diagnosing why a finished assembly failed inspection or a sound/mold complaint.
日本語の概要は準備中です。原文の説明を表示しています。
Use when a task needs the judgment of an Engineering Teacher, Postsecondary — diagnosing a spike in a gatekeeper course's D/F/W rate, running a capstone design course with an industry sponsor, closing the loop on an ABET student-outcome assessment, or building a tenure/promotion teaching-effectiveness case beyond raw student evaluation scores.
日本語の概要は準備中です。原文の説明を表示しています。
Use when a task needs the judgment of a Registered Dietitian Nutritionist — calculating caloric/macronutrient needs for a clinical case, designing a medical-nutrition-therapy plan for a disease-specific condition (renal, diabetic, oncology), setting an enteral or parenteral feeding prescription, or screening/triaging malnutrition risk.
日本語の概要は準備中です。原文の説明を表示しています。
Use when a task needs the judgment of a Cost Estimator — building a conceptual (Class 5) budget from a napkin sketch, developing a hard-bid estimate from complete construction documents, leveling subcontractor bids before award, making a bid/no-bid call on an RFP, or reconciling a design-development estimate against an owner's target budget.
日本語の概要は準備中です。原文の説明を表示しています。
Use when a task needs the judgment of a Clinical Nurse Specialist — diagnosing why a unit-level outcome metric (CLABSI, falls, pressure injury) is off benchmark, designing and scaling a practice-change pilot, appraising whether a new clinical guideline actually fits the local population, writing a quarterly outcomes report to nursing leadership, or coaching staff nurses through a new protocol without formal authority over them. US hospital/health-system default; state nurse practice acts vary. A reasoning aid, not clinical or legal advice.
日本語の概要は準備中です。原文の説明を表示しています。