「ai」の検索結果

AI 短剧 (AI 微短剧) (AI 短剧 (AI 微短剧) (从业者视角) — 用 AIGC 工具（AI 视频生成 / AI 脚本 / AI 生图 / AI 配音 / 对口型 / 角色一致性）制作竖屏微短剧并变现的新兴行业。覆盖: (a) 创作工作流 — 选题→剧本/分镜→AI 生图→图生视频(首尾帧/运镜/参考)→配音/对口型→剪辑/调色→成片，其中角色/场景一致性是第一性难题; (b) 工具栈 — 视频生成(可灵 Kling / 即梦 Seedance / 海螺 Hailuo / Vidu / Runway Gen / OpenAI Sora / Pika / Luma / Pixverse)、脚本(LLM)、生图(Midjourney/SD/即梦)、配音(TTS)、对口型、剪辑(剪映/CapCut); (c) 商业/变现 — 国内付费投流(IAP + ROI + 平台分账, 抖音/快手/红果/微信小程序短剧)与海外订阅(ReelShort/DramaBox/ShortMax/GoodShort)两套打法、品牌定制、成本结构; (d) 合规 — 中国《人工智能生成合成内容标识办法》(2025-09 强制 AI 标识)、广电微短剧备案与分类分层审核、版权与肖像权。主战场 = 抖音/快手/视频号/B站 + 海外短剧 App。学派分歧: 纯 AI vs AI+实拍混合、国内投流 vs 海外订阅、视频工具派之争、「AI 短剧是真需求还是伪风口」。不含: 传统实拍短剧制作、通用影视编剧(已有 scriptwriting skill)、短视频信息流投放(已有 short-video-ads skill)、纯 AI 视频底层技术研发。) Master OS — automated mastery of AI 短剧 (AI 微短剧) (从业者视角) — 用 AIGC 工具（AI 视频生成 / AI 脚本 / AI 生图 / AI 配音 / 对口型 / 角色一致性）制作竖屏微短剧并变现的新兴行业。覆盖: (a) 创作工作流 — 选题→剧本/分镜→AI 生图→图生视频(首尾帧/运镜/参考)→配音/对口型→剪辑/调色→成片，其中角色/场景一致性是第一性难题; (b) 工具栈 — 视频生成(可灵 Kling / 即梦 Seedance / 海螺 Hailuo / Vidu / Runway Gen / OpenAI Sora / Pika / Luma / Pixverse)、脚本(LLM)、生图(Midjourney/SD/即梦)、配音(TTS)、对口型、剪辑(剪映/CapCut); (c) 商业/变现 — 国内付费投流(IAP + ROI + 平台分账, 抖音/快手/红果/微信小程序短剧)与海外订阅(ReelShort/DramaBox/ShortMax/GoodShort)两套打法、品牌定制、成本结构; (d) 合规 — 中国《人工智能生成合成内容标识办法》(2025-09 强制 AI 标识)、广电微短剧备案与分类分层审核、版权与肖像权。主战场 = 抖音/快手/视频号/B站 + 海外短剧 App。学派分歧: 纯 AI vs AI+实拍混合、国内投流 vs 海外订阅、视频工具派之争、「AI 短剧是真需求还是伪风口」。不含: 传统实拍短剧制作、通用影视编剧(已有 scriptwriting skill)、短视频信息流投放(已有 short-video-ads skill)、纯 AI 视频底层技术研发。: top builders' mental models, tool stack, current workflows, jargon, and where to keep up. Trigger this skill when the user works on AI 短剧 (AI 微短剧) (从业者视角) — 用 AIGC 工具（AI 视频生成 / AI 脚本 / AI 生图 / AI 配音 / 对口型 / 角色一致性）制作竖屏微短剧并变现的新兴行业。覆盖: (a) 创作工作流 — 选题→剧本/分镜→AI 生图→图生视频(首尾帧/运镜/参考)→配音/对口型→剪辑/调色→成片，其中角色/场景一致性是第一性难题; (b) 工具栈 — 视频生成(可灵 Kling / 即梦 Seedance / 海螺 Hailuo / Vidu / Runway Gen / OpenAI Sora / Pika / Luma / Pixverse)、脚本(LLM)、生图(Midjourney/SD/即梦)、配音(TTS)、对口型、剪辑(剪映/CapCut); (c) 商业/变现 — 国内付费投流(IAP + ROI + 平台分账, 抖音/快手/红果/微信小程序短剧)与海外订阅(ReelShort/DramaBox/ShortMax/GoodShort)两套打法、品牌定制、成本结构; (d) 合规 — 中国《人工智能生成合成内容标识办法》(2025-09 强制 AI 标识)、广电微短剧备案与分类分层审核、版权与肖像权。主战场 = 抖音/快手/视频号/B站 + 海外短剧 App。学派分歧: 纯 AI vs AI+实拍混合、国内投流 vs 海外订阅、视频工具派之争、「AI 短剧是真需求还是伪风口」。不含: 传统实拍短剧制作、通用影视编剧(已有 scriptwriting skill)、短视频信息流投放(已有 short-video-ads skill)、纯 AI 视频底层技术研发。 problems and wants industry-grade thinking, tool selection, or workflow guidance. 触发词：「ai 短剧」「ai 微短剧」「ai short drama」「ai 短剧制作」「ai 短剧工作流」

日本語の概要は準備中です。原文の説明を表示しています。

