738 件 ・ 関連度順
概要と使いどころ
API Design Principles workflow skill. Use this skill when the user needs Master REST and GraphQL API design principles to build intuitive, scalable, and maintainable APIs that delight developers and stand the test of time and the operator should preserve the upstream workflow, copied support files, and provenance before merging or handing off.
日本語の概要は準備中です。原文の説明を表示しています。
API Design Principles workflow skill. Use this skill when the user needs Master REST and GraphQL API design principles to build intuitive, scalable, and maintainable APIs that delight developers and stand the test of time and the operator should preserve the upstream workflow, copied support files, and provenance before merging or handing off.
日本語の概要は準備中です。原文の説明を表示しています。
CEO (Chief Executive Officer) — 一家公司「最高操作员」的工艺, 与泛泛「领导力 / 管理学」不同: (a) 设定战略与凝结愿景 (Drucker 的「企业的经营理论」+ Porter 论定位 + Hamilton Helmer 的「七力」+ Andy Grove 的「战略转折点」+ Roger Martin 《Playing to Win》); (b) 资本配置是 CEO 单一最高杠杆的工作 (Buffett/Munger Berkshire 致股东信 + William Thorndike 《The Outsiders 商界局外人》论 8 位非常规 CEO + Michael Mauboussin 论 hurdle rate + Bezos 年度致股东信「invariants vs bets」+ Mark Leonard Constellation Software); (c) 组建与领导高管班子 (Patrick Lencioni 《团队的五大障碍》+ Ben Horowitz 《艰难的事》+ Reed Hastings 《No Rules Rules》人才密度 + Andy Grove HOP《高产出管理》+ Lou Gerstner IBM 转型 + Marshall Goldsmith); (d) 董事会与投资人关系 (Larcker & Tayan 《公司治理重要》+ Bill George 《True North》+ 正式 CEO-董事长 / CEO-独立董事 protocol + 维权投资人 playbook + 资本市场沟通); (e) 企业文化与价值观作为操作系统 (Netflix 文化手册 + Amazon Leadership Principles + Bridgewater 《Principles》Ray Dalio + Schein 论组织文化 + 任正非 灰度 + 张瑞敏 人单合一 + 稻盛和夫 阿米巴); (f) 高不确定下的高风险决策 (Bezos Type 1/Type 2 决策 + premortem Klein + Kahneman 论 executive bias + RAPID/DACI + base rates + 情景规划 + 反思 premortem); (g) 对内对外沟通 (创始人 / CEO 致股东信作为机构构建工具: Bezos / Buffett / Reed Hastings 备忘录 / 任正非 内部讲话 + Town Hall + 危机沟通 Tylenol/Boeing/Wells Fargo + 应对维权投资人); (h) 跨阶段规模化 (创业 0→1 / 扩张 1→100 / 成熟期掌舵 / 危机转型): Steve Blank + Brian Chesky founder-mode + Marc Andreessen + Pierre Lassonde + Lou Gerstner 转型; (i) 创始人 CEO vs 职业经理人 CEO 的差异 (Paul Graham 「Founder Mode」2024 + Brian Chesky + Reed Hastings (创始人→职业过渡) + BCG/McKinsey 的「manager mode」+ 两者各自代价 + 什么时候切换)。诚实处理: 幸存者偏差 (单个 CEO 的打法 ≠ 普适规律, 学术研究显示 CEO 个人方差约 ⅓, 约 70% 来自行业 / 时代 / 运气 / 资本结构), 创始人崇拜, 区分可复制工艺与不可移植个人魅力, 治理与利益相关者责任 (员工 / 股东 / 社会), 反对 CEO 神话与 Welch 退休金扭曲 / Theranos / WeWork / FTX / Uber-Kalanick 时代 / Musk 80h+ / 996 工时崇拜。覆盖 founder-CEO (Bezos/Hastings/黄仁勋/Chesky/Brin/任正非) 与职业 CEO (Nadella/Gerstner/Pichai/Mulally/Lafley)。不含: 泛泛管理理论 (商业书已覆盖, 本 skill 专谈 C-suite 这个具体岗位), 不含: 「领导力」作为个人成长自助 (Robbins/Tracy/Maxwell 励志体裁), 不含: 「如何创业」早期战术 — 一旦有员工 / 董事会 / 资本, CEO 的工艺才开始。 (CEO (Chief Executive Officer) — the craft of being the top operator of a company, distinct from generic 'leadership/management': (a) setting the strategy and crystallizing the vision (Drucker's 'theory of the business' + Porter on positioning + Hamilton Helmer's 7 powers + Andy Grove's strategic inflection points + Roger Martin Playing to Win); (b) capital allocation as the CEO's single highest-leverage job (Buffett/Munger Berkshire letters + William Thorndike 'The Outsiders' on 8 unconventional CEOs + Michael Mauboussin on hurdle rates + Bezos's annual shareholder letter approach to invariants vs bets + Mark Leonard Constellation Software); (c) building and leading the executive team (Patrick Lencioni 'Five Dysfunctions' + Ben Horowitz 'Hard Things About Hard Things' + Reed Hastings 'No Rules Rules' on talent density + Andy Grove HOP + Lou Gerstner IBM turnaround + Marshall Goldsmith); (d) board and investor relations (Larcker & Tayan 'Corporate Governance Matters' + Bill George 'True North' + the formal CEO-Chair / CEO-Lead Director protocols + activist investor playbooks + capital markets communication); (e) culture and values as operating system (Netflix culture deck + Amazon Leadership Principles + Bridgewater 'Principles' Ray Dalio + Schein on org culture + 任正非 Ren Zhengfei 灰度 + 张瑞敏 Zhang Ruimin 人单合一 + 稻盛和夫 阿米巴); (f) high-stakes decision-making under uncertainty (Bezos Type 1 vs Type 2 + premortem Klein + Kahneman 'Thinking Fast and Slow' for executive bias + RAPID/DACI + base rates + scenario planning + premortem); (g) internal and external communication (founder/CEO letters as institution-builders: Bezos shareholder letters / Buffett letters / Reed Hastings memos / 任正非 内部讲话 + Town Halls + crisis communication Tylenol/Boeing/Wells Fargo + activist responses); (h) cross-stage scaling (founder-CEO of 0→1 / scaling 1→100 / mature-stage stewardship / turnaround): Steve Blank + Brian Chesky founder-mode + Marc Andreessen + Pierre Lassonde mining vs steady-state + Lou Gerstner turnaround; (i) the founder-CEO vs professional-manager-CEO distinction (Paul Graham 'Founder Mod
日本語の概要は準備中です。原文の説明を表示しています。
複数のスキルに共通する行動原則を抽出し、既存ルールとの重複や不足を確認します。根拠と修正文案を示し、利用者の承認後にルールファイルへ反映するスキルです。
Apply timeless marketing and business principles to any problem. Use when someone needs strategic thinking, wants to evaluate a marketing decision, needs a framework for a tough choice, or mentions "first principles," "should I do X," "what would work here," or wants to think through a marketing problem systematically.
日本語の概要は準備中です。原文の説明を表示しています。
Foundational software design principles applied specifically to robotics module development. Use this skill when designing robot software modules, structuring codebases, making architecture decisions, reviewing robotics code, or building reusable robotics libraries. Trigger whenever the user mentions SOLID principles for robots, modular robotics software, clean architecture for robots, dependency injection in robotics, interface design for hardware, real-time design constraints, error handling strategies for robots, configuration management, separation of concerns in perception-planning- control, composability of robot behaviors, or any discussion of software craftsmanship in a robotics context. Also trigger for code reviews of robotics code, refactoring robot software, or designing APIs for robotics libraries.
日本語の概要は準備中です。原文の説明を表示しています。
Applies KISS, YAGNI, and SOLID principles for clean code with reduced complexity. Use when refactoring or reviewing code for over-engineering.
日本語の概要は準備中です。原文の説明を表示しています。
Guides compliance with Canada's Personal Information Protection and Electronic Documents Act (PIPEDA, S.C. 2000, c. 5). Covers the 10 fair information principles in Schedule 1, consent requirements, cross-border transfer obligations, breach notification under Division 1.1, and OPC enforcement. Keywords: PIPEDA, Canada privacy, fair information principles, OPC, breach notification, cross-border transfer, consent.
日本語の概要は準備中です。原文の説明を表示しています。
Facilitate a structured conversation to define DDD guardrails for domain design within a repository. Produces a formal ddd-principles.md document that the domain-driven-design atom will use as its override. Use when setting up domain design principles, defining aggregate rules, or when the user says 'setup DDD', 'define domain rules', 'DDD principles', or 'help me define my domain patterns'.
日本語の概要は準備中です。原文の説明を表示しています。
Axiom — First-Principles Assumption Auditor / 第一性原理拆解器 workflow skill. Use this skill when the user needs First-principles assumption auditor. Classifies each hidden assumption (fact / convention / belief / interest-driven), ranks by fragility × impact, and rebuilds conclusions from verified premises. Bilingual: auto-detects Chinese or English and the operator should preserve the upstream workflow, copied support files, and provenance before merging or handing off.
日本語の概要は準備中です。原文の説明を表示しています。
Axiom — First-Principles Assumption Auditor / 第一性原理拆解器 workflow skill. Use this skill when the user needs First-principles assumption auditor. Classifies each hidden assumption (fact / convention / belief / interest-driven), ranks by fragility × impact, and rebuilds conclusions from verified premises. Bilingual: auto-detects Chinese or English and the operator should preserve the upstream workflow, copied support files, and provenance before merging or handing off.
日本語の概要は準備中です。原文の説明を表示しています。
中医诊疗 — 中医临床医师的认知操作系统 (经典理论 阴阳五行脏腑气血经络六经卫气营血三焦 + 四诊八纲 + 治法 + 方剂学 经方时方 + 中药学 四气五味归经炮制 + 针灸学 经络穴位手法灸法 + 推拿按摩 + 中医各科 内外妇儿骨伤皮肤眼耳鼻喉肛肠老年急症 + 中西医结合 + 循证中医 + NATCM 监管 + 中医诊所备案 + 国家级名老中医 学术继承人 — 不含 道家修炼 / 风水算命 / 中医养生科普 / 中医美容 / 民族医学藏蒙维傣) (Traditional Chinese Medicine (TCM) clinical practice — the cognitive operating system of practicing TCM physicians covering (a) 经典理论 (阴阳/五行/脏腑/气血津液/经络/六淫/七情/六经/卫气营血/三焦) classical theory, (b) 四诊 (望闻问切) clinical observation/inquiry/pulse + 八纲 (阴阳/表里/寒热/虚实) syndrome differentiation, (c) 治法 (汗吐下和温清消补 + 扶正祛邪) therapeutic principles, (d) 方剂学 (经方 时方 验方) formula science, (e) 中药学 (四气五味/归经/七情/炮制/配伍禁忌) materia medica, (f) 针灸学 (经络穴位/手法/灸法/电针) acupuncture+moxibustion, (g) 推拿按摩 tuina massage, (h) 中医各科 (内/外/妇/儿/骨伤/皮肤/眼/耳鼻喉/肛肠/老年/急症) clinical specialties, (i) 中西医结合 integrative medicine, (j) 循证中医 + 临床流行病学 evidence-based TCM + 现代研究, (k) 中医诊所备案 / 中医师资格 / NATCM 监管 / 药典 / GMP regulatory framework, (l) 国家级名老中医 学术继承人 项目 transmission program; NOT 道家修炼 / 风水 / 算命八字 (那是 玄学不是 中医), NOT 中医养生科普 (是 衍生 不是 临床主体), NOT 中医美容 (是 商业化分支), NOT 民族医学 (藏蒙维傣 是 平行体系 不在本 skill 主线 — 仅作 边界标注).) Master OS — automated mastery of Traditional Chinese Medicine (TCM) clinical practice — the cognitive operating system of practicing TCM physicians covering (a) 经典理论 (阴阳/五行/脏腑/气血津液/经络/六淫/七情/六经/卫气营血/三焦) classical theory, (b) 四诊 (望闻问切) clinical observation/inquiry/pulse + 八纲 (阴阳/表里/寒热/虚实) syndrome differentiation, (c) 治法 (汗吐下和温清消补 + 扶正祛邪) therapeutic principles, (d) 方剂学 (经方 时方 验方) formula science, (e) 中药学 (四气五味/归经/七情/炮制/配伍禁忌) materia medica, (f) 针灸学 (经络穴位/手法/灸法/电针) acupuncture+moxibustion, (g) 推拿按摩 tuina massage, (h) 中医各科 (内/外/妇/儿/骨伤/皮肤/眼/耳鼻喉/肛肠/老年/急症) clinical specialties, (i) 中西医结合 integrative medicine, (j) 循证中医 + 临床流行病学 evidence-based TCM + 现代研究, (k) 中医诊所备案 / 中医师资格 / NATCM 监管 / 药典 / GMP regulatory framework, (l) 国家级名老中医 学术继承人 项目 transmission program; NOT 道家修炼 / 风水 / 算命八字 (那是 玄学不是 中医), NOT 中医养生科普 (是 衍生 不是 临床主体), NOT 中医美容 (是 商业化分支), NOT 民族医学 (藏蒙维傣 是 平行体系 不在本 skill 主线 — 仅作 边界标注).: top builders' mental models, tool stack, current workflows, jargon, and where to keep up. Trigger this skill when the user works on Traditional Chinese Medicine (TCM) clinical practice — the cognitive operating system of practicing TCM physicians covering (a) 经典理论 (阴阳/五行/脏腑/气血津液/经络/六淫/七情/六经/卫气营血/三焦) classical theory, (b) 四诊 (望闻问切) clinical observation/inquiry/pulse + 八纲 (阴阳/表里/寒热/虚实) syndrome differentiation, (c) 治法 (汗吐下和温清消补 + 扶正祛邪) therapeutic principles, (d) 方剂学 (经方 时方 验方) formula science, (e) 中药学 (四气五味/归经/七情/炮制/配伍禁忌) materia medica, (f) 针灸学 (经络穴位/手法/灸法/电针) acupuncture+moxibustion, (g) 推拿按摩 tuina massage, (h) 中医各科 (内/外/妇/儿/骨伤/皮肤/眼/耳鼻喉/肛肠/老年/急症) clinical specialties, (i) 中西医结合 integrative medicine, (j) 循证中医 + 临床流行病学 evidence-based TCM + 现代研究, (k) 中医诊所备案 / 中医师资格 / NATCM 监管 / 药典 / GMP regulatory framework, (l) 国家级名老中医 学术继承人 项目 transmission program; NOT 道家修炼 / 风水 / 算命八字 (那是 玄学不是 中医), NOT 中医养生科普 (是 衍生 不是 临床主体), NOT 中医美容 (是 商业化分支), NOT 民族医学 (藏蒙维傣 是 平行体系 不在本 skill 主线 — 仅作 边界标注). problems and wants industry-grade thinking, tool selection, or workflow guidance. 触发词：「中医」「中医学」「中医药」「中医诊疗」「中医临床」
日本語の概要は準備中です。原文の説明を表示しています。
Software design principles, patterns, and architecture from SOLID through distributed systems. Covers the five SOLID principles with violations and fixes, DRY/KISS/YAGNI heuristics, separation of concerns, 12 GoF design patterns organized by intent (creational, structural, behavioral), architectural patterns (MVC, MVP, MVVM, layered, hexagonal, microservices, event-driven), coupling and cohesion metrics, dependency injection, and the design decision framework for choosing between competing approaches. Use when making design decisions, reviewing architecture, refactoring code, or teaching software engineering principles.
日本語の概要は準備中です。原文の説明を表示しています。
Derive a theoretical result step-by-step from first principles or established theorems, with every step explicitly justified and special cases checked. Use when deriving a formula or theorem from first principles, proving a mathematical statement by logical deduction, re-deriving a textbook result for verification or adaptation, extending a known result to a more general setting, or producing a self-contained derivation for a paper or thesis.
日本語の概要は準備中です。原文の説明を表示しています。
Knowledge skill that applies behavioral psychology and persuasion principles to any marketing asset. Covers Cialdini's 6 principles, cognitive biases, and ethical persuasion frameworks. This skill is invoked BY other skills to enhance their output. Use it whenever copy needs more psychological weight, when a landing page feels flat, when email sequences lack urgency, or when any marketing asset needs to be more persuasive. Also use when someone says 'make this more convincing', 'add urgency', 'psychological triggers', 'persuasion framework', 'behavioral psychology', 'conversion optimization', 'nudge', 'influence tactics', or 'why isn't this converting'. Make sure to use this whenever ANY marketing copy needs to be more persuasive, even if the user just says 'this feels weak' or 'how do I get more signups', psychology principles likely apply.
日本語の概要は準備中です。原文の説明を表示しています。
Foundational ethics, authority hierarchy, and structural principles for the Predicate agent. Always-on law (composable system-prompt core): Truth>Harmony, Evidence>Authority, Halt>Assumption, Outcomes>Process — four ordered principles that govern every walk. Reference (by-moment): conflict resolution, ethics adjudication, novel situations, precedence walkthrough, entropy diagnostics, principled resistance. Trigger (reference depth): resolving rule conflicts, ethics calls, novel situations. Prompt contains: constitution, principles, precedence, truth over harmony, outcomes over process, evidence over authority, principled resistance.
日本語の概要は準備中です。原文の説明を表示しています。
実装前に参照する設計原則。理解容易性 = 読み手の思考量の少なさを基準に、AI が作りがちな失敗4パターン（引数・依存5個以上、コマンド層肥大・ドメイン貧血症、ポリモーフィズム機会の見逃し、トリッキーな実装）と、実装後セルフチェックの7観点（名称・役割・参照・状態・面積・階層・秩序）を言語化。Use when starting any implementation task, when user says '設計原則', 'design principles', or before writing new entities/commands/repositories.
Strip a problem to its irreducible fundamental truths and rebuild the solution from the ground up — free from analogy, convention, and inherited assumptions. Load when the user feels constrained by how something has always been done, when existing solutions feel expensive or inefficient for no good reason, when the user asks to think from first principles, challenge the fundamentals, or rebuild this from scratch. Also triggers on "why does it have to work this way", "what are the actual constraints here", "ignore what everyone else does", or when deep-thinking diagnoses a convention-break frame. Based on Aristotle's first principles method, popularised by Musk and Feynman. Produces genuinely novel solutions by eliminating convention.
日本語の概要は準備中です。原文の説明を表示しています。
Master REST and GraphQL API design principles to build intuitive, scalable, and maintainable APIs that delight developers and stand the test of time.
日本語の概要は準備中です。原文の説明を表示しています。
Master REST and GraphQL API design principles to build intuitive, scalable, and maintainable APIs that delight developers. Use when designing new APIs, reviewing API specifications, or establishing API design standards.
日本語の概要は準備中です。原文の説明を表示しています。
Master REST and GraphQL API design principles to build intuitive, scalable, and maintainable APIs that delight developers and stand the test of time.
日本語の概要は準備中です。原文の説明を表示しています。
Physics-based reasoning framework (Musk methodology) that deconstructs a problem to irreducible fundamental truths, classifies every element as hard constraint, soft constraint, or assumption, then reconstructs the optimal solution from fundamentals alone. USE WHEN first principles, fundamental truths, challenge assumptions, real constraint, rebuild from scratch, start over, physics first, question everything, reasoning by analogy. NOT FOR structural feedback loops (use SystemsThinking).
日本語の概要は準備中です。原文の説明を表示しています。
[omh] Turn repeated lessons into written rules: extract repeated principles from skills, prompts, traces, reviews, and failures into reviewed rule candidates without auto-mutating guidance. Use when the user says: rules-distill, rules distill, distill rules, rule distillation, principle distill, skill principles, extract agent rules, turn traces into rules.
日本語の概要は準備中です。原文の説明を表示しています。
Define actionable principles that resolve trade-offs when the team disagrees. Use when the same decisions keep getting relitigated. For a single project's framing, use `design-brief`.
日本語の概要は準備中です。原文の説明を表示しています。