「goal」の検索結果

The craft of producing creative assets that communicate brand, product, and message effectively. Creative communications bridges strategy and execution—translating brand positioning and marketing goals into visual, audio, and interactive experiences that resonate with audiences. This skill covers creative briefing, creative production workflows, asset creation, creative feedback, and cross-channel creative adaptation. Great creative communications amplifies strategy; it doesn't replace it. Use when "creative, creative brief, assets, video, motion, animation, creative production, photoshoot, visual content, creative review, ad creative, creative feedback, creative, production, video, motion, assets, briefs, feedback, visual-content" mentioned.

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

Expert in designing community strategies that align with business goals while creating genuine value for members. Covers community-market fit, positioning, culture design, governance models, and long-term roadmapping. Understands that great communities are intentionally designed, not accidentally grown. Use when "community strategy, build a community, community vision, community culture, community roadmap, community-market fit, why community, " mentioned.

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

Your most loyal users aren't just customers - they're potential advocates, contributors, and community members who can become the engine of your growth. Community-led growth isn't about broadcasting to an audience - it's about creating a space where your users connect with each other, share knowledge, and become invested in your success. This skill covers community strategy, platform selection, engagement tactics, ambassador programs, and the metrics that matter. Whether you're building a Discord for developers or a forum for power users, the goal is the same: creating genuine value that makes members want to stay and contribute. Use when "community, discord, forum, user group, ambassador, champions, developer relations, devrel, community engagement, community growth, power users, superfans, community, discord, engagement, devrel, ambassador, forum, user-community, growth, retention, champions" mentioned.

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

