5,054 件 ・ 関連度順
概要と使いどころ
Find what a change could break somewhere else before it ships, beyond the diff, and prove the one fact it's safe because of by running real code instead of writing it up. Use for 'blast radius of X', 'what could this break', or reviewing a small diff you don't trust.
日本語の概要は準備中です。原文の説明を表示しています。
知らない分野にキャッチアップするとき、汎用的な言葉から界隈の用語・中心の人・場（学会・雑誌・個人ブログ・動画・リポジトリ・一覧）を特定し、 引用・リンク・著者を芋づる式にたどって、当たりの原文（論文も個人の記事や動画の字幕も）を要約せずそのまま ~/research/<話題>/sources/ に落とす。 周ごとに地図（map.md）を育て、要る主張の全部に原文が付くか飽和したら止める。 見張りのモードでは、地図の場（Qiita・Zenn のタグ、note、YouTube、ブログ、arXiv）の新着を RSS で引いて原文の冒頭つきで並べる。 以下で使用:「芋づる式に調べて」「この分野をキャッチアップしたい」「界隈の用語と人から掘って」 「論文とか先行研究を漁って」「既存の技術を真似したいから元ネタを探して」「上手い人のやり方を集めて」「原文で落として」「/imozuru」 「〇〇って研究あるの？原典ほしい」「全然わからないから流れを掘って」「どういう界隈でどう呼ばれてるか知りたい」 「〇〇の新着見て」「今週の〇〇の記事まとめて」「キャッチアップ」「/imozuru watch」 "dig into this field", "find the canonical papers on X", "literature dive", "what's new in X this week"。 以下には使用しない: 答えが1つの事実の確認（年・有無だけ・仕様1つ → そのまま検索）／ 手元の PC の中の資料を探す／読んだ資料の要約や解説を書く。
Audits and reorganises what an AI coding agent carries in its context window: instruction files, path-scoped rules, skills, subagents, hooks and the running conversation. Use when someone says "the agent ignores our CLAUDE.md", "set this repo up for Claude Code / Codex / Cursor", "my AGENTS.md is too long", "quality drops in long sessions", "it keeps inventing APIs", "what should go in a skill versus the rules file", or asks how to hand work to a subagent. Grounded in the documented loading behaviour of Claude Code, with the equivalents for Codex, Gemini CLI and Cursor.
日本語の概要は準備中です。原文の説明を表示しています。
Builds a content strategy a small team can execute: audience needs backed by counted evidence, an audit of what is already published, a topic map with one page per search intent, a scored backlog, a 90-day calendar sized to real capacity, and the numbers that will show whether it worked. Use when someone asks "what should we write about", "plan our blog", "content strategy", "content plan for next quarter", "topic clusters", "content audit", "our blog traffic is falling", or wants a pile of content ideas turned into a prioritised plan.
日本語の概要は準備中です。原文の説明を表示しています。
Writes the App Store "What's New in This Version" text for an app update from the repository's commit history: finds the range since the last shipped version, separates changes users can notice from internal work, drafts plain-text notes within Apple's 4,000-character limit and review guidelines, and returns a trace from every sentence back to its commits. Use when someone asks to "write release notes for the App Store", "generate What's New from git", "summarize changes since the last tag for the store listing", or needs the same notes cut to Google Play's 500 characters.
日本語の概要は準備中です。原文の説明を表示しています。
Go is the language of infrastructure. From Docker to Kubernetes to the entire cloud-native ecosystem, Go powers the systems that run the internet. It's not about what you can build - it's about what you won't break at 3 AM. This skill covers idiomatic Go patterns, error handling, concurrency with goroutines and channels, HTTP servers, microservice architecture, and the standard library that makes Go so powerful. Key insight: Go's simplicity is a feature. Fight the urge to abstract. Embrace boring, readable code. 2025 lesson: The teams succeeding with Go are the ones who resist overengineering. A main.go with 500 lines beats a "clean architecture" with 50 packages. Use when "golang, go service, go microservice, goroutine, channels, go http, go api, go backend, gin, fiber, chi router, go concurrency, go, golang, microservices, backend, concurrency, goroutines, channels, http, api" mentioned.
日本語の概要は準備中です。原文の説明を表示しています。
The practice of collecting, analyzing, and acting on data to drive product decisions. Great analytics isn't about dashboards—it's about insights that lead to action. Every metric should answer a question that changes behavior. This skill covers event tracking, metrics design, dashboards, user behavior analysis, and data-driven decision making. The best analytics teams measure what matters, not what's easy to measure. Use when "analytics, metrics, tracking, dashboard, funnel, cohort, retention, events, KPI, measure, data, insights, conversion, engagement, analytics, metrics, data, dashboards, tracking, funnels, cohorts, KPIs, insights" mentioned.
日本語の概要は準備中です。原文の説明を表示しています。
awareness-stage-mapper workflow skill. Use this skill when the user needs One sentence - what this skill does and when to invoke it and the operator should preserve the upstream workflow, copied support files, and provenance before merging or handing off.
日本語の概要は準備中です。原文の説明を表示しています。
awareness-stage-mapper workflow skill. Use this skill when the user needs One sentence - what this skill does and when to invoke it and the operator should preserve the upstream workflow, copied support files, and provenance before merging or handing off.
日本語の概要は準備中です。原文の説明を表示しています。
影视编剧 (Scriptwriting / Screenwriting) — 为电影 / 电视 / 流媒体剧集写戏剧蓝本的从业者认知操作系统: 决定「讲什么故事、人物是谁为何转变、场景如何被戏剧化、主题为何重要」的学科 —— 区别于导演 (调度 / 视觉实现)、制片 (融资 / 排期)、小说 (无格式 / 场景 / 视觉动作约束)。覆盖 (a) 故事与结构理论 (亚里士多德《诗学》情节 / 人物 / 思想 + 突转 peripeteia / 发现 anagnorisis + 净化 catharsis; Syd Field 范式 / 三幕 / 情节点; Freytag 金字塔; Egri 前提; McKee《故事》掌控性理念 / 鸿沟 / 价值正负转变 / 激励事件 / 渐进式复杂化; Truby《故事剖析》22 步 + 道德论证; Vogler/Campbell 英雄之旅; Blake Snyder《救猫咪》15 拍节拍表; Dan Harmon 故事环; John Yorke 五幕《进入森林》; Frank Daniel 八序列法; 起承转合东亚戏剧结构), (b) 人物 (想要 vs 需要 / 外在目标 vs 内在缺失, 人物弧光 正 / 负 / 平, flaw-wound-ghost 创伤背景, 主动 vs 被动主角的能动性, Egri 三维人物 生理 / 社会 / 心理, 反派是主角的镜子, 群像与关系网, 人物在压力下的选择中显形), (c) 对白 (潜台词 subtext, 对白即动作与冲突而非信息, 避免太直白 on the nose, 人物独特声口, 信息植入 exposition, Mamet/Sorkin 意图-阻碍式对白, 展示而非告知, 中文剧台词工艺), (d) 场景与序列工艺 (场景是有目标 / 冲突 / 转折的微型故事, 场景价值充能与转折点, 晚进早出, 八序列法, set piece, 转场, 场景头 / 动作行 / 括号提示 格式工艺), (e) 主题与前提 (掌控性理念 / 前提, 主题是被戏剧化的论证而非说教, 道德论证 Truby, 主题统一性, 这到底在讲什么), (f) 类型 (类型惯例是对观众的承诺, Snyder 10 类故事, 颠覆 vs 尊重套路, 类型片 vs 文艺片, 中国类型 主旋律 / 古装 / 年代 / 悬疑 / 甜宠 / 都市 / 军旅 / 历史正剧), (g) 格式与工业流程 (好莱坞剧本格式与 Final Draft, logline 一句话故事, treatment 故事大纲, 节拍表, 分场 / 分集大纲, spec 原创剧本 vs 委托, pitch, coverage, 美剧编剧室与 showrunner 制; 中国 大纲→人物小传→分集大纲→剧本, 长剧集 40 集结构, 网络电影 / 网大, 分账剧, 平台定制剧, 微短剧竖屏短剧), (h) 改稿与开发 (写作就是改写, 改稿 / 润色 / 推倒重写, 处理意见 / 改稿意见, 片方与平台 notes, 杀死你的宝贝, 围读, 开发地狱), (i) 改编 (IP改编 小说 / 漫画 / 游戏改编, 忠于精神而非字句, 压缩, 中国网文 IP 热), (j) 中国影视编剧产业现实 (审查 / 广电总局约束, 备案 / 立项, 平台定制剧 爱优腾芒, 分账, 编剧维权 署名权 / 欠薪 / 枪手, 注水剧, 流量 + 大IP 资本逻辑 vs 原创工艺, 导演中心制 vs 编剧话语权), (k) 编剧职业与工艺生涯 (spec vs 委托, 编剧 vs 编审 / 策划, 单兵 vs 编剧室, 在开发链条中的位置, WGA 与署名仲裁规范, 入行, 中国编剧地位与权益)。跨 电影 / 美剧流媒体 / 中国电影与长剧集。不含 导演 / 摄影 / 制片 / 融资 / 表演 / 电影理论批评为终点 / 泛小说写作 / 纪录片 / 新闻 —— 本 skill 是「戏剧化编剧」工艺: 故事 / 人物 / 场景 / 对白 / 主题 / 结构 / 格式 与围绕它们的产业流程。 (Scriptwriting / Screenwriting for film & TV (影视编剧) — the cognitive operating system of practitioners who write the dramatic blueprint of films, television, and streaming series: the discipline of deciding WHAT story is told, WHO the characters are and why they change, HOW the scenes are dramatized, and WHY it matters thematically — distinct from directing (staging/visual realization), producing (financing/scheduling), and prose fiction (which has no format/scene/visual-action constraints). Covers (a) story & structure theory (Aristotle's Poetics — plot/character/thought + reversal peripeteia/recognition anagnorisis + catharsis; Syd Field's paradigm/three-act/plot points; Freytag's pyramid; Lajos Egri's premise; Robert McKee's Story — controlling idea/the gap/value charge/inciting incident/progressive complications; John Truby's 22 steps & moral argument; Christopher Vogler/Joseph Campbell hero's journey; Blake Snyder's Save the Cat 15-beat sheet; Dan Harmon's story circle; John Yorke's 5-act Into the Woods; Frank Daniel's 8-sequence method; 起承转合 East-Asian dramatic structure), (b) character (want vs need/external goal vs internal lack, character arc positive/negative/flat, 人物弧光, flaw-wound-ghost backstory, agency active vs passive protagonist, Egri's 3-dimensional character physiology/sociology/psychology, antagonist as the protagonist's mirror, ensemble & relationship webs, character revealed through choice under pressure), (c) dialogue (subtext 潜台词, dialogue as action & conflict not information, 'on the nose' avoidance, distinct character voice, exposition handling, Mamet/Sorkin intention-obstacle dialogue, show-don't-tell, 台词 craft in Chinese drama), (d) scene & sequence craft (scene as a mini-story with goal/conflict/turn, scene value charge & turning point, enter-late-leave-early, the 8-sequence method, set pieces, transitions, slug line/action line/parenthetical format craft), (e) theme & premise (controlling idea/premise/前提, theme as dramatized argument not message, moral argument Truby, thematic unity, 'what is this really about'), (f) genre (genre conventions as audience promise, Snyder's 10 story types, subverting vs honoring tropes, 类型片 vs 文艺片, Chinese genres 主旋律/古装/年代/悬疑/甜宠/都市/军旅/历史正剧), (g) format & industry process (Holly
日本語の概要は準備中です。原文の説明を表示しています。
广告外包公司绩效管理 (广告外包公司绩效管理 (Ad Agency / Marketing-Outsourcing Firm Performance Management) — 广告/营销外包公司(乙方 agency:创意热店/4A/本土广告公司/传媒公司/数字营销代理/MCN/设计工作室/内容外包)的『怎么做绩效管理』职业认知操作系统,面向老板/合伙人、运营总监(COO)、HR/HRBP、项目总监、team lead、以及想搭绩效体系的从业者。覆盖: (a) 第一性张力 — 绩效管理的核心世界观分歧: **创意/知识工作『不可量化』 vs 『必须可考核』(创意难归因、难标准化,硬套 KPI 杀创意;但不考核养懒人——这是本行绩效的元矛盾) ⇄ 结果导向(KPI/业绩/回款) vs 过程导向(OKR/能力/成长) ⇄ 个人绩效 vs 团队协作(广告是集体产物,创意-AE-媒介-设计协作,难拆到个人) ⇄ 强激励(提成制:多劳多得但抢单/短视/不协作/吃老客户) vs 稳定(固定+奖金:公平但大锅饭) ⇄ 规模/流水 vs 利润/人效(低价接单冲规模 vs 保毛利)**; (b) 绩效体系设计 — KPI(关键指标法)/OKR(目标与关键成果)/BSC(平衡计分卡)/360 环评/MBO(目标管理)/KSF(关键成功因子)/积分制/计件提成;考核周期(月/季/年+项目制);绩效面谈、绩效改进 PIP、强制分布(271/活力曲线)争议、绩效结果应用(调薪/晋升/淘汰/奖金); (c) 分岗位绩效(本行难点,各岗量化差异极大) — 创意(文案/美术/创意总监:作品质量、获奖、比稿命中率——最难量化)、AE/客户执行(客户满意度、续约、回款、增购、客诉)、媒介/投放(可量化:ROI/ROAS/CPM/转化——最易量化)、策略/策划(方案通过率、洞察)、设计(产能/返稿率/品质)、项目管理(交付准时率、利润率)、销售/BD(新签、回款、毛利); (d) 项目与客户维度绩效(agency 特有,专业服务公司逻辑) — 项目利润率(收入-人力成本-外部成本)、工时制与人效(billability 可计费工时率/utilization 利用率/realization 实现率,借鉴咨询律所)、人均产值/人均毛利、客户续约率与 LTV、客户集中度风险、比稿投入产出、改稿次数失控; (e) 激励与分配机制 — 提成制(按签单/毛利/回款抽成)、项目奖金分成(如何在创意-AE-媒介间分)、年终奖包、合伙人制/事业合伙人/工作室 studio 制/阿米巴、股权期权、创意人才的非物质激励(署名/获奖/成长); (f) 人效、成本与文化 — 人效比(人力成本占收入比,业内估计通常 40-55%,非普适)、毛利率、加班/血汗工厂文化批判(乙方 996/改稿到凌晨)、人才流失率与保留、招聘与培养、组织架构(客户组 vs 职能组 vs 项目制矩阵); (g) 外包/乙方特有张力对绩效的侵蚀 — 甲乙方权力不对等(甲方压价、无限改稿、比稿白嫖创意、账期长垫款重回款难)、低价内卷与红海、项目制不确定性(旺淡季、大客户依赖)、创意工时不可控如何计入绩效、外包 vs 自建团队的成本对比; (h) 争议/批判 — KPI 量化派 vs 创意不可考核派、提成制养蛊 vs 团队协作、强制分布/末位淘汰是否适合小 agency、工时制(billable hours)被咨询律所验证但绑架员工健康、『向甲方看齐做 OKR』水土不服、绩效主义扼杀创意(索尼绩效主义之殇式批判)、乙方绩效本质是『用考核对冲甲方不确定性』的转嫁; (i) 流派/思想谱系 — 专业服务公司管理派(David Maister《Managing the Professional Service Firm》PSF 圣经:leverage 杠杆/utilization 利用率/billing;借鉴咨询律所会计所) vs agency 专家经营派(David C. Baker《The Business of Expertise》+2Bobs podcast、Blair Enns《Win Without Pitching》《Pricing Creativity》定位与定价) vs OKR/目标管理派(John Doerr《Measure What Matters》、Google/Intel OKR、字节/飞书 OKR 本土化) vs 中式绩效工具派(KSF 薪酬全绩效/积分制/阿米巴/华为绩效体系被广告公司借用) vs 本土 4A/广告公司实战派(省广/蓝色光标/华扬联众/利欧 等上市广告公司管理 + 创意热店工作室制)。不含: 广告投放/信息流/SEM 的技术操作本身、甲方市场部/品牌方内部绩效、通用 HR 招聘薪酬全流程(仅取与绩效相关部分)、纯财务会计做账、MCN 达人孵化运营细节。) Master OS — automated mastery of 广告外包公司绩效管理 (Ad Agency / Marketing-Outsourcing Firm Performance Management) — 广告/营销外包公司(乙方 agency:创意热店/4A/本土广告公司/传媒公司/数字营销代理/MCN/设计工作室/内容外包)的『怎么做绩效管理』职业认知操作系统,面向老板/合伙人、运营总监(COO)、HR/HRBP、项目总监、team lead、以及想搭绩效体系的从业者。覆盖: (a) 第一性张力 — 绩效管理的核心世界观分歧: **创意/知识工作『不可量化』 vs 『必须可考核』(创意难归因、难标准化,硬套 KPI 杀创意;但不考核养懒人——这是本行绩效的元矛盾) ⇄ 结果导向(KPI/业绩/回款) vs 过程导向(OKR/能力/成长) ⇄ 个人绩效 vs 团队协作(广告是集体产物,创意-AE-媒介-设计协作,难拆到个人) ⇄ 强激励(提成制:多劳多得但抢单/短视/不协作/吃老客户) vs 稳定(固定+奖金:公平但大锅饭) ⇄ 规模/流水 vs 利润/人效(低价接单冲规模 vs 保毛利)**; (b) 绩效体系设计 — KPI(关键指标法)/OKR(目标与关键成果)/BSC(平衡计分卡)/360 环评/MBO(目标管理)/KSF(关键成功因子)/积分制/计件提成;考核周期(月/季/年+项目制);绩效面谈、绩效改进 PIP、强制分布(271/活力曲线)争议、绩效结果应用(调薪/晋升/淘汰/奖金); (c) 分岗位绩效(本行难点,各岗量化差异极大) — 创意(文案/美术/创意总监:作品质量、获奖、比稿命中率——最难量化)、AE/客户执行(客户满意度、续约、回款、增购、客诉)、媒介/投放(可量化:ROI/ROAS/CPM/转化——最易量化)、策略/策划(方案通过率、洞察)、设计(产能/返稿率/品质)、项目管理(交付准时率、利润率)、销售/BD(新签、回款、毛利); (d) 项目与客户维度绩效(agency 特有,专业服务公司逻辑) — 项目利润率(收入-人力成本-外部成本)、工时制与人效(billability 可计费工时率/utilization 利用率/realization 实现率,借鉴咨询律所)、人均产值/人均毛利、客户续约率与 LTV、客户集中度风险、比稿投入产出、改稿次数失控; (e) 激励与分配机制 — 提成制(按签单/毛利/回款抽成)、项目奖金分成(如何在创意-AE-媒介间分)、年终奖包、合伙人制/事业合伙人/工作室 studio 制/阿米巴、股权期权、创意人才的非物质激励(署名/获奖/成长); (f) 人效、成本与文化 — 人效比(人力成本占收入比,业内估计通常 40-55%,非普适)、毛利率、加班/血汗工厂文化批判(乙方 996/改稿到凌晨)、人才流失率与保留、招聘与培养、组织架构(客户组 vs 职能组 vs 项目制矩阵); (g) 外包/乙方特有张力对绩效的侵蚀 — 甲乙方权力不对等(甲方压价、无限改稿、比稿白嫖创意、账期长垫款重回款难)、低价内卷与红海、项目制不确定性(旺淡季、大客户依赖)、创意工时不可控如何计入绩效、外包 vs 自建团队的成本对比; (h) 争议/批判 — KPI 量化派 vs 创意不可考核派、提成制养蛊 vs 团队协作、强制分布/末位淘汰是否适合小 agency、工时制(billable hours)被咨询律所验证但绑架员工健康、『向甲方看齐做 OKR』水土不服、绩效主义扼杀创意(索尼绩效主义之殇式批判)、乙方绩效本质是『用考核对冲甲方不确定性』的转嫁; (i) 流派/思想谱系 — 专业服务公司管理派(David Maister《Managing the Professional Service Firm》PSF 圣经:leverage 杠杆/utilization 利用率/billing;借鉴咨询律所会计所) vs agency 专家经营派(David C. Baker《The Business of Expertise》+2Bobs podcast、Blair Enns《Win Without Pitching》《Pricing Creativity》定位与定价) vs OKR/目标管理派(John Doerr《Measure What Matters》、Google/Intel OKR、字节/飞书 OKR 本土化) vs 中式绩效工具派(KSF 薪酬全绩效/积分制/阿米巴/华为绩效体系被广告公司借用) vs 本土 4A/广告公司实战派(省广/蓝色光标/华扬联众/利欧 等上市广告公司管理 +
日本語の概要は準備中です。原文の説明を表示しています。
摄影 (摄影 (Photography) — 以静态影像为产出的视觉创作 + 服务行业：从看见 → 用光 → 构图 → 拍摄 → 后期 → 交付的认知操作系统，覆盖商业摄影 (commercial: 产品/广告/电商/美食)、人像摄影 (portrait: 影楼/写真/婚礼/时尚/环境人像)、纪实与街头摄影 (documentary/photojournalism/street)，以及与之贯通的风光、新闻、艺术摄影。面向职业摄影师 / 助理 / 修图师 / 想转职业的资深爱好者 / 服务这行的人 (器材厂商、图库、后期外包、影楼运营)。覆盖: (a) 第一性张力 — **光 (light is the craft — 看光、控光、塑光：硬光/柔光、方向、色温、光比、布光是摄影第一性) ⇄ 器材 (gear — 相机/镜头/灯具迷信, 'GAS' gear-acquisition-syndrome, 'the best camera is the one you have with you' — 器材不是摄影)**; **决定性瞬间/抓取 (decisive moment, Cartier-Bresson, 等待与预判, 纪实/街头不可重来) ⇄ 构建/导演 (constructed/directed, 商业与人像是布光摆姿造光的'制造'而非'捕获')**; **前期/拍对 (get it right in camera, 曝光/白平衡/构图当场拍对) ⇄ 后期/暗房 (post/darkroom, Ansel Adams 'negative is the score, print is the performance' — RAW 冲洗/调色/修图是创作一半)**; **作者性/艺术表达 (vision, personal voice, 'photograph what you feel not what you see') ⇄ 服务性/商业交付 (client brief, 影楼标准化出片, 'shoot the brief not your ego', 摄影是生意)**; **真实/未操纵 (truth, photojournalism ethics, 不过度 PS, 新闻摄影伦理) ⇄ 修饰/理想化 (retouch, 商业人像液化磨皮, 广告的'谎言')**; **决定性技术参数 (曝光三角 aperture/shutter/ISO, 景深, 互易律) ⇄ 看见/眼力 (seeing, 'photography is about seeing not cameras', 构图/光感是 tacit 眼力)**; **胶片/慢/不可见 (film, 慢工, 不可即时回看, 暗房) ⇄ 数码/即时/海量 (digital, chimping, 连拍, 后期无限)**; AI 对摄影的冲击 ('是不是摄影'、生成式填充/换天/AI 修图、真实性危机); (b) 核心工作流 / pipeline (最标准、最易蒸高质量+CLI 化) — 通用链: 看光选光 → 曝光三角决策 (光圈定景深/快门定动静/ISO 兜底) → 测光与曝光 (评价/点测光, 向右曝光 ETTR, 直方图, 区域系统) → 构图 (三分法/引导线/框架/负空间/前景) → 对焦 → 拍摄 → 选片 culling → RAW 后期 (Lightroom/Capture One: 曝光/白平衡/色调曲线/HSL/局部) → 精修 retouch (Photoshop: 频率分离/液化/D&B) → 调色 grading → 输出交付 (色彩管理/sRGB/打印/图库上传); 子流派 SOP: 影棚商业布光 (主光/辅光/轮廓光/背景光, 三点布光, 光质修饰器 softbox/beauty-dish/grid)、婚礼/纪实一天流程、街头扫街、产品/电商台面、人像引导摆姿 posing & direction; (c) 工具栈 — 相机系统 (无反主导: Sony A 系 / Canon R / Nikon Z / 富士 X&GFX / 徕卡 M; 中画幅 Phase One/Hasselblad/GFX 商业; 残幅 vs 全幅 vs 中幅)、镜头 (大三元, 定焦 vs 变焦, 35/50/85 人像三剑客, 微距, 移轴)、灯具 (机顶闪 Godox/Profoto, 影室灯, 常亮 LED, 持续光 vs 闪光)、修饰器 (柔光箱/反光伞/束光筒/雷达罩/旗板)、测光/附件 (测光表, 灰卡, 三脚架, 滤镜 ND/CPL/渐变)、后期软件 (Adobe Lightroom Classic/CC 主导, Capture One 商业/影室, Photoshop 精修, DxO PhotoLab/PureRAW 降噪, Capture One vs Lightroom 之争, 国产: 醒图/泼辣 Polarr/Snapseed 移动端, RawTherapee/Darktable 开源, AI: Lightroom 生成式/Photoshop Generative Fill/Topaz Photo AI/Gigapixel/Luminar Neo)、色彩管理 (X-Rite/Calibrite 校色仪, ICC, 显示器)、图库/交付 (Pixieset/图虫/500px/视觉中国/Getty/Adobe Stock, 客片在线选片); (d) 知识正典 — Ansel Adams 'The Camera / The Negative / The Print' 三部曲 + 区域系统 (Zone System)、Henri Cartier-Bresson 'The Decisive Moment'、Michael Freeman 'The Photographer's Eye' (构图) 'The Photographer's Mind'、Bryan Peterson 'Understanding Exposure' (曝光入门圣经)、Scott Kelby 'Digital Photography Book' 系列 + Lightroom/Photoshop 书、Joe McNally 'The Hot Shoe Diaries / Sketching Light' (闪光灯)、Light Science & Magic (布光科学经典教材)、Roland Barthes 'Camera Lucida' (摄影哲学)、Susan Sontag 'On Photography'、John Szarkowski 'The Photographer's Eye'、National Geographic 摄影指南、Robert Capa / Sebastião Salgado / Steve McCurry (纪实)、Annie Leibovitz / Richard Avedon / Peter Lindbergh (人像/时尚)、Galen Rowell / Ansel Adams (风光); (e) figures/流派 — 风光/系统派 (Ansel Adams 区域系统奠基、Galen Rowell 探险风光、Marc Adamus); 决定性瞬间/纪实街头派 (Henri Cartier-Bresson 奠基、Robert Capa 战地、Sebastião Salgado 社会纪实、Steve McCurry、Vivian Maier、Daido Moriyama、森山大道/荒木经惟 日本派、Vivian Maier); 人像/时尚派 (Richard Avedon、Annie Leibovitz、Peter Lindbergh、Platon、Joey L、Lindsay Adler 时尚布光); 布光/教育派 (Joe McNally、Zack Arias 'one light'、Profoto/strobist David Hobby 'Strobist' 闪光灯启蒙博客、Karl Taylor 商业布光教学); 商业/广告派 (Chase Jarvis 'CreativeLive'创办+'best camera'、Joel Grimes、Tim Wallace 汽车); 后期/修图派 (Pratik Naik、Aaron Nace 'Phlearn'); 街头当代派 (Eric Kim 街头博客、Joel Meyerowitz、Saul Leiter 色彩街头); 中文圈 (李涛 'photoshop教学'、宁思潇潇 器材评测、thomas 'Thomas看看世界' 风光后期、阿刘 风光、668 人像); 哲学/批评 (Susan Sontag、Roland Barthes、John Szarkowski MoMA); (f) 行业话术/黑话 — 曝光三角 exposure triangle / 光圈 aperture f-stop / 快门 shutter speed / 感光度 ISO / 景深 DoF depth of field / 焦段 focal length / 等效 / 全画幅 full-frame vs 残幅 crop / 大三元 / 定焦 prime / 互易律 reciprocity / 向右曝光 ETTR / 直方图 histogram / 高光溢出 clipping / 动态范围 dynamic range / 宽容度 / 白平衡 WB
日本語の概要は準備中です。原文の説明を表示しています。
Analyze GitHub and Discord signals to prioritize maintainer attention. Use when asked about priorities, what's hot, what needs attention, or project status.
日本語の概要は準備中です。原文の説明を表示しています。
Reads the visual content of slides, pages, and images the way a human would, not just their embedded text. Use when a PPTX or PDF has image slides, screenshots, charts, scanned figures, or flattened-to-image layouts that the built-in pptx/pdf skills read as empty; when asked to transcribe, describe, OCR, or extract what is shown in an image, slide deck, or document page; or when embedded-text extraction returned little or nothing from a visually rich file. Triggers on 'read this deck', 'what's on these slides', 'transcribe', 'OCR', 'extract text from image', 'describe this chart/diagram', .pptx/.pdf/.png/.jpg with visual content.
日本語の概要は準備中です。原文の説明を表示しています。
Analyzes an AI/ML publication — paper, preprint, article, technical blog post — and extracts what an enterprise AI engineer should do about it. Use when someone supplies a URL or document on RAG, embeddings, fine-tuning, prompt engineering, agents, or LLM deployment and asks "review this paper", "what do you make of this", "is this worth adopting", or "summarise the method and its limits". The subject matter must itself be machine learning.
日本語の概要は準備中です。原文の説明を表示しています。
Interpret video content visually by sampling frames into timestamped contact sheets that can be read as images. Use when: user asks what happens in a video; asks to summarize, describe, review, or QA video content or footage; asks about scenes, actions, people, or objects in a video; needs a storyboard-style overview of a clip; asks to find where something occurs in a video. Triggers on 'watch this video', 'what's in this video', 'summarize the video', 'describe the footage', 'contact sheet', 'storyboard', 'review this clip', 'find the scene where', 'scene detection', 'shot boundaries', 'detect cuts', 'dwell points'. For converting, trimming, or transcoding video, use processing-video instead.
日本語の概要は準備中です。原文の説明を表示しています。
Break out of a locked problem frame by picking one disciplined move — reframe, provocation (Po), random stimulus, SCAMPER, inversion, structured analogy, constraint play, or family traversal — and committing to it before evaluating. Use when stuck, when options feel narrow or obvious, when iterations produce variations of the same idea, or when the user says "widen this", "break out of", "think differently", "I'm stuck", "feels too obvious", "stress-test the framing", "what am I missing", or holds two related examples and asks what lies between or beyond them. Complements challenging (which evaluates) and convening-experts (which synthesizes viewpoints); this skill generates distance, not judgment.
日本語の概要は準備中です。原文の説明を表示しています。
Pre-change blast-radius report for a symbol or file. Walks tree-sitting references, augments with a plain-text scan over non-parsed files (configs, plain docs), and clusters affected sites by feature (`_FEATURES.md`) or top-level package. Use when about to refactor, rename, or delete something in a repo you don't own — "what breaks if I change `validateUser`", "who calls this", "is this safe to remove", "where is this used", "blast radius", "impact analysis". This is the CONVERGENT pre-change risk skill — for "what is this repo?" use exploring-codebases; for "where is X?" use searching-codebases.
日本語の概要は準備中です。原文の説明を表示しています。
When the user wants to plan, map, or restructure their website's page hierarchy, navigation, URL structure, or internal linking. Also use when the user mentions "sitemap," "site map," "visual sitemap," "site structure," "page hierarchy," "information architecture," "IA," "navigation design," "URL structure," "breadcrumbs," "internal linking strategy," "website planning," "what pages do I need," "how should I organize my site," or "site navigation." Use this whenever someone is planning what pages a website should have and how they connect. NOT for XML sitemaps (that's technical SEO — see seo-audit). For SEO audits, see seo-audit. For structured data, see schema.
日本語の概要は準備中です。原文の説明を表示しています。
When the user needs marketing ideas, inspiration, or strategies for their SaaS or software product. Also use when the user asks for 'marketing ideas,' 'growth ideas,' 'how to market,' 'marketing strategies,' 'marketing tactics,' 'ways to promote,' 'ideas to grow,' 'what else can I try,' 'I don't know how to market this,' 'brainstorm marketing,' or 'what marketing should I do.' Use this as a starting point whenever someone is stuck or looking for inspiration on how to grow. For specific channel execution, see the relevant skill (ads, social, emails, etc.).
日本語の概要は準備中です。原文の説明を表示しています。
When the user wants to create, plan, or optimize a lead magnet for email capture or lead generation. Also use when the user mentions "lead magnet," "gated content," "content upgrade," "downloadable," "ebook," "cheat sheet," "checklist," "template download," "opt-in," "freebie," "PDF download," "resource library," "content offer," "email capture content," "Notion template," "spreadsheet template," or "what should I give away for emails." Use this for planning what to create and how to distribute it. For interactive tools as lead magnets, see free-tools. For writing the actual content, see copywriting. For the email sequence after capture, see emails.
日本語の概要は準備中です。原文の説明を表示しています。
When the user wants to conduct, analyze, or synthesize customer research. Use when the user mentions "customer research," "ICP research," "talk to customers," "analyze transcripts," "customer interviews," "survey analysis," "support ticket analysis," "voice of customer," "VOC," "build personas," "customer personas," "jobs to be done," "JTBD," "what do customers say," "what are customers struggling with," "Reddit mining," "G2 reviews," "review mining," "digital watering holes," "community research," "forum research," "competitor reviews," "customer sentiment," or "find out why customers churn/convert/buy." Use for both analyzing existing research assets AND gathering new research from online sources. For writing copy informed by research, see copywriting. For acting on research to improve pages, see cro.
日本語の概要は準備中です。原文の説明を表示しています。
Use when writing tests, improving coverage, or deciding what to test in this CLI
日本語の概要は準備中です。原文の説明を表示しています。
Use when the user asks which paad skills exist, what a paad skill does, which one fits their situation, or how to invoke one — including "what can paad do", "list the paad skills", "is there a paad skill for X", or a request for the arguments of a named paad skill
日本語の概要は準備中です。原文の説明を表示しています。