「software」の検索結果

Expert CIS Controls v8 (CIS Top 18) advisor — implementation group scoping (IG1/IG2/IG3), control gap assessments, safeguard-level guidance, asset inventory, software inventory, data protection, secure configuration, account management, access control, continuous vulnerability management, audit log management, email and web browser protections, malware defenses, network infrastructure management, network monitoring and defense, application software security, incident response, penetration testing, and CIS Controls mapping to NIST CSF, ISO 27001, SOC 2, and CMMC. Use for any question about CIS Controls, CIS Benchmarks, Implementation Groups, or prioritized cyber hygiene for any organization size.

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

Use Ontoly's deterministic Software Graph and MCP capabilities for repository architecture, request tracing, dependency analysis, configuration lookup, and impact analysis before falling back to source search.

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

Automatically generate production-ready Skills for any software, API, CLI tool, library, workflow, or service. Use this skill whenever the user wants to create a skill from scratch for a target application, convert an existing tool into an agent-native skill, generate skills for multiple platforms (Claude Code, OpenClaw, Codex), or automate the full skill creation pipeline including analysis, design, implementation, testing, optimization, and multi-platform packaging. Also use when the user mentions "skill-anything", "generate a skill for", "make a skill from", "skillify", or wants to turn any software into an agent-ready skill. Even if they just say "create a skill for X" where X is any tool or API, this skill should trigger.

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

Complete Product Owner / Product Manager capability — a wiki-style knowledge map of product practice in active software development: the role and its boundaries, strategy cascade (vision → OKRs → roadmap → backlog), continuous discovery, backlog craft (epics, INVEST stories, acceptance criteria), prioritization frameworks (RICE, MoSCoW, Kano, WSJF), sprint delivery, metrics (North Star, AARRR), stakeholder management, and anti-patterns. The PO/PM owns what gets built, in what order, and why — including the end-to-end user flows and user journeys. Use when scoping a product or feature, decomposing an idea into outcomes/epics/stories, prioritizing a backlog, defining an MVP, mapping user journeys, measuring success, or saying no to a stakeholder. Pairs with super-ui-ux-design, which owns how each screen looks and behaves.

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

Transform an AI agent into a disciplined software development partner with strong judgment, transparent decisions, proportionate verification, and craftsmanship. Use for software implementation, feature work, bug fixing, refactoring, optimization, migrations, and sustained collaboration inside a codebase. Do not use merely because a task involves an AI agent; use a dedicated agent-design skill when the primary problem is agent architecture.

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

Scores shortlisted accounting packages against 57 evidence-backed fields, emitted as CSV, SQL, JSON Schema or Notion on request. Use for choosing accounting software.

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

Identifies bug-introducing commits using SZZ-style analysis based on bug-fixing commits, commit history, and code blame information. Use this skill when you need to trace bugs back to their origin, identify which commits introduced bugs, analyze bug-fix commits to find root causes, perform software repository mining for bug analysis, or conduct empirical studies on software defects. Triggers when users ask to find bug-introducing commits, identify when a bug was introduced, trace bug origins, perform SZZ analysis, or analyze bug-fixing commits.

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

Recommends appropriate software design patterns based on problem descriptions, requirements, or code scenarios. Use when designing software architecture, refactoring code, solving common design problems, or choosing between design approaches. Analyzes the problem context and suggests suitable creational, structural, behavioral, architectural, or concurrency patterns with implementation guidance and trade-off analysis.

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

Detects and analyzes ambiguous language in software requirements and user stories. Use when reviewing requirements documents, user stories, specifications, or any software requirement text to identify vague quantifiers, unclear scope, undefined terms, missing edge cases, subjective language, and incomplete specifications. Provides detailed analysis with clarifying questions and suggested improvements.

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

Identifies boundaries between modules or components in software systems through static code analysis and dependency detection. Use when Claude needs to analyze software architecture, identify module boundaries, detect boundary violations, find circular dependencies, or assess component coupling. Supports Python (packages and imports) and Java (packages and dependencies). Trigger when users ask to "identify boundaries", "find component boundaries", "detect boundary violations", "analyze module structure", "check architecture", or "find circular dependencies".

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

Evaluate architecture and module boundaries for volatility-based decomposition using Juval Lowy's framework (from "Righting Software", building on Parnas 1972). Use when reviewing module splits, service boundaries, new abstractions, or any decomposition decision. Trigger on phrases like "where should this boundary be", "how to split this", "module boundaries", "encapsulate change", "volatility", or references to Lowy, Parnas, or "Righting Software". Complements /hickey (interleaved concerns) with a different lens (change encapsulation).

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

Scan project dependencies for known vulnerabilities, generate software bills of materials, and enforce license compliance across the software supply chain. Use when the user requests dependency scanning or provides relevant inputs for this workflow.

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

Provider-independent workflow for producing SaaS and software product demo videos, including app walkthroughs, feature launches, sales demos, onboarding clips, help-center explainers, website hero demos, and PLG assets. Use when an agent must plan, script, capture, synthesize, edit, localize, review, or QA privacy-safe software demo videos with substantiated claims, accessible captions, screen/cursor direction, CTA variants, and stakeholder approval.

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

AI code reviewer grounded in classic software engineering books for catching design smells, coupling issues, and architectural risks.

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

architect-review workflow skill. Use this skill when the user needs Master software architect specializing in modern architecture and the operator should preserve the upstream workflow, copied support files, and provenance before merging or handing off.

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

@arm-cortex-expert workflow skill. Use this skill when the user needs Senior embedded software engineer specializing in firmware and driver development for ARM Cortex-M microcontrollers (Teensy, STM32, nRF52, SAMD) and the operator should preserve the upstream workflow, copied support files, and provenance before merging or handing off.

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

architect-review workflow skill. Use this skill when the user needs Master software architect specializing in modern architecture and the operator should preserve the upstream workflow, copied support files, and provenance before merging or handing off.

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

@arm-cortex-expert workflow skill. Use this skill when the user needs Senior embedded software engineer specializing in firmware and driver development for ARM Cortex-M microcontrollers (Teensy, STM32, nRF52, SAMD) and the operator should preserve the upstream workflow, copied support files, and provenance before merging or handing off.

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

Apify Actorization workflow skill. Use this skill when the user needs Actorization converts existing software into reusable serverless applications compatible with the Apify platform. Actors are programs packaged as Docker images that accept well-defined JSON input, perform an action, and optionally produce structured JSON output and the operator should preserve the upstream workflow, copied support files, and provenance before merging or handing off.

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

Apify Actorization workflow skill. Use this skill when the user needs Actorization converts existing software into reusable serverless applications compatible with the Apify platform. Actors are programs packaged as Docker images that accept well-defined JSON input, perform an action, and optionally produce structured JSON output 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 the mental models of Bill Gates, co-founder of Microsoft and philanthropist. Use this skill whenever you are evaluating climate change solutions, global health interventions, philanthropic resource allocation, software platform economics, or the paradigm-shifting impacts of AI. Trigger this skill when the user is facing decisions about maximizing ROI on charitable giving, assessing clean energy technologies (like calculating the "Green Premium"), building winner-take-all software ecosystems, or using data to drive large-scale institutional progress. Channel his "impatient optimism" to prioritize innovation that multiplies by zero rather than settling for incremental efficiency.

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

Applies the reasoning style of Judy Faulkner, founder and CEO of Epic Systems, to decisions around corporate governance, healthcare technology, and unconventional leadership. Use this skill whenever Claude is asked for advice on going public vs. staying private, M&A strategy (acquisitions), budgeting, reducing software-driven burnout, data privacy, or interoperability. Faulkner's thinking is highly independent, fiercely protective of long-term mission over short-term profits, and deeply skeptical of traditional corporate playbooks (like MBAs, strict budgets, and venture capital). Trigger this skill to channel her focus on organic growth, customer empathy, and treating software as 'mental clay'.

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

Designs runtime topology in a chosen solution. Use when choosing monolith vs services, cells, consistency, ADRs. Not for cross-system design (software-solution-architecture).

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