供应链与生产运营 (供应链与生产运营 (Supply Chain & Production Operations) — 面向制造业与消费品实体供应链的『计划-制造-交付』运营判断,不是采购谈价技巧,也不是跨境电商发货物流。覆盖: (a) 第一性张力 — 这行的核心世界观分歧: **流动 > 局部效率(用有效产出/流动时间看系统,而不是用设备利用率/人均产出看工位;非瓶颈上的效率是幻觉) ⇄ 精益拉动 vs 推式预测(TPS/JIT 按下游消耗拉动、小批量平准化 vs MRP 按预测展开净需求推动;DDMRP 解耦缓冲是第三条路) ⇄ 精益/丰田 TPS 派 vs 约束理论 TOC 派(消除七大浪费、全局改善 vs 五步聚焦瓶颈、鼓-缓冲-绳 DBR 排产;两派互相指责对方浪费时间/只治标) ⇄ 变异是敌人(Deming/六西格玛/Factory Physics 的 VUT 排队论: 利用率越靠近满载排队时间越爆炸,交期长不是产能不够而是变异+高负荷) ⇄ 库存是负债 vs 库存是缓冲(会计把库存记成资产、精益视其为掩盖问题的水位、TOC 与韧性派视其为吸收变异的必要缓冲;真问题是缓冲放在哪一层而不是有没有) ⇄ 精益 JIT vs 韧性冗余(2020-2023 断链后 just-in-case、多源、近岸/友岸的回摆;精益派反驳崩的是『假精益』——单一来源+砍库存不砍变异) ⇄ 服务水平 vs 库存成本(安全库存/报童模型/ABC-XYZ 的经典取舍,牛鞭效应放大上游波动) ⇄ 成本导向压价 vs 供应商共生开发(Kraljic 分级、丰田供应商协会式长期共生 vs 年降指标与竞价) ⇄ 一个数 vs 各部门各算各的(S&OP/IBP 的本质是跨职能对齐到一套数字与一份产销计划))**; (b) 工具栈(此行的工具是『系统+方法』的混合) — ERP/MRP(SAP S/4HANA PP·MM、Oracle、用友·金蝶、Odoo、NetSuite)、APS 高级计划排程(Kinaxis RapidResponse、o9、Blue Yonder、SAP IBP、OMP、Siemens Opcenter APS)、MES/车间执行(Siemens Opcenter、Rockwell FactoryTalk、黑湖智造)、WMS/TMS、需求预测(统计模型 + Nixtla StatsForecast/Prophet、FVA 预测增值分析)、运筹优化与仿真(OR-Tools、Gurobi、Pyomo、AnyLogic、FlexSim、SimPy)、供应链风险与多级可视(Resilinc、Everstream、Interos)、分析层(SQL/Python pandas/Power BI)、以及纸笔工具(价值流图 VSM、A3、看板、标准作业票)—— 选型决策树的关键分岔是 MTS/MTO/ATO/ETO 履行模式与需求变异度,而非厂商功能清单; (c) 心智模型层 — 利特尔法则(在制品 = 产出率 × 流动时间)、瓶颈与非瓶颈、缓冲三态(库存/时间/产能缓冲)、解耦点(客户订单渗透点 CODP)、牛鞭效应、takt time 节拍与产线平衡、OEE 与六大损失、muda·mura·muri 三种浪费、自働化 jidoka 与安灯、防错 poka-yoke、SMED 快速换模换出小批量、平准化 heijunka、PDCA 与丰田改善型 Toyota Kata、DMAIC 与 Cpk 过程能力、报童模型与安全库存公式、ABC-XYZ 分级; (d) 工作流/SOP — 跑一轮月度 S&OP(需求评审→供应评审→预 S&OP→执行 S&OP)、做需求预测与预测误差复盘(MAPE/WMAPE/bias/FVA)、设定库存分级与安全库存、MRP 跑批与例外消息处理(缺料齐套与 MRP 神经质)、瓶颈识别与 DBR 排产、价值流图现状图→未来图→改善计划、新品导入 NPI 与多级 BOM/ECN 工程变更、供应商选择与开发(RFQ→审厂→APQP/PPAP→量产→年度绩效)、断料应急与交期承诺(ATP/CTP)、循环盘点与库存准确率; (e) 知识正典(en/ja 一手极厚,中译齐全) — 《目标 The Goal》Goldratt(TOC 小说体奠基)、《丰田生产方式》大野耐一、《改变世界的机器》Womack·Jones·Roos(MIT IMVP 研究)、《精益思想 Lean Thinking》Womack & Jones、《丰田模式 The Toyota Way》Liker、《工厂物理学 Factory Physics》Hopp & Spearman(排队论视角的运营科学)、《学习观察 Learning to See》Rother & Shook(VSM)、《丰田套路 Toyota Kata》Rother、Spear & Bowen 的 HBR 1999《Decoding the DNA of the Toyota Production System》、Lee/Padmanabhan/Whang 1997《The Bullwhip Effect in Supply Chains》、Ptak & Smith 的 DDMRP、Orlicky 的 MRP、Chopra & Meindl 的供应链管理教材、Deming《转危为安 Out of the Crisis》、Sheffi《The Resilient Enterprise》、ASCM/APICS 的 SCOR 参考模型与 CPIM/CSCP 知识体系; (f) 行业大佬/figures — 大野耐一(TPS 立法者)、新乡重夫(SMED/防错)、Eliyahu Goldratt(TOC 创立者)、W. Edwards Deming(变异与系统观)、James Womack & Daniel Jones(把 TPS 译成西方可学的『精益』)、Jeffrey Liker(丰田模式学术化)、Mike Rother(VSM 与改善型)、Wallace Hopp & Mark Spearman(工厂物理学)、Hau Lee(斯坦福,牛鞭效应与 Triple-A 供应链)、Yossi Sheffi(MIT,韧性)、Carol Ptak & Chad Smith(DDMRP)、David Simchi-Levi(MIT,风险敞口指数)、Steven Spear(TPS 的 DNA)、以及中文圈的供应链实务作者(刘宝红等); (g) 争议/批判(必须保留不洗白) — JIT 是不是 2021 全球断链的元凶(精益派反驳:崩的是单一来源+砍库存不砍变异的『假精益』);西方学精益的高失败率(只搬工具不搬思维,精益在很多工厂沦为裁员的代号);六西格玛黑带官僚化与扼杀创新之争;TOC 派与精益派互相攻击(Goldratt 讽刺精益是等浪费自己浮现);预测无用论(需求驱动派说预测必然错、要靠缓冲吸收)vs 统计预测派;控制塔/数字孪生/AI 预测的过度承诺与高项目失败率;中国制造的年降与内卷式压价 vs 供应商共生;近岸·友岸外包是真实产能转移还是政治叙事; (h) 流派/思想谱系 — **精益/TPS 派(丰田血统:大野-新乡→Womack/Jones/Liker/Rother,信全局消除浪费与人的改善能力)** vs **约束理论 TOC 派(Goldratt:系统产出只由瓶颈决定,聚焦五步、DBR、缓冲管理)** vs **统计质量/六西格玛派(Deming-Juran-Shewhart→GE/Motorola,信减少变异与过程能力)** vs **运营科学/工厂物理学派(Hopp & Spearman:用排队论与数学定律解释,认为精益与 TOC 都是特例)** vs **需求驱动/DDMRP 派(Ptak & Smith:预测不可靠,靠战略解耦缓冲)** vs **韧性/风险派(Sheffi、Simchi-Levi:效率之外必须为断链设计)**。不含: 跨境电商卖家的发货与头程物流(已由 cross-border-ecommerce 覆盖)、纯采购的商务谈判技巧、企业级 ERP 的代码实施与二次开发、通用项目管理。) Master OS — automated mastery of 供应链与生产运营 (Supply Chain & Production Operations) — 面向制造业与消费品实体供应链的『计划-制造-交付』运营判断,不是采购谈价技巧,也不是跨境电商发货物流。覆盖: (a) 第一性张力 — 这行的核心世界观分歧: **流动 > 局部效率(用有效产出/流动时间看系统,而不是用设备利用率/人均产出看工位;非瓶颈上的效率是幻觉) ⇄ 精益拉动 vs 推式预测(TPS/JIT 按下游消耗拉动、小批量平准化 vs MRP 按预测展开净需求推动;DDMRP 解耦缓冲是第三条路) ⇄ 精益/丰田 TPS 派 vs 约束理论 TOC 派(消除七大浪费、全局改善 vs 五步聚焦瓶颈、鼓-缓冲-绳 DBR 排产;两派互相指责对方浪费时间/只治标) ⇄ 变异是敌人(Deming/六西格玛/Factory Physics 的 VUT 排队论: 利用率越靠近满载排队时间越爆炸,交期长不是产能不够而是变异+高负荷) ⇄ 库存是负债 vs 库存是缓冲(会计把库存记成资产、精益视其为掩盖问题的水位、TOC 与韧性派视其为吸收变异的必要缓冲;真问题是缓冲放在哪一层而不是有没有) ⇄ 精益 JIT vs 韧性冗余(2020-2023 断链后

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

Interactive codebase orientation for a HUMAN who wants to learn the code. Runs the same tree-sitting + featuring pipeline as exploring-codebases but synthesizes it into guided exercises and an HTML teaching artifact rather than an analysis document. Use for "orient me to this repo", "teach me this codebase", "walk me through this code", "learning orientation", or when someone wants genuine comprehension rather than a task completed. The audience is the test: if nobody is being taught and the goal is to get work done, use exploring-codebases instead.

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

Builds and revises a complete skill DIRECTORY — SKILL.md, scripts, references, assets — and packages it. Use for "create a skill for X", "turn this into a skill", "update/improve this skill", "why doesn't my skill trigger", "review this SKILL.md", "package this skill", or when a repeated procedure should become a reusable artifact. Enforces the structure that makes skills work — a concrete procedure rather than a goal statement, an explicit applicability boundary, failure modes with their signals, a runtime verification step, and a description checked against the existing catalogue for confusability. For choosing whether the instruction should be a skill at all rather than project instructions or a prompt, use crafting-instructions. For writing quality inside the prose, use writing-instructions.

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

Create refined user personas from research data with demographics, goals, frustrations, and behavioral patterns. Use when synthesizing user research into actionable persona profiles for design decisions.

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

Apply David Ogilvy's advertising principles when writing or reviewing copy, headlines, product descriptions, landing pages, ads, emails, or any persuasive text. Use when the goal is copy that sells, not copy that wins awards. Covers positioning, headlines, promises, brand voice, long-form copy, and visual logic. Source: How to Create Advertising That Sells (1972) + Ogilvy on Advertising.

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

Write clear design rationale connecting decisions to user needs, business goals, and principles.

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

Advocate for design quality, scope, and time with cross-functional partners and leadership using evidence and shared goals.

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

Reverse-engineer the hook from a viral X (Twitter) tweet or thread URL. Identifies which of the 10 canonical 2026 X formulas it uses (one-liner contrarian, data-point, build-in-public, quote-tweet, mini-list, relatable cold-open, listicle-thread, story thread, curiosity-gap, how-I teardown), explains why it worked, and returns a blank template mapped to your topic with its primary goal. Use to learn from a tweet you admire. Not for writing your own (use x-post-writer or x-thread-builder).

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

Draft a single tweet or short auto-thread for X (Twitter) using a 2026 X hook formula (one-liner contrarian, data-point, build-in-public, mini-list, relatable cold-open), picked by goal (replies, reposts, likes, bookmarks). Respects the 280-char limit (25,000 on Premium), runs the humanizer pass, and publishes via Publora on approval. Use to write a tweet from notes. Not for long threads (use x-thread-builder) or auditing a draft (use x-humanizer --mode audit).

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

Build a long-form X (Twitter) thread (tweetstorm) using a 2026 thread formula (listicle-thread, story thread, curiosity-gap opener, how-I teardown), picked by goal (bookmarks, likes, reposts, replies). Structures tweet 1 as a promise plus open loop, paces one beat per tweet, and closes for the repost. Publishes via Publora, which auto-splits long content into a numbered (1/N) thread. Not for single tweets (use x-post-writer) or auditing a draft (use x-humanizer --mode audit).

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

Applies the reasoning, principles, and mental models of Sebastian Thrun (robotics and self-driving cars pioneer, founder of Google X, Waymo, Udacity, Stanford University). Reach for this skill whenever Claude is asked to advise on hardware/software systems engineering, autonomous vehicles, moonshot ideation, probabilistic robotics (SLAM), or leading high-stakes engineering teams. Trigger this skill for discussions on democratizing education, regulating AI, transitioning from academic research to product development, or managing technical teams with empathy. Use it to shift focus from incremental component debates to end-to-end execution and audacious goals.

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

Applies the reasoning, principles, and frameworks of Jürgen Schmidhuber (LSTM co-inventor and deep learning pioneer). Reach for this skill whenever tackling problems involving sequence learning, artificial curiosity, intrinsic motivation, reinforcement learning architectures, or predicting long-term technological and cosmic evolution. Use this when discussing AGI timelines, the history and attribution of AI breakthroughs, data compression as learning, or when designing autonomous agents that must set their own goals. Trigger this skill for topics like recurrent neural networks, algorithmic information theory, open-source AI democratization, and evaluating true existential risks versus media hype.

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

Suede-owned product-marketing context discipline. Use when a project needs a shared record of product, audience, ICP, positioning, objections, customer language, proof, and goals, or when that record needs updating. NOT FOR: writing a campaign (use suede-campaign-in-a-box), conducting new customer interviews (use suede-customer-research), or publishing brand claims.

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

Generate a self-contained handoff prompt that lets the user continue work in a fresh coding agent session with empty context. The prompt captures everything a new agent needs: project, goal, progress, decisions, current state, and remaining work. **Triggers — use this skill when:** - User says "handoff", "hand off", "hand-off" - User asks to "generate a continuation prompt" - User says "give me a prompt to continue this" - User asks to "wrap up for a new session" - User says "context transfer", "session transfer" - User asks "how do I pick this up later" - User wants to "pass this to another agent"

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

Run a structured weekly review covering projects, habits, goals, and planning. Use when asked for a weekly review, week summary, or weekly planning session.

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

Alert by webhook/email on web changes — use for "monitor/watch/track/alert me when": recurring checks on known URLs (prefer over repeated one-off scrapes) or web-wide watches for new results (queries + goal).

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

Apply senior software engineering standards when writing, editing, or refactoring any code. Use this skill whenever the user asks to write a function, build a feature, fix a bug, design a module, or improve existing code — even if they don't mention quality explicitly. The goal is production-grade code: readable, correct, maintainable, secure, and failure-aware. Always active for any coding task, at any scale.

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

Find, rank, and safely remove accidental codebase complexity by proving real consumers, dynamic entrypoints, compatibility obligations, duplicate representations, speculative surfaces, and lifecycle ownership. Use when asked to simplify or clean up a repository, reclaim code entropy, reduce over-engineering or redundancy, find deletion candidates, collapse duplicate state/APIs, remove dead or added-then-abandoned code beyond static-tool output, or implement an evidence-backed simplification pass in any language or stack. Also trigger for 代码化简、熵回收、删代码、清理冗余、收敛抽象、去除过度设计. Do not use as a performance audit unless simplification is the stated goal.

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

Use when the CTO describes a feature, task, or project goal. Orchestrates the full SDLC pipeline automatically based on project type.

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

Alert by webhook/email on web changes — use for "monitor/watch/track/alert me when": recurring checks on known URLs (prefer over repeated one-off scrapes) or web-wide watches for new results (queries + goal).

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

This skill should be used when the user asks to "optimize my LinkedIn profile", "update my LinkedIn headline", "rewrite my LinkedIn summary", "improve my LinkedIn about section", or when Genesis identifies that the user's profile doesn't align with their current goals or target audience.

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