2,377 件 ・ 関連度順
概要と使いどころ
When the user wants to perform load testing or performance testing using Artillery with YAML-based scenario definitions. Also use when the user mentions "artillery," "YAML load test," "WebSocket testing," "Socket.io load test," "scenario-based load testing," or "artillery run." For JavaScript-based load testing, see k6.
日本語の概要は準備中です。原文の説明を表示しています。
Model Context Protocol expert for building MCP servers, tools, resources, and client integrationsUse when "mcp server, model context protocol, claude code extension, building ai tools, tool definition, mcp transport, stdio transport, sse transport, resource provider, prompt template, mcp, model-context-protocol, claude-code, ai-tools, llm-integration, anthropic, server, protocol" mentioned.
日本語の概要は準備中です。原文の説明を表示しています。
Use when designing disaster recovery strategies, defining RPO/RTO targets, implementing failover mechanisms, or conducting chaos engineering tests - covers active-active, pilot light, and backup strategiesUse when ", " mentioned.
日本語の概要は準備中です。原文の説明を表示しています。
Expert in CrewAI - the leading role-based multi-agent framework used by 60% of Fortune 500 companies. Covers agent design with roles and goals, task definition, crew orchestration, process types (sequential, hierarchical, parallel), memory systems, and flows for complex workflows. Essential for building collaborative AI agent teams. Use when "crewai, multi-agent team, agent roles, crew of agents, role-based agents, collaborative agents, crewai, multi-agent, agents, orchestration, roles, collaborative-ai" mentioned.
日本語の概要は準備中です。原文の説明を表示しています。
Use when implementing data governance frameworks, building data catalogs, establishing data lineage, defining data quality rules, or setting up data stewardship programs - covers metadata management, data quality, and complianceUse when ", " mentioned.
日本語の概要は準備中です。原文の説明を表示しています。
Expert in Claude Code hooks - user-defined shell commands that execute at specific points in Claude Code's lifecycle. Provides guaranteed automation that doesn't rely on the LLM "remembering" to do something. Essential for enterprise workflows, code quality enforcement, and deterministic behavior in agentic coding. Use when "claude code hooks, automate claude, block tool use, pre tool use, post tool use, session start hook, claude lifecycle, claude-code, automation, hooks, lifecycle, cli, workflow, devtools" mentioned.
日本語の概要は準備中です。原文の説明を表示しています。
Tools are how AI agents interact with the world. A well-designed tool is the difference between an agent that works and one that hallucinates, fails silently, or costs 10x more tokens than necessary. This skill covers tool design from schema to error handling. JSON Schema best practices, description writing that actually helps the LLM, validation, and the emerging MCP standard that's becoming the lingua franca for AI tools. Key insight: Tool descriptions are more important than tool implementations. The LLM never sees your code - it only sees the schema and description. Use when "agent tool, function calling, tool schema, tool design, mcp server, mcp tool, tool use, build tool for agent, define function, input_schema, tool_use, tool_result, agents, tools, function-calling, mcp, json-schema, anthropic, openai, llm-tools" mentioned.
日本語の概要は準備中です。原文の説明を表示しています。
Runs a multi-phase project from an orchestrating main thread that plans, routes and verifies but does not build. Defines a few long-lived workstreams, each owning a file area end to end in its own worktree, and routes every follow-up to the owning agent instead of spawning a one-off. Covers base-SHA recording, rebase-before-commit, stale-checkout detection, and shared-machine hygiene (ports, processes, measurement noise). Use when a project spans several phases or sessions with three or more agents working at once.
日本語の概要は準備中です。原文の説明を表示しています。
Build the deterministic evidence ledger (artifact_manifest.json + claims.json) that every other Anti-Autoresearch auditor reads. One pass inventories artifacts, derives the observability level (L0 PDF-only / L1 +LaTeX / L2 +repo+results) by fixed rule, and extracts span-anchored, hashed, checkable claims (numbers, comparisons, scope, method, baselines, citations, captions, table cells) into claims.json. An OPTIONAL additive cross-model pass ADDS span-anchored semantic claims — method, theorem statements with their assumptions, definitions, proof/derivation steps and equations, scope, baselines, conclusions, the motivation span, and reproducibility-artifact references (the proof, derivation, and structure anchors the family B/D/G auditors need) — it never invents a number, emits a finding, or computes a verdict. Run FIRST, before any audit skill. Triggers: "build the ledger", "extract claims", "prep for integrity audit", "evidence ledger", "建证据账本".
日本語の概要は準備中です。原文の説明を表示しています。
Apify Actorization workflow skill. Use this skill when the user needs Actorization converts existing software into reusable serverless applications compatible with the Apify platform. Actors are programs packaged as Docker images that accept well-defined JSON input, perform an action, and optionally produce structured JSON output and the operator should preserve the upstream workflow, copied support files, and provenance before merging or handing off.
日本語の概要は準備中です。原文の説明を表示しています。
Apify Actorization workflow skill. Use this skill when the user needs Actorization converts existing software into reusable serverless applications compatible with the Apify platform. Actors are programs packaged as Docker images that accept well-defined JSON input, perform an action, and optionally produce structured JSON output and the operator should preserve the upstream workflow, copied support files, and provenance before merging or handing off.
日本語の概要は準備中です。原文の説明を表示しています。
Azure AI Hosted Agents (Python) workflow skill. Use this skill when the user needs Build container-based Foundry Agents with Azure AI Projects SDK (ImageBasedHostedAgentDefinition). Use when creating hosted agents with custom container images in Azure AI Foundry and the operator should preserve the upstream workflow, copied support files, and provenance before merging or handing off.
日本語の概要は準備中です。原文の説明を表示しています。
🧠 Andru.ia Niche Intelligence (Dominio Experto) workflow skill. Use this skill when the user needs Estratega de Inteligencia de Dominio de Andru.ia. Analiza el nicho específico de un proyecto para inyectar conocimientos, regulaciones y estándares únicos del sector. Actívalo tras definir el nicho and the operator should preserve the upstream workflow, copied support files, and provenance before merging or handing off.
日本語の概要は準備中です。原文の説明を表示しています。
🧠 Andru.ia Niche Intelligence (Dominio Experto) workflow skill. Use this skill when the user needs Estratega de Inteligencia de Dominio de Andru.ia. Analiza el nicho específico de un proyecto para inyectar conocimientos, regulaciones y estándares únicos del sector. Actívalo tras definir el nicho and the operator should preserve the upstream workflow, copied support files, and provenance before merging or handing off.
日本語の概要は準備中です。原文の説明を表示しています。
Define or review SLOs and SLAs for a service. Use when a senior developer needs reliability targets.
日本語の概要は準備中です。原文の説明を表示しています。
Define engineering standards across teams. Use when a senior developer needs to align practices.
日本語の概要は準備中です。原文の説明を表示しています。
Define consistent API error codes and responses. Use when a mid-level developer needs error standardization.
日本語の概要は準備中です。原文の説明を表示しています。
Define performance budgets and guardrails. Use when a senior developer needs performance targets and enforcement.
日本語の概要は準備中です。原文の説明を表示しています。
产品设计 / UX 设计 (产品设计 / UX 设计 (Product Design / UX Design) — 数字产品的用户体验设计：从用户研究 → 信息架构 → 交互设计 → 视觉/UI → 可用性测试 → 设计系统的认知操作系统，面向 UX designer / product designer / interaction designer / UX researcher / design systems engineer / design lead，以及想入行、转岗、服务这行(设计外包、设计工具厂商、研究平台)的视角。覆盖: (a) 第一性张力 — **用户中心/研究驱动 (user-centered, 'you are not the user', research before pixels, observe behavior not opinions) ⇄ 商业目标/约束/交付 (business goals, north-star metrics, ship it, designer 服务于产品成功不是个人作品集)**; **设计直觉/品味/craft (taste, aesthetics, 'attractive things work better' — Norman 情感化设计) ⇄ 数据/实验/A-B 测试 (data-driven, metrics, experimentation, 'opinions are not data')**; **用户说的 (stated preference, 访谈里说喜欢) ⇄ 用户做的 (revealed behavior, 行为观察 > 自陈, usability test 看人真实卡在哪)**; **一致性/设计系统/规范 (consistency, design system, Jakob's law 用户带着别处的习惯来, 复用组件) ⇄ 创新/打破模式 (innovation, 该不该破规范)**; **减法/简化 (simplicity, Krug 'Don't Make Me Think', less but better — Dieter Rams) ⇄ 功能丰富/利益相关者塞需求 (feature creep, stakeholder pressure)**; **UX(体验/流程/研究) ⇄ UI(视觉/像素/组件)** 的职责之争, **designer 该不该写代码 (design engineer / 'should designers code')**; (b) 核心工作流 / pipeline (最标准、最易蒸高质量+CLI 化) — Double Diamond (发现 discover → 定义 define → 开发 develop → 交付 deliver) / Design Thinking (共情 empathize → 定义 → 构思 ideate → 原型 prototype → 测试 test) / Design Sprint (Jake Knapp 5 天冲刺); 完整链: 用户研究 (访谈/问卷/可用性测试/卡片分类) → persona / journey map / JTBD → 信息架构 IA + 用户流 user flow → 线框 wireframe (低保真) → 交互/原型 prototype (高保真) → 视觉 UI / 设计系统落地 → 可用性测试 usability testing → handoff 给开发 → 度量迭代 (北极星 / HEART 框架); (c) 工具栈 — 设计/原型 (Figma 绝对主导 / Sketch 衰退 / Adobe XD 已停更 / Framer 高保真+建站 / Penpot 开源 / Principle / ProtoPie 微交互); 协作白板 (FigJam / Miro / Mural); 用户研究 (Maze / UserTesting / Lookback / Dovetail 研究库 / Optimal Workshop 卡片分类树测试 / Hotjar / Microsoft Clarity 热图); 设计系统/交付 (Storybook / 蓝湖(中) / Zeplin / design tokens / Tokens Studio); 度量 (Amplitude / Mixpanel / 北极星指标); AI 新兴 (Figma AI / v0 by Vercel / Galileo AI / Uizard / Cursor 给 design engineer); (d) 知识正典 — Don Norman《The Design of Everyday Things》(affordance/signifier/mapping 圣经)、Steve Krug《Don't Make Me Think》(可用性入门)、Alan Cooper《About Face》《The Inmates Are Running the Asylum》(交互设计/persona 起源)、Jakob Nielsen 10 Usability Heuristics + NN/g 文章库、Jake Knapp《Sprint》、Jeff Gothelf《Lean UX》、Teresa Torres《Continuous Discovery Habits》、Erika Hall《Just Enough Research》、Julie Zhuo《The Making of a Manager》、《Refactoring UI》(Adam Wathan/Steve Schoger)、《Universal Principles of Design》、Laws of UX (Jon Yablonski)、《100 Things Every Designer Needs to Know About People》(Susan Weinschenk)、IDEO/Stanford d.school 设计思维材料; (e) figures/流派 — 认知心理/人因派 (Don Norman 认知科学奠基、Susan Weinschenk 行为心理、Kathryn Whitenton); 可用性工程派 (Jakob Nielsen 启发式/折扣可用性、Steve Krug、Jared Spool UIE); 交互设计/目标导向派 (Alan Cooper goal-directed/persona、Kim Goodwin); 设计思维派 (IDEO Tim Brown、David Kelley d.school); 精益/持续探索派 (Jeff Gothelf Lean UX、Teresa Torres continuous discovery、Marty Cagan《Inspired》产品发现); 设计系统/系统化派 (Brad Frost Atomic Design、Nathan Curtis design tokens、Alla Kholmatova); 视觉/UI craft 派 (Adam Wathan & Steve Schoger Refactoring UI、Dieter Rams 'less but better' 工业设计遗产); 设计领导/职业派 (Julie Zhuo、Aarron Walter 情感化设计、John Maeda); 移动优先 (Luke Wroblewski 'Mobile First'); (f) 行业话术/黑话 — affordance 可供性 / signifier 意符 / mental model 心智模型 / IA 信息架构 / heuristic evaluation 启发式评估 / usability 可用性 / a11y accessibility 无障碍 / WCAG / persona 用户画像 / journey map 用户旅程 / JTBD jobs-to-be-done / north-star metric 北极星 / HEART 框架 / wireframe 线框 / mockup / prototype 原型 / fidelity 保真度 (lo-fi/hi-fi) / design system 设计系统 / design token 设计令牌 / atomic design 原子设计 / component library 组件库 / handoff 交付 / red routes 关键路径 / dark pattern 暗黑模式 / Fitts's law / Hick's law / Jakob's law / Miller 7±2 / progressive disclosure 渐进披露 / above the fold / hamburger menu / skeuomorphism vs flat / micro-interaction / empty state / edge case / happy path / design debt 设计债 / dogfooding / dot voting / affinity mapping 亲和图 / card sorting 卡片分类 / tree testing / A/B test / NPS / SUS (System Usability Scale); (
日本語の概要は準備中です。原文の説明を表示しています。
Lightweight guidance for using the Upstash Workflow SDK to define, trigger, and manage workflows. Use this Skill whenever a user wants to create workflow endpoints, run steps, or interact with the Upstash Workflow client.
日本語の概要は準備中です。原文の説明を表示しています。
Generate navigable semantic maps from PDF documents. Extracts section structure via font analysis, then runs LLM extraction per section for claims, symbols, and dependencies — all page-anchored. Produces _MAP.md (progressive disclosure), .symbols.json (definition index), .anchors.json (claim references), and a _USAGE.md snippet for CLAUDE.md. Use when analyzing papers, specs, or legal docs; when asked to "map this document", "index this PDF", "what does this paper say"; or when a coding agent needs grounded reference material from a PDF source. Analogous to tree-sitting but for prose documents.
日本語の概要は準備中です。原文の説明を表示しています。
Use when defining visual novel characters for a @drincs/pixi-vn game — creating a character with a name, color, icon and other props, registering it so it can be looked up by id, and referencing it from dialogue/narration. Load this before writing any `CharacterBaseModel` or `RegisteredCharacters` code.
日本語の概要は準備中です。原文の説明を表示しています。
Use when writing or editing Pixi'VN story content — defining labels (scenes) with newLabel, writing dialogue steps, adding player choices with newChoiceOption/newCloseChoiceOption, conditional/branching labels, or wiring up narration.call/jump/continue and Game.start to progress the story.
日本語の概要は準備中です。原文の説明を表示しています。
Define version control strategies for design files, components, and libraries.
日本語の概要は準備中です。原文の説明を表示しています。