3,549 件 ・ 関連度順
概要と使いどころ
应用从 AI for Everyone 蒸馏出的「试点势能飞轮 — 先求成功再求价值」方法论。Use when the user needs practical guidance, diagnosis, workflow design, decision support, or an action plan related to pilot-momentum-flywheel.
日本語の概要は準備中です。原文の説明を表示しています。
应用从 AI for Everyone 蒸馏出的「AI转型五步指南 — 组织变革路线图」方法论。Use when the user needs practical guidance, diagnosis, workflow design, decision support, or an action plan related to ai-transformation-playbook.
日本語の概要は準備中です。原文の説明を表示しています。
应用从 AI for Everyone 蒸馏出的「分层AI培训 — 高管/经理/工程师的差异化学习」方法论。Use when the user needs practical guidance, diagnosis, workflow design, decision support, or an action plan related to role-tiered-training.
日本語の概要は準備中です。原文の説明を表示しています。
应用从 AI for Everyone 蒸馏出的「从小处着手+寻找伙伴 — AI入门的行动原则」方法论。Use when the user needs practical guidance, diagnosis, workflow design, decision support, or an action plan related to start-small-find-partner.
日本語の概要は準備中です。原文の説明を表示しています。
应用从 AI for Everyone 蒸馏出的「统计化验收标准 — 不追求100%准确」方法论。Use when the user needs practical guidance, diagnosis, workflow design, decision support, or an action plan related to statistical-acceptance.
日本語の概要は準備中です。原文の説明を表示しています。
应用从 AI for Everyone 蒸馏出的「AI价值驱动三途径 — 降本/增收/新业务」方法论。Use when the user needs practical guidance, diagnosis, workflow design, decision support, or an action plan related to three-value-drivers.
日本語の概要は準備中です。原文の説明を表示しています。
应用从 AI for Everyone 蒸馏出的「AI团队构建 — 打造高效AI团队的角色与协作」方法论。Use when the user needs practical guidance, diagnosis, workflow design, decision support, or an action plan related to ai-team-building.
日本語の概要は準備中です。原文の説明を表示しています。
应用从 AI for Everyone 蒸馏出的「AI战略护城河 — 用AI构建可持续竞争优势」方法论。Use when the user needs practical guidance, diagnosis, workflow design, decision support, or an action plan related to ai-strategy-moat.
日本語の概要は準備中です。原文の説明を表示しています。
应用从 AI for Everyone 蒸馏出的「训练集/测试集分离 — AI的'科学方法」方法论。Use when the user needs practical guidance, diagnosis, workflow design, decision support, or an action plan related to train-test-split.
日本語の概要は準備中です。原文の説明を表示しています。
应用从 AI for Everyone 蒸馏出的「AI流水线 — 多组件串联的系统设计模式」方法论。Use when the user needs practical guidance, diagnosis, workflow design, decision support, or an action plan related to ai-pipeline.
日本語の概要は準備中です。原文の説明を表示しています。
应用从 AI for Everyone 蒸馏出的「统一数据仓库 — AI的数据基础设施」方法论。Use when the user needs practical guidance, diagnosis, workflow design, decision support, or an action plan related to unified-data-warehouse.
日本語の概要は準備中です。原文の説明を表示しています。
Adopt govctl in an existing project. Discovers undocumented decisions, backfills ADRs/RFCs, annotates source code. Use when: (1) Project has no governance yet, (2) User mentions migrate, adopt, onboard, or brownfield
日本語の概要は準備中です。原文の説明を表示しています。
Elicit and challenge data-analysis requirements before querying. Use when the user asks ambiguous data questions, requests business/report answers, needs metric definitions clarified, or may be drawing decisions from incomplete data.
日本語の概要は準備中です。原文の説明を表示しています。
MUST USE when designing ClickHouse architectures, selecting between ingestion or modeling patterns, or translating best practices into workload-specific system designs. Complements clickhouse-best-practices with decision frameworks and explicit provenance labels.
日本語の概要は準備中です。原文の説明を表示しています。
Cut a versioned LoreWeave release — draft the CHANGELOG.md entry from what shipped since the last tag, confirm the SemVer bump and pre-release/release decision with the user, then tag and push to trigger the automated build + GitHub Release. Use when the user says "cut a release", "publish v...", "ship v0.1.0", "make a release", or asks what's changed since the last version.
日本語の概要は準備中です。原文の説明を表示しています。
Create or audit a complete, concise, UI-ready website page content framework from verified business facts before visual design. Use to define page goals, customer decision flow, section order, realistic draft copy, content and evidence needs, CTAs, or page-family rules; do not use for visual design, HTML, SEO implementation, or platform code.
日本語の概要は準備中です。原文の説明を表示しています。
Turn an electronic product idea, behavior description, reverse-engineering note, or incomplete circuit concept into a decision-ready engineering brief and architecture. Use before schematic design or audit when functions, operating states, power, interfaces, mechanics, production quantity, cost, or measurable requirements are missing or ambiguous.
日本語の概要は準備中です。原文の説明を表示しています。
Verify a PCBA BOM and proposed components before circuit or placement freeze, including exact manufacturer part numbers, pin semantics, packages, footprints, CAD and 3D models, lifecycle, live stock, MOQ, assembly class, price, and approved substitutes. Use for sourcing locks, unavailable or expensive parts, JLCPCB/LCSC matching, BOM risk, or cost-aware substitution decisions.
日本語の概要は準備中です。原文の説明を表示しています。
Use when organizing raw material into a coherent structure, defining the throughline of a piece, building an outline, or making strategic decisions about what to include and cut from generated content.
日本語の概要は準備中です。原文の説明を表示しています。
Interview the user relentlessly about a plan or design until reaching shared understanding, resolving each branch of the decision tree. Use when the user wants to stress-test a plan, get grilled on their design, or mentions "grill me". Run BEFORE /build when a feature idea is fuzzy and a PRD doesn't yet exist.
日本語の概要は準備中です。原文の説明を表示しています。
Interview the user relentlessly about a plan or design until reaching shared understanding, resolving each branch of the decision tree. Use when the user wants to stress-test a plan, get grilled on their design, or mentions "grill me". Run BEFORE /claude-setup:build when a feature idea is fuzzy and a PRD doesn't yet exist.
日本語の概要は準備中です。原文の説明を表示しています。
当用户纠结文案该写长还是写短时调用。适用于：规划广告/邮件/着陆页篇幅、 别人说"没人看长文案"时需要决策依据、产品复杂不知道该写多少。 核心信号：用户在问"文案写多长合适""会不会太长了"。 不适用于：已有明确篇幅要求、纯社交媒体短文案。
日本語の概要は準備中です。原文の説明を表示しています。
Run a premortem on any plan, launch, product, hire, strategy, or decision. Imagines it failed 6 months from now, works backward to find every reason why, then produces a revised plan. Triggers include "premortem this", "premortem my", "what could kill this", "stress test this plan", "find the blind spots", "poke holes in this", "where will this break", "am I missing anything", "what could go wrong", "future-proof this", "devil's advocate this".
日本語の概要は準備中です。原文の説明を表示しています。
Build explainability tools for AI decisions. TRIGGERS - Use when user needs help with ai-explainability-tool related tasks.
日本語の概要は準備中です。原文の説明を表示しています。