小红书 AI 自媒体博主 (小红书 AI 自媒体博主 (从业者视角) — 在小红书做『AI 赛道』内容的自媒体博主，重点是**怎么写文案、怎么制作内容**。覆盖: (a) AI 赛道选题 — AI 工具测评 / AI 绘画 / AI 教程与 prompt / AI 副业变现 / AI 资讯解读 / AI 效率，按小红书用户(偏年轻女性 + 泛知识)重构选题; (b) 文案与内容结构(核心) — 封面(第一眼/大字报/对比图)、标题(数字/痛点/好奇缺口/关键词前置)、正文(钩子开头/分点/口语化/emoji/利他价值)、标签与 SEO 关键词、CTA 与互动引导、人设 voice; (c) 内容制作工作流 — 选题(对标爆款/找选题)→标题封面→脚本或正文→制作(图文/口播/录屏/数字人)→标签发布→数据复盘迭代; (d) AI 工具用于内容生产 — 文案(豆包/Kimi/DeepSeek/GPT)、生图(即梦/MJ/可图)、口播数字人、剪辑(剪映)、封面(Canva/创可贴)、选题与 SEO(新红/千瓜/灰豚); (e) 平台机制与起号 — 推荐算法(收藏率/互动率/完播/搜索)、薯条投放、违禁词/限流/避坑、起号与涨粉、垂直度; (f) 变现(次要) — 蒲公英广告 / 知识付费 / 引流私域 / AI 工具带货。学派分歧: 图文 vs 短视频、干货教程 vs 测评种草 vs 资讯搬运、真人出镜 vs 数字人/无人起号、原创 vs 搬运洗稿、AI 全自动批量 vs AI 辅助精做。不含: 通用小红书运营(已有 xiaohongshu-ops skill, 本 skill 聚焦 AI 赛道 + 文案/内容生产)、电商带货全流程、其他平台、AI 工具本身的技术原理。) Master OS — automated mastery of 小红书 AI 自媒体博主 (从业者视角) — 在小红书做『AI 赛道』内容的自媒体博主，重点是**怎么写文案、怎么制作内容**。覆盖: (a) AI 赛道选题 — AI 工具测评 / AI 绘画 / AI 教程与 prompt / AI 副业变现 / AI 资讯解读 / AI 效率，按小红书用户(偏年轻女性 + 泛知识)重构选题; (b) 文案与内容结构(核心) — 封面(第一眼/大字报/对比图)、标题(数字/痛点/好奇缺口/关键词前置)、正文(钩子开头/分点/口语化/emoji/利他价值)、标签与 SEO 关键词、CTA 与互动引导、人设 voice; (c) 内容制作工作流 — 选题(对标爆款/找选题)→标题封面→脚本或正文→制作(图文/口播/录屏/数字人)→标签发布→数据复盘迭代; (d) AI 工具用于内容生产 — 文案(豆包/Kimi/DeepSeek/GPT)、生图(即梦/MJ/可图)、口播数字人、剪辑(剪映)、封面(Canva/创可贴)、选题与 SEO(新红/千瓜/灰豚); (e) 平台机制与起号 — 推荐算法(收藏率/互动率/完播/搜索)、薯条投放、违禁词/限流/避坑、起号与涨粉、垂直度; (f) 变现(次要) — 蒲公英广告 / 知识付费 / 引流私域 / AI 工具带货。学派分歧: 图文 vs 短视频、干货教程 vs 测评种草 vs 资讯搬运、真人出镜 vs 数字人/无人起号、原创 vs 搬运洗稿、AI 全自动批量 vs AI 辅助精做。不含: 通用小红书运营(已有 xiaohongshu-ops skill, 本 skill 聚焦 AI 赛道 + 文案/内容生产)、电商带货全流程、其他平台、AI 工具本身的技术原理。: top builders' mental models, tool stack, current workflows, jargon, and where to keep up. Trigger this skill when the user works on 小红书 AI 自媒体博主 (从业者视角) — 在小红书做『AI 赛道』内容的自媒体博主，重点是**怎么写文案、怎么制作内容**。覆盖: (a) AI 赛道选题 — AI 工具测评 / AI 绘画 / AI 教程与 prompt / AI 副业变现 / AI 资讯解读 / AI 效率，按小红书用户(偏年轻女性 + 泛知识)重构选题; (b) 文案与内容结构(核心) — 封面(第一眼/大字报/对比图)、标题(数字/痛点/好奇缺口/关键词前置)、正文(钩子开头/分点/口语化/emoji/利他价值)、标签与 SEO 关键词、CTA 与互动引导、人设 voice; (c) 内容制作工作流 — 选题(对标爆款/找选题)→标题封面→脚本或正文→制作(图文/口播/录屏/数字人)→标签发布→数据复盘迭代; (d) AI 工具用于内容生产 — 文案(豆包/Kimi/DeepSeek/GPT)、生图(即梦/MJ/可图)、口播数字人、剪辑(剪映)、封面(Canva/创可贴)、选题与 SEO(新红/千瓜/灰豚); (e) 平台机制与起号 — 推荐算法(收藏率/互动率/完播/搜索)、薯条投放、违禁词/限流/避坑、起号与涨粉、垂直度; (f) 变现(次要) — 蒲公英广告 / 知识付费 / 引流私域 / AI 工具带货。学派分歧: 图文 vs 短视频、干货教程 vs 测评种草 vs 资讯搬运、真人出镜 vs 数字人/无人起号、原创 vs 搬运洗稿、AI 全自动批量 vs AI 辅助精做。不含: 通用小红书运营(已有 xiaohongshu-ops skill, 本 skill 聚焦 AI 赛道 + 文案/内容生产)、电商带货全流程、其他平台、AI 工具本身的技术原理。 problems and wants industry-grade thinking, tool selection, or workflow guidance. 触发词：「小红书 ai 博主」「小红书 ai 自媒体」「小红书 ai 赛道」「小红书爆款文案」「小红书 ai 教程」

日本語の概要は準備中です。原文の説明を表示しています。

This skill should be used when the user asks how to "use VibeTags", "add VibeTags annotations", "set up AI guardrails", "protect code from AI", "configure AI platforms", asks about @AILocked, @AIContext, @AIDraft, @AIAudit, @AIIgnore, @AIPrivacy, @AICore, @AIPerformance, @AIContract, @AITestDriven, @AIThreadSafe, @AIImmutable, @AIDeprecated, @AIObservability, @AIRegulation, @AIArchitecture, @AILegacyBridge, @AIStrictClasspath, @AIInternationalized, @AIPublicAPI, @AISchemaSafe, @AIStrictExceptions, @AIStrictTypes, @AIParallelTests, @AIIdempotent, @AIFeatureFlag, @AISecure, @AICallersOnly, @AISandboxOnly, @AIMemoryBudget, @AIPure, @AIDomainModel, @AIExtensible, @AIInputSanitized, @AISecureLogging, @AIExplain, @AIPrototype, @AISunset, @AITemporary annotations, or wants to control how AI tools interact with Java code.

日本語の概要は準備中です。原文の説明を表示しています。

知乎 AI 自媒体博主 (知乎 AI 自媒体博主 (从业者视角) — 在知乎做『AI 赛道』内容的自媒体博主，重点是**怎么写文案、怎么制作内容**。覆盖: (a) AI 赛道选题 — AI 工具实测 / 大模型解读 / prompt 工程 / AI 副业与变现 / AI 编程 / AI 行业分析 / AI 资讯解读，按知乎用户(偏高学历、理性、求深度、爱较真)重构选题; (b) 文案与内容结构(核心) — 知乎体回答/文章(开头钩子『先说结论/抛反常识/讲故事』、逻辑论证、数据与案例、分点小标题、配图与代码块、结尾升华或金句)、标题(问题型/数字型/反差型/痛点型)、专业感与『讲人话』的平衡、人设 voice、引用与举证(知乎读者吃『有理有据』); (c) 内容制作工作流 — 找问题/选题(热榜/搜索流量词/对标高赞)→搭框架(论点+论据+案例)→写初稿→配图配数据→排版→发布→盐选/付费咨询/带货沉淀; (d) AI 工具用于内容生产 — 找选题与资料(GPT/Claude/Kimi/秘塔)、写作辅助与改写、配图(即梦/MJ)、代码与图表、英文一手编译; (e) 平台机制与涨粉 — 知乎推荐算法(赞同/收藏/想法/盐值/专业徽章/搜索长尾)、热榜与问题流量、好物推荐/知乎带货、盐选专栏、创作者激励、垂直度与权重、避坑(折叠/限流/广告判定); (f) 变现(次要) — 盐选专栏 / 好物推荐带货 / 付费咨询 / 知乎知学堂引流 / 私域 / 商业合作。学派分歧: 长答案深度干货 vs 短平快蹭热榜、专业严肃 vs 故事化通俗、原创 vs 编译搬运洗稿、真人专业人设 vs AI 批量生产、回答优先 vs 文章优先、纯涨粉 vs 直奔盐选变现。不含: 通用知乎运营、电商带货全流程、其他平台(小红书/推特另有 sister skill)、AI 工具本身技术原理。) Master OS — automated mastery of 知乎 AI 自媒体博主 (从业者视角) — 在知乎做『AI 赛道』内容的自媒体博主，重点是**怎么写文案、怎么制作内容**。覆盖: (a) AI 赛道选题 — AI 工具实测 / 大模型解读 / prompt 工程 / AI 副业与变现 / AI 编程 / AI 行业分析 / AI 资讯解读，按知乎用户(偏高学历、理性、求深度、爱较真)重构选题; (b) 文案与内容结构(核心) — 知乎体回答/文章(开头钩子『先说结论/抛反常识/讲故事』、逻辑论证、数据与案例、分点小标题、配图与代码块、结尾升华或金句)、标题(问题型/数字型/反差型/痛点型)、专业感与『讲人话』的平衡、人设 voice、引用与举证(知乎读者吃『有理有据』); (c) 内容制作工作流 — 找问题/选题(热榜/搜索流量词/对标高赞)→搭框架(论点+论据+案例)→写初稿→配图配数据→排版→发布→盐选/付费咨询/带货沉淀; (d) AI 工具用于内容生产 — 找选题与资料(GPT/Claude/Kimi/秘塔)、写作辅助与改写、配图(即梦/MJ)、代码与图表、英文一手编译; (e) 平台机制与涨粉 — 知乎推荐算法(赞同/收藏/想法/盐值/专业徽章/搜索长尾)、热榜与问题流量、好物推荐/知乎带货、盐选专栏、创作者激励、垂直度与权重、避坑(折叠/限流/广告判定); (f) 变现(次要) — 盐选专栏 / 好物推荐带货 / 付费咨询 / 知乎知学堂引流 / 私域 / 商业合作。学派分歧: 长答案深度干货 vs 短平快蹭热榜、专业严肃 vs 故事化通俗、原创 vs 编译搬运洗稿、真人专业人设 vs AI 批量生产、回答优先 vs 文章优先、纯涨粉 vs 直奔盐选变现。不含: 通用知乎运营、电商带货全流程、其他平台(小红书/推特另有 sister skill)、AI 工具本身技术原理。: top builders' mental models, tool stack, current workflows, jargon, and where to keep up. Trigger this skill when the user works on 知乎 AI 自媒体博主 (从业者视角) — 在知乎做『AI 赛道』内容的自媒体博主，重点是**怎么写文案、怎么制作内容**。覆盖: (a) AI 赛道选题 — AI 工具实测 / 大模型解读 / prompt 工程 / AI 副业与变现 / AI 编程 / AI 行业分析 / AI 资讯解读，按知乎用户(偏高学历、理性、求深度、爱较真)重构选题; (b) 文案与内容结构(核心) — 知乎体回答/文章(开头钩子『先说结论/抛反常识/讲故事』、逻辑论证、数据与案例、分点小标题、配图与代码块、结尾升华或金句)、标题(问题型/数字型/反差型/痛点型)、专业感与『讲人话』的平衡、人设 voice、引用与举证(知乎读者吃『有理有据』); (c) 内容制作工作流 — 找问题/选题(热榜/搜索流量词/对标高赞)→搭框架(论点+论据+案例)→写初稿→配图配数据→排版→发布→盐选/付费咨询/带货沉淀; (d) AI 工具用于内容生产 — 找选题与资料(GPT/Claude/Kimi/秘塔)、写作辅助与改写、配图(即梦/MJ)、代码与图表、英文一手编译; (e) 平台机制与涨粉 — 知乎推荐算法(赞同/收藏/想法/盐值/专业徽章/搜索长尾)、热榜与问题流量、好物推荐/知乎带货、盐选专栏、创作者激励、垂直度与权重、避坑(折叠/限流/广告判定); (f) 变现(次要) — 盐选专栏 / 好物推荐带货 / 付费咨询 / 知乎知学堂引流 / 私域 / 商业合作。学派分歧: 长答案深度干货 vs 短平快蹭热榜、专业严肃 vs 故事化通俗、原创 vs 编译搬运洗稿、真人专业人设 vs AI 批量生产、回答优先 vs 文章优先、纯涨粉 vs 直奔盐选变现。不含: 通用知乎运营、电商带货全流程、其他平台(小红书/推特另有 sister skill)、AI 工具本身技术原理。 problems and wants industry-grade thinking, tool selection, or workflow guidance. 触发词：「知乎 ai 博主」「知乎 ai 自媒体」「知乎 ai 赛道」「知乎高赞回答」「知乎 ai 文章」

日本語の概要は準備中です。原文の説明を表示しています。

推特中文圈 AI 自媒体博主 (推特(X) 中文圈 AI 自媒体博主 (从业者视角) — 在 X/推特 用中文做 AI 内容的自媒体博主，重点是**怎么写推文/thread、怎么制作内容**。覆盖: (a) 选题 — AI 模型发布解读 / prompt 技巧 / AI 工具实测 / AI 出海与独立开发(build in public) / 英文一手编译翻译 / 信息差 / AI 资讯快讯 / 深度长推; (b) 文案与内容结构(核心) — 单条推(开头钩子/信息密度/短句断行/配图截图/数据图)、长推与 thread(首条钩子/编号/逻辑链/结尾关注 CTA)、引用锐评(quote tweet)、排版可读性、配图(ray.so/carbon 代码图/产品截图/对比图); (c) 内容制作工作流 — 找信息源(英文一手/arXiv/官方/Reddit/HN)→选题→编译总结加洞察→写推/thread→配图→发布→互动维护; (d) AI 工具用于内容生产 — 英文一手编译总结(GPT/Claude/Kimi)、配图(ray.so/carbon/截图美化)、thread 工具(Typefully/Hypefury)、翻译、排程分析; (e) 平台机制与涨粉 — X 算法时间线(转评赞/互动权重/外链降权)、蹭热点借势、互动与回复、build in public 涨粉、英文区搬运到中文区的信息差红利; (f) 变现(次要) — 广告 / 知识星球 / 社群 / 付费课程 / 咨询 / 导流。学派分歧: 编译搬运(英文一手翻译) vs 原创洞察、快讯资讯 vs 深度长推、锐评玩梗 vs 严肃干货、build in public vs 纯内容、全 AI 自动发 vs 人工精选。代表生态(宝玉/歸藏/向阳乔木/AI 进化论/小互/Gorden Sun 等)。不含: 英文 AI Twitter 圈(聚焦中文圈)、通用 X 增长营销、其他平台、AI 工具技术原理。) Master OS — automated mastery of 推特(X) 中文圈 AI 自媒体博主 (从业者视角) — 在 X/推特 用中文做 AI 内容的自媒体博主，重点是**怎么写推文/thread、怎么制作内容**。覆盖: (a) 选题 — AI 模型发布解读 / prompt 技巧 / AI 工具实测 / AI 出海与独立开发(build in public) / 英文一手编译翻译 / 信息差 / AI 资讯快讯 / 深度长推; (b) 文案与内容结构(核心) — 单条推(开头钩子/信息密度/短句断行/配图截图/数据图)、长推与 thread(首条钩子/编号/逻辑链/结尾关注 CTA)、引用锐评(quote tweet)、排版可读性、配图(ray.so/carbon 代码图/产品截图/对比图); (c) 内容制作工作流 — 找信息源(英文一手/arXiv/官方/Reddit/HN)→选题→编译总结加洞察→写推/thread→配图→发布→互动维护; (d) AI 工具用于内容生产 — 英文一手编译总结(GPT/Claude/Kimi)、配图(ray.so/carbon/截图美化)、thread 工具(Typefully/Hypefury)、翻译、排程分析; (e) 平台机制与涨粉 — X 算法时间线(转评赞/互动权重/外链降权)、蹭热点借势、互动与回复、build in public 涨粉、英文区搬运到中文区的信息差红利; (f) 变现(次要) — 广告 / 知识星球 / 社群 / 付费课程 / 咨询 / 导流。学派分歧: 编译搬运(英文一手翻译) vs 原创洞察、快讯资讯 vs 深度长推、锐评玩梗 vs 严肃干货、build in public vs 纯内容、全 AI 自动发 vs 人工精选。代表生态(宝玉/歸藏/向阳乔木/AI 进化论/小互/Gorden Sun 等)。不含: 英文 AI Twitter 圈(聚焦中文圈)、通用 X 增长营销、其他平台、AI 工具技术原理。: top builders' mental models, tool stack, current workflows, jargon, and where to keep up. Trigger this skill when the user works on 推特(X) 中文圈 AI 自媒体博主 (从业者视角) — 在 X/推特 用中文做 AI 内容的自媒体博主，重点是**怎么写推文/thread、怎么制作内容**。覆盖: (a) 选题 — AI 模型发布解读 / prompt 技巧 / AI 工具实测 / AI 出海与独立开发(build in public) / 英文一手编译翻译 / 信息差 / AI 资讯快讯 / 深度长推; (b) 文案与内容结构(核心) — 单条推(开头钩子/信息密度/短句断行/配图截图/数据图)、长推与 thread(首条钩子/编号/逻辑链/结尾关注 CTA)、引用锐评(quote tweet)、排版可读性、配图(ray.so/carbon 代码图/产品截图/对比图); (c) 内容制作工作流 — 找信息源(英文一手/arXiv/官方/Reddit/HN)→选题→编译总结加洞察→写推/thread→配图→发布→互动维护; (d) AI 工具用于内容生产 — 英文一手编译总结(GPT/Claude/Kimi)、配图(ray.so/carbon/截图美化)、thread 工具(Typefully/Hypefury)、翻译、排程分析; (e) 平台机制与涨粉 — X 算法时间线(转评赞/互动权重/外链降权)、蹭热点借势、互动与回复、build in public 涨粉、英文区搬运到中文区的信息差红利; (f) 变现(次要) — 广告 / 知识星球 / 社群 / 付费课程 / 咨询 / 导流。学派分歧: 编译搬运(英文一手翻译) vs 原创洞察、快讯资讯 vs 深度长推、锐评玩梗 vs 严肃干货、build in public vs 纯内容、全 AI 自动发 vs 人工精选。代表生态(宝玉/歸藏/向阳乔木/AI 进化论/小互/Gorden Sun 等)。不含: 英文 AI Twitter 圈(聚焦中文圈)、通用 X 增长营销、其他平台、AI 工具技术原理。 problems and wants industry-grade thinking, tool selection, or workflow guidance. 触发词：「推特 ai 博主」「推特中文 ai」「x ai 自媒体」「推特 thread」「推特爆款推文」

日本語の概要は準備中です。原文の説明を表示しています。

AIGC 创作工作流 (AIGC 创作工作流 / AIGC Creative Workflow — 以「生成式 AI 视觉创作（图像 + 视频）的工程化创作流水线」为对象的认知操作系统：从「需求/概念（要做什么画面/镜头/风格）→ 模型与工具选型（Midjourney / Stable Diffusion·SDXL·Flux / ComfyUI / 可灵 Kling / 即梦 Jimeng / Runway / Vidu / Sora）→ Prompt 与参数设计（提示词工程、风格描述、负向、种子、CFG/步数/采样器、参考图）→ 可控生成（ControlNet / LoRA / IPAdapter / inpainting / 图生图 / 局部重绘 / 区域控制）→ 批量出图与筛选 → 精修与合成（放大/超分、修手修脸、PS/AE 后期、抠图合成）→ 图生视频/文生视频（首尾帧、运镜、时长、一致性、对口型）→ 商业交付与迭代复现（参数留存、工作流文件复用、版权与可商用判断）」的完整创作-工程-交付决策链。覆盖 (a) 第一性张力 — **可控性/工程化复现（ControlNet/LoRA/ComfyUI 节点工作流/固定种子与参数/可复现可迭代）⇄ 随机性/抽卡玄学（出图随机、prompt 玄学、抽卡刷图、靠运气）**；**审美/创意/艺术指导主导（人的审美判断、概念设计、构图、镜头语言、艺术总监能力——'模型是地板，审美是天花板'）⇄ 工具/模型/参数主导（堆模型能力、堆参数、堆 LoRA、以为换个大模型就行）**；**开源生态/本地可控（Stable Diffusion / ComfyUI / Flux / civitai / liblib 本地部署可定制可控可商用、显卡门槛）⇄ 闭源商业/易用黑盒（Midjourney / 可灵 / 即梦 / Runway 开箱即用但不可精控、按量付费、黑盒）**；**图像生成（T2I/I2I：Midjourney / SDXL / Flux）⇄ 视频生成（T2V/I2V：可灵 / Runway Gen-3 / Vidu / 即梦 / Sora，2024-2025 前沿从图迁移到视频）**；**生产力/商业量产（替代或增强传统设计/插画/电商/广告/影视分镜流程、降本提效、批量）⇄ 纯艺术创作/作者表达（个人风格、实验性、作品集）**；**效率/批量（一次出几十张筛选、商单走量、自动化 pipeline）⇄ 质量/精控（单张精修、商业可用级细节、修手修脸修穿帮）**。(b) 核心工作流 / pipeline（最标准、最易蒸高质量 + CLI 化）— 单图创作链：概念/参考收集（moodboard/风格定位/竞品）→ 模型工具选型（按可控性/风格/成本/可商用判断 MJ vs SD/Flux vs 国产）→ Prompt 与参数设计（主体/风格/光影/镜头/负向词/CFG/采样器/分辨率/种子）→ 首轮出图与方向筛选 → 可控迭代（ControlNet 控构图/姿态/线稿、LoRA 控风格/角色一致性、图生图重绘、inpainting 局部修）→ 放大超分与精修（高清放大/修手修脸/后期调色合成）→ 交付与参数留存（工作流文件/种子/参数复现）。视频创作链：分镜/脚本→首帧出图（图像链产出关键帧）→图生视频（运镜/时长/首尾帧/动态强度）→多镜头一致性（角色/场景/风格统一）→对口型/配音/配乐→剪辑合成→交付。ComfyUI 工程链：节点工作流搭建（加载器/采样/ControlNet/放大/面部修复节点）→ 参数化与复用→批量队列→工作流分享（civitai/openart workflow json）。(c) 工具栈 — 闭源图像（Midjourney v6/v7、DALL·E 3、Adobe Firefly、Ideogram、Recraft）、开源图像与底座（Stable Diffusion 1.5/SDXL/SD3、Flux.1 dev/schnell（Black Forest Labs）、ComfyUI（节点式）、Automatic1111/Forge WebUI、Fooocus）、可控生成插件（ControlNet、LoRA、IPAdapter、AnimateDiff、inpainting/outpainting、ReActor 换脸、面部修复 CodeFormer/GFPGAN、放大 ESRGAN/SUPIR/Topaz）、模型/资源社区（Hugging Face、Civitai、liblib 哩布、吐司 Tusi、openart）、视频生成（可灵 Kling、即梦 Dreamina/Jimeng、Runway Gen-3/Gen-4、Luma Dream Machine、Pika、Vidu、海螺 Hailuo、Sora、Wan 通义万相、MiniMax）、辅助（Magnific 放大、Krea、Photoshop/After Effects 后期、ChatGPT/Claude 写 prompt、reverse prompt 反推）。(d) 知识正典 — AIGC 创作 canon 横跨论文/工程/社区教程：奠基论文（DDPM、Latent Diffusion/Stable Diffusion（Rombach et al）、DiT、ControlNet（Zhang et al）、LoRA、DreamBooth、Textual Inversion、SDEdit、IP-Adapter、视频扩散 SVD/Sora 技术报告）、官方文档与模型卡（Stability AI、Black Forest Labs Flux、ComfyUI 文档、Midjourney docs、可灵/即梦官方教程、Hugging Face diffusers）、社区教程与工作流（ComfyUI 官方示例、civitai 文章、B站/YouTube 创作者长教程、openart workflow）、prompt 工程资源（Midjourney 风格库、提示词指南）。(e) figures/流派 — 模型/工具创造者（Midjourney David Holz、Stability AI Emad/Robin Rombach、Black Forest Labs（Flux，原 SD 团队）、ComfyUI comfyanonymous、ControlNet 张吕敏 Lvmin Zhang、AUTOMATIC1111、可灵/即梦/快手字节团队）、创作者 KOL 与教育者（Midjourney/SD 头部创作者、ComfyUI 工作流大神、AI 视频创作者、国内 B站/抖音 AIGC 教程作者、独立 AI 艺术家）、行业分析与评测（AI 工具评测、生成式 AI 创作生态观察者）。流派分歧：开源可控派（SD/ComfyUI/Flux 本地精控）vs 闭源易用派（MJ/可灵开箱即用）、工程化派（节点工作流/可复现/参数化）vs 玄学抽卡派（prompt 玄学/堆词/抽卡）、审美主导派（'模型是地板审美是天花板'）vs 工具主导派（堆模型堆参数）、图像派 vs 视频派、艺术创作派 vs 商业生产力派、国产工具派（可灵/即梦/liblib）vs 海外工具派（MJ/Flux/Runway）。(f) 行业话术/黑话 — 出图 / 抽卡 / 刷图 / 炼丹（训练 LoRA）/ 喂图 / 垫图（参考图/图生图）/ 控图 / 锁种子 seed / CFG / 采样器 sampler / 步数 steps / 重绘幅度 denoise / 提示词 prompt / 咒语 / 负向 negative / 权重 / tag / 大模型 checkpoint / 底模 / LoRA / ControlNet / 控线稿/openpose/depth / IPAdapter / inpainting 局部重绘 / outpainting 扩图 / 高清放大 / 超分 / 修手 / 崩手 / AI 味 / 风格 / 角色一致性 / 工作流 workflow / 节点 / 跑图 / 队列 / 文生图 T2I / 图生图 I2I / 文生视频 T2V / 图生视频 I2V / 首帧/尾帧 / 运镜 / 动态强度 / 时长 / 对口型 / 一致性 / 可商用 / 训练集 / 过拟合 / 翻车 / 穿帮。(g) 争议/批判 — 「版权与训练数据」（模型训练用未授权作品、生成图版权归属、可商用风险、洗图/伪原创）、「AI 替代创作者就业」（替代画师/插画师/设计师/摄影、行业冲击与转型）、「AI 味与审美趋同」（生成图同质化、套模板、缺乏原创审美）、「玄学 prompt 神话与割韭菜」（'咒语'神秘化、'7天 AIGC 变现/月入过万'付费课割韭菜、抽卡当能力）、「工具快速迭代与淘汰焦虑」（模型月月换、工作流频繁失效、追新疲劳）、「开源 vs 闭源之争」（可控可商用 vs 易用黑盒）、「质量天花板」（修手修脸穿帮、长视频一致性、可控性仍有限）。(h) 大量隐性创作手艺 + 审美 + 工程 + 沟通软技能（prompt 的描述功底与审美词汇、参数与采样的手感、ControlNet/LoRA 的组合控制经验、节点工作流的搭建与调试、批量筛选的审美眼力、修图合成的后期功底、镜头语言与运镜设计、角色/风格一致性的控制、商业需求的翻译与交付、版权与可商用的判断）是高 tacit、靠大量实操跑图 + 审美积累 + 工程调试经验的核心。水分极高（大量'咒语速成/一键变现/AI 绘画割韭菜'营销

日本語の概要は準備中です。原文の説明を表示しています。

Free domain research and availability checking. No API keys or credentials required. Uses RDAP (1195+ TLDs) with whois CLI fallback for universal coverage. Checks if domains are available, searches keywords across TLDs, performs WHOIS/RDAP lookups, checks expiry dates, and finds nameservers. Use when the agent needs to: check if a domain is available, search for domains, find who owns a domain, check domain expiration, get nameservers, bulk check domains, or do any domain research. Triggers on: 'check domain', 'is domain available', 'search domains', 'domain availability', 'who owns this domain', 'whois', 'domain expiry', 'when does domain expire', 'nameservers for', 'domain research', 'find domains for', 'domain ideas', 'bulk domain check'.

日本語の概要は準備中です。原文の説明を表示しています。

YouTube channel business email and contact extractor: accepts a channel id (UCxxx), handle (@name), or URL; navigates the channel About view; extracts the business email from the description text plus full channel metadata (name, id, country, subscriber count, view count, video count, joined date, external links classified as social/aggregator/personal). When the description has no email, follows non-social outbound links (personal site, business site, link aggregator) and scans those pages for an email so creators who place their inquiry email on their own site are still covered. Use when user mentions youtube channel email, youtube business email, youtube creator email, youtube contact email, youtube channel contact, youtube channel scraper email, youtube email finder, youtube influencer email, youtube outreach, youtube sponsorship contact, youtube partnership email, scrape email from youtube, get email from youtube channel, find youtube creator contact, extract youtube channel emails in bulk, youtube channel inquiry email, business inquiries youtube, brand deal email youtube, lead generation youtube creators, youtube creator outreach list, youtube channel about email, ytInitialData about, youtube channel id to email, youtube handle to email, youtube channel url to email, youtube about page scraper, channel about page email, youtube channel metadata, youtube channel social links, youtube channel external links, youtube channel description email, follow channel website for email, scrape creator personal website from youtube. Also applies to building creator/KOL contact databases for influencer marketing, agency lead lists, sponsorship prospecting, brand-creator collaboration sourcing, and enriching existing YouTube channel lists with contact info.

日本語の概要は準備中です。原文の説明を表示しています。

Sales enablement, technical presales and deal acceleration for B2B SaaS revenue teams. Use this skill when planning outbound campaigns, running discovery calls, building deal strategy, creating battle cards, writing proposals, responding to RFPs, preparing a product demo, scoping a proof of concept or pilot, answering a security questionnaire or the AI annex buyers now attach to it, executing sales sequences, coaching qualification, or deciding what the website's AI chat agent is allowed to say. Also triggers on: outbound, cold outreach, reply handling, reply classification, out-of-office replies, auto-replies counted as replies, our reply rate is inflated, prospect replied remove me, opt-out by reply, is this list ready to send, launch readiness, CRM segment outbound, we emailed a current customer, outbound hit an open opportunity, ownerless leads, prospects engaging our competitors, competitor connections, displacement list, is this personalization creepy, can we mention they visited our site, signal freshness, deal strategy, pipeline, battle card, objection handling, common objections, why do we keep hearing this objection, mine call transcripts for objections, objection register, proposal, RFP, discovery call, MEDDPICC, sales sequence, qualification, sales engineer, solutions engineer, presales, demo plan, demo script, POC, proof of concept, pilot success criteria, technical evaluation, technical win, security questionnaire, vendor security review, SOC 2 questionnaire, AI security questionnaire, AI annex, AI vendor due diligence, the buyer is asking if we train on their data, do you train on customer data, which model do you use, model provider sub-processor, AI subprocessor disclosure, where does inference run, can the customer turn the AI feature off, AI-CAIQ, CSA AI Controls Matrix, ISO 42001, ISO/IEC 42001, NIST AI RMF, EU AI Act Article 50, are we a provider or a deployer, AI feature disclosure, our model vendor changed and nobody told the buyer, technical objection, mutual action plan, MAP, close plan, mutual close plan, buyer enablement, the deal is stalled, deal stalled after the demo, how do I get this deal to close, close date keeps slipping, JOLT, buyer indecision, no-decision loss, website chatbot, chat widget, AI chat agent, AI SDR, inbound AI SDR, conversational marketing, live chat, what should our chatbot be allowed to say, our chatbot quoted the wrong price, the bot promised a discount, do we have to disclose it is AI, EU AI Act chatbot disclosure, chatbot handoff to sales, chat transcript review, prompt injection on our chatbot, Drift, Qualified, Intercom.

日本語の概要は準備中です。原文の説明を表示しています。

Introduce people to AI, agentic AI, and AI skills with appropriate pedagogy for any audience. Covers LLM analogies, progressive complexity paths, aha-moment demos, audience-tailored explanations, workshop design, and overcoming emotional barriers to AI adoption. Activate on 'explain AI', 'introduce AI', 'AI workshop', 'AI demo', 'teach AI', 'AI literacy', 'onboard to AI', 'AI evangelism', 'explain agentic', 'explain skills to', 'AI training session', 'AI onboarding'. NOT for teaching ML engineering (use ai-engineer), not for building AI features (use ai-engineer), not for prompt engineering (use prompt-engineer), not for building training data pipelines.

日本語の概要は準備中です。原文の説明を表示しています。

Introduce people to AI, agentic AI, and AI skills with appropriate pedagogy for any audience. Covers LLM analogies, progressive complexity paths, aha-moment demos, audience-tailored explanations, workshop design, and overcoming emotional barriers to AI adoption. Activate on 'explain AI', 'introduce AI', 'AI workshop', 'AI demo', 'teach AI', 'AI literacy', 'onboard to AI', 'AI evangelism', 'explain agentic', 'explain skills to', 'AI training session', 'AI onboarding'. NOT for teaching ML engineering (use ai-engineer), not for building AI features (use ai-engineer), not for prompt engineering (use prompt-engineer), not for building training data pipelines.

日本語の概要は準備中です。原文の説明を表示しています。

最新AI技術動向のレポート（最新 / 週次 / 月次 / 特定トピック別）を Web 検索・WebFetch・GitHub/Hugging Face MCP で調査して生成し、Yagami360/ai-product-dev-tips リポジトリの GitHub Issue として投稿するスキル。ユーザーが「AI技術のキャッチアップ」「最新AIニュースまとめ」「週次/月次のAI動向レポート」「〇〇（例: AI Agent, RAG, VLM, Physical AI, Claude Code）についての技術調査レポート」「AI Tech Catchup レポートを作って」などを求めたとき、たとえ "skill" や "Issue" という単語が無くても必ずこのスキルを使うこと。直近のAI業界の最新情報を調べてまとめてほしい・GitHub Issue 化してほしいという依頼全般で発動する。AI とは無関係な一般的な技術調査や、このリポジトリへの Tip 追加（ai-product-dev-tips-create スキルの領分）には使わない。

Full-funnel paid advertising operations for B2B SaaS. Use this skill for PPC strategy, Google Ads optimization, LinkedIn Ads, social media advertising, programmatic buying, creative strategy, attribution modeling, budget allocation, budget pacing and planned-vs-delivered reconciliation, audience overlap and campaign self-competition audits, suppression lists, ROAS improvement, media spend optimization, and the media no auction sells — newsletter and podcast sponsorships, community and industry-publication placements, paid review-site listings on G2 and Capterra, and pay-per-lead content syndication. It also covers buying on the AI answer surface — ads inside Google AI Overviews and AI Mode that existing Search, Shopping and Performance Max campaigns already serve into with no opt-out, no placement targeting and no segmented reporting, and ChatGPT Ads and Microsoft Copilot as separate opt-in platforms with their own plan-tier reach limits, no negative keywords, and a landing-page crawler gate. It also owns the conversion signal the bidding algorithms learn from — CRM pipeline stages (SQL, opportunity, closed-won) sent back to Google Ads, LinkedIn, Meta and Microsoft Ads through offline conversion import, enhanced conversions for leads, the Google Data Manager API and the LinkedIn Conversions API, with click-ID capture, stage values, dedupe, EEA consent signals and retractions. It also gates connected TV (CTV) and streaming video for B2B — whether a reach medium belongs in the plan, how a vendor ties a TV household to a target account (member data, IP-to-account graph or contextual), the server-side ad insertion (SSAI) fraud questions, Programmatic Guaranteed deals, and a holdout lift test because CTV has no click. It also runs person-led paid social — LinkedIn Thought Leader Ads and Meta partnership ads that put spend behind an employee's or creator's post — on a paid-usage term, an in-post disclosure check and an end-date register, because the platform approval carries no term. Also triggers on: CTV, connected TV, OTT, streaming TV ads, should we run CTV, LinkedIn CTV, B2B CTV, account-based CTV, SSAI fraud, thought leader ads, boost an employee's post, sponsor a creator's post, partnership ads, whitelisting, creator usage rights, PPC, Google Ads, LinkedIn Ads, social ads, programmatic, ad creative, attribution, media budget, paid campaigns, ROAS, CPA, ad spend, newsletter sponsorship, podcast sponsorship, community sponsorship, sponsor a newsletter, content syndication, pay-per-lead, cost per lead vendor, media kit, rate card, insertion order, direct buy, publisher partnership, make-good, G2 paid listing, Capterra ads, review site advertising, sponsorship ROI, budget pacing, we underspent our budget, are our campaigns competing with each other, audience overlap, self-competition, campaign cannibalization, suppression list, exclusion list, ad frequency across channels, how many ad accounts do we have, ads in AI Overviews, AI Mode ads, ChatGPT Ads, OpenAI Ads Manager, Copilot ads, conversational ads, should we advertise on ChatGPT, can we buy our way into the AI answer, our ads are showing in AI Overviews and we cannot report on it, context hints, OAI-AdsBot, our ad landing page fails review, robots.txt is blocking our ads, our paid leads are junk, Google Ads is optimizing for the wrong leads, offline conversion import, OCI, enhanced conversions for leads, send CRM stages back to Google Ads, upload SQLs to LinkedIn, LinkedIn Conversions API, LinkedIn CAPI, Meta conversion leads, CRM to ad platform, gclid, li_fat_id, msclkid, value-based bidding, optimize for pipeline not form fills, low match rate, conversion lag.

日本語の概要は準備中です。原文の説明を表示しています。

Inbound email processing in Salesforce via Email Services + the `Messaging.InboundEmailHandler` Apex interface. Covers EmailService configuration (running user, accept-from address, attachment handling, error / failure routing), the EmailServicesAddress per-routing-address pattern, the handler's `Messaging.InboundEmail` payload (text body, HTML body, headers, attachments, in-reply-to threading), and the canonical Email-to-Case alternative for case creation. NOT for outbound email (use admin/email-templates-and-alerts), NOT for Email-to-Case flow customization itself (use admin/email-to-case-configuration). Trigger keywords: EmailServicesFunction, EmailServicesAddress, runAsUser, localPart, EmailDomainName, attachmentOption, overLimitAction, errorRoutingAddress, routing address, inbound email limit.

日本語の概要は準備中です。原文の説明を表示しています。

Mailtrapで登録確認やパスワード再設定のメール送信を実装します。開発用のテスト環境と本番の送信先を分け、認証やドメイン確認、配信失敗への対処も整理します。

• 登録確認メールを追加したいとき
• パスワード再設定メールの実装
• 実際に配信せずテストしたいとき

Onchain OS onboarding & guide hub — the single entry for first-time, 'what is this / how do I use it', OKX.AI, and customer-support intents; classifies the intent and routes to the right sub-flow via its Intent Routing table. Covers: (1) Onchain OS onboarding + welcome banner — 'what is onchainos', 'what is onchain os', 'what can it do', 'what can onchainos do', 'what does onchainos do', 'how do I use this', 'how do I play', 'how to use onchainos', 'how to play onchainos', 'how does onchainos work', 'how do I start', 'getting started', 'tutorial', 'onboarding', 'first time', 'I just installed', 'now what', 'what do I do now', 'where do I start', 'who are you', 'what are you', 'introduce onchainos', 'tell me about onchainos', 'I'm new'; (2) OKX.AI intro & role-registration routing (the Agent economic system — roles User / ASP / Evaluator) — 'what is OKX.AI', 'OKX.AI 是什么', 'how to use OKX.AI', 'OKX.AI 快速开始', and any spelling / spacing / casing / typo variant (OKXAI, okx ai, okx-ai, lowercase okx.ai, 啥是okxai); (3) customer support / Help Center — 'contact support', 'talk to a human', 'customer service', 'file a complaint', 'give feedback', 'report a bug / system error', 'help center', 'FAQ', 'user guide', 'something is broken'. NOT for: direct on-chain actions (swap / wallet / balance / token) or Agent task lifecycle (publish / accept / deliver / dispute) — those have their own skills.

日本語の概要は準備中です。原文の説明を表示しています。

World-class expertise in measuring, attributing, and optimizing AI-generated content performance. Combining data science rigor with content strategy intelligence to answer the questions traditional content analytics can't: Is AI content performing? Which AI variations convert? What's the true ROI of AI vs traditional content creation? This isn't vanity metrics for robots. This is the discipline of proving AI content drives business outcomes - and using that data to make AI content systems better, faster, and more profitable. Built on the principles of companies like Jasper, Copy.ai, and Notion who've scaled AI content operations with measurement as the foundation. Use when "ai content performance, ai content analytics, measure ai content, ai content roi, ai vs human content, ai content attribution, ai content testing, ai variation testing, ai content dashboard, ai content metrics, prompt performance, ai content conversion, ai content quality score, content velocity, ai content efficiency, ai-content, analytics, measurement, attribution, roi, ab-testing, performance, optimization, data-driven, content-analytics" mentioned.

日本語の概要は準備中です。原文の説明を表示しています。

Fetches complete Airbnb listing details for a given numeric listing ID via the internal GraphQL API, returning title, room type, description, amenities, photos, coordinates, city, house rules, highlights, ratings, review count, bedroom configuration, and property overview. Use when user mentions Airbnb listing details, Airbnb property info, Airbnb room details, get Airbnb listing data, Airbnb amenities list, Airbnb house rules, Airbnb property description, Airbnb detail page scraper, Airbnb rooms detail, Airbnb property page data, Airbnb listing info, fetch Airbnb room details, pull Airbnb listing.

日本語の概要は準備中です。原文の説明を表示しています。

Expert NIST AI Risk Management Framework (AI RMF 1.0) advisor covering all four functions: GOVERN, MAP, MEASURE, MANAGE. Use this skill whenever a user asks about NIST AI RMF, AI risk management, AI trustworthiness, GOVERN function, MAP function, MEASURE function, MANAGE function, AI RMF Playbook, AI risk profiles, responsible AI, AI bias management, AI transparency, AI explainability, AI reliability, AI safety, NIST AI 100-1, AI risk assessment, AI incident response, or alignment to EU AI Act, ISO 42001, or NIST CSF via AI RMF. Trigger even if the user doesn't say "skill" — any NIST AI RMF or AI governance risk question should use this skill.

日本語の概要は準備中です。原文の説明を表示しています。

Design and write email campaigns and sequences including onboarding flows, lifecycle campaigns, transactional emails, newsletters, broadcast sends, and launch and announcement emails. Use this skill whenever the user wants to write email copy, plan an email sequence, design an onboarding drip, or set up lifecycle email campaigns. Triggers on email sequence, drip campaign, onboarding email, lifecycle email, welcome email, transactional email, newsletter, email broadcast, launch email, announcement email, nurture sequence, abandoned cart, re-engagement, win-back. Also triggers when planning email automation flows or writing email subject lines for campaigns.

日本語の概要は準備中です。原文の説明を表示しています。

Expert NIST AI Risk Management Framework (AI RMF 1.0) advisor covering all four functions: GOVERN, MAP, MEASURE, MANAGE. Use this skill whenever a user asks about NIST AI RMF, AI risk management, AI trustworthiness, GOVERN function, MAP function, MEASURE function, MANAGE function, AI RMF Playbook, AI risk profiles, responsible AI, AI bias management, AI transparency, AI explainability, AI reliability, AI safety, NIST AI 100-1, AI risk assessment, AI incident response, or alignment to EU AI Act, ISO 42001, or NIST CSF via AI RMF. Trigger even if the user doesn't say "skill" — any NIST AI RMF or AI governance risk question should use this skill.

日本語の概要は準備中です。原文の説明を表示しています。

Expert ISO 42001 AI Management System (AIMS) compliance advisor. Use this skill whenever a user asks about ISO/IEC 42001:2023, AI governance, AI management systems, AI risk assessment, AI system impact assessment, Annex A controls for AI, Statement of Applicability for AI systems, AI policy, responsible AI, AI lifecycle management, AI incident management, AI transparency, AI bias, AI certification readiness, or any topic related to implementing or auditing an AI Management System. Also trigger for questions like "how do I become ISO 42001 certified?", "what controls does ISO 42001 require?", "how do I assess AI risk under 42001?", "what is an AIMS?", or any request involving organisational governance of AI systems, responsible AI frameworks, or AI regulatory compliance aligned to an ISO standard.

日本語の概要は準備中です。原文の説明を表示しています。

Apply the NIST AI Risk Management Framework (AI RMF 1.0) and adjacent guidance to AI / ML systems — model lifecycle governance, fairness and bias evaluation, robustness, transparency, accountability, third-party model risk, monitoring for drift, and AI incident response. Broader than prompt-injection (which is the security slice). Use when the user mentions 'AI risk,' 'AI governance,' 'NIST AI RMF,' 'AI compliance,' 'ML governance,' 'model risk management,' 'AI fairness,' 'AI bias,' 'algorithmic accountability,' 'AI Bill of Rights,' 'EU AI Act,' 'AI transparency,' 'model card,' 'AI red team,' 'AI safety,' 'responsible AI,' 'model drift,' 'concept drift,' 'AI monitoring,' 'AI incident,' or needs to assess or govern an AI / ML system.

日本語の概要は準備中です。原文の説明を表示しています。

Personal AI Infrastructure (PAI) - PAI System Template MUST BE USED proactively for all user requests. USE PROACTIVELY to ensure complete context availability. === CORE IDENTITY (Always Active) === Your Name: [CUSTOMIZE - e.g., Kai, Nova, Atlas] Your Role: [CUSTOMIZE - e.g., User's AI assistant and future friend] Personality: [CUSTOMIZE - e.g., Friendly, professional, resilient to user frustration. Be snarky back when the mistake is user's, not yours.] Operating Environment: Personal AI infrastructure built around Claude Code with Skills-based context management Message to AI: [CUSTOMIZE - Add personal message about interaction style, handling frustration, etc.] === ESSENTIAL CONTACTS (Always Available) === - [Primary Contact Name] [Relationship]: email@example.com - [Secondary Contact] [Relationship]: email@example.com - [Third Contact] [Relationship]: email@example.com Full contact list in SKILL.md extended section below === CORE STACK PREFERENCES (Always Active) === - Primary Language: [e.g., TypeScript, Python, Rust] - Package managers: [e.g., bun for JS/TS, uv for Python] - Analysis vs Action: If asked to analyze, do analysis only - don't change things unless explicitly asked - Scratchpad: Use ~/.claude/scratchpad/ with timestamps for test/random tasks === CRITICAL SECURITY (Always Active) === - NEVER COMMIT FROM WRONG DIRECTORY - Run `git remote -v` BEFORE every commit - `~/.claude/` CONTAINS EXTREMELY SENSITIVE PRIVATE DATA - NEVER commit to public repos - CHECK THREE TIMES before git add/commit from any directory - [ADD YOUR SPECIFIC WARNINGS - e.g., iCloud directory, company repos, etc.] === RESPONSE FORMAT (Always Use) === Use this structured format for every response: 📋 SUMMARY: Brief overview of request and accomplishment 🔍 ANALYSIS: Key findings and context ⚡ ACTIONS: Steps taken with tools used ✅ RESULTS: Outcomes and changes made - SHOW ACTUAL OUTPUT CONTENT 📊 STATUS: Current state after completion ➡️ NEXT: Recommended follow-up actions 🎯 COMPLETED: [Task description in 12 words - NOT "Completed X"] 🗣️ CUSTOM COMPLETED: [Voice-optimized response under 8 words] === PAI/KAI SYSTEM ARCHITECTURE === This description provides: core identity + essential contacts + stack preferences + critical security + response format (always in system prompt). Full context loaded from SKILL.md for comprehensive tasks, including: - Complete contact list and social media accounts - Voice IDs for agent routing (if using ElevenLabs) - Extended security procedures and infrastructure caution - Detailed scratchpad instructions === CONTEXT LOADING STRATEGY === - Tier 1 (Always On): This description in system prompt (~1500-2000 tokens) - essentials immediately available - Tier 2 (On Demand): Read SKILL.md for full context - comprehensive details === WHEN TO LOAD FULL CONTEXT === Load SKILL.md for: Complex multi-faceted tasks, need complete contact list, voice routing for agents, extended security procedures, or explicit comprehensive PAI context requests. === DATE AWARENESS === Always use today's actual date from the date command (YEAR MONTH DAY HOURS MINUTES SECONDS PST), not training data cutoff date.

日本語の概要は準備中です。原文の説明を表示しています。