「diagram」の検索結果

[OPTIONAL] AI-powered visual generation using Google Nano Banana Pro. For user flows, architecture diagrams, mockups.

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

図解1枚で何をどの順に決めるか引きたいとき、図種選定・コネクタ入射・日本語ラベル・素材レイヤ検査の根拠を参照したいときに使う。

Use for documents, reports, memos, guides, academic papers, or formal text that needs clear structure, reliable tone, formatting, and diagrams.

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

Use when creating, revising, or critiquing a chart, dashboard, or KPI display that makes a quantitative comparison someone will act on. Covers honest comparison and rendered checks; leave palette, marks, and library mechanics to the medium's own skill. Skip decorative graphics and diagrams with no data.

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

Redesign GitHub README homepages or create project-native pure SVG, hybrid SVG-composed PNG/WebP, and opt-in animated GIF assets. Use when a user asks to beautify, redesign, rebrand, visually upgrade, simplify, or audit a GitHub README; create only a hero, section headers, diagrams, badges, motion graphics, showcase modules, or other README assets; or turn a repository homepage into a cohesive visual story. If whole-README work versus asset-only work is unclear, ask which scope the user wants. For hero-like assets where pure SVG and generated raster material are both viable, explain the tradeoffs and confirm the implementation before creating the asset.

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

This skill should be used when creating comprehensive project plans for system development or implementation projects. Use this skill when you need to create Project Charters, Project Plans, WBS, Gantt Charts, RACI matrices, Risk analysis, or other PMBOK-aligned project management artifacts. Outputs are in Markdown format with Mermaid diagrams for visualizations. Leverages comprehensive PM knowledge base in references/ directory (544KB, 11 files) including PMBOK standards, Software/SaaS best practices, IT industry guidance, and specialized PM methodologies.

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

Comprehensive Lean Six Sigma consulting skill supporting all belt levels (White Belt to Master Black Belt). Use this skill for DMAIC/DMADV project execution, Lean waste elimination (VSM, 8 Wastes/DOWNTIME, 5S), statistical analysis (process capability Cp/Cpk, control charts, hypothesis testing), and Six Sigma training/education. Triggers include "improve process", "reduce defects", "sigma level", "DMAIC project", "value stream mapping", "Kaizen", "process capability", "control chart", "root cause analysis", "5 Whys", "Fishbone diagram", "FMEA", "DOE", or requests involving process improvement methodologies.

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

因果関係ループ図の良い点・悪い点を分析し、改善点と改善のための問いを生成

検証結果に基づいて因果関係ループ図を洗練・修正する

因果関係ループ図を作る時の観点を説明する

因果関係ループ図の作成を実行

技術図・概念図・比較図・データ図の情報設計、生成、掲載サイズでの画像レビュー、修正を行う。図解・構成図の作成、図の可読性改善、既存図のレビューに使う。UI画面設計や装飾イラストは対象外。

Build a rich, self-contained HTML explanation of a code change — diff, branch, commit range, MR/PR — with background, intuition, a code walkthrough, diagrams, and a glossary, then quiz the reader interactively in chat. Use when the user asks to explain a change, understand a PR/MR, walk through a diff, onboard onto a branch, or says "explain this PR", "what does this branch do", "teach me this change", or "/explain-diff".

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

Load when creating, editing, or debugging Lottie/Bodymovin JSON for the local Skia Skottie player: logo/type/SVG animation, loaders, icons, UI microinteractions, lower thirds, charts, diagrams, scene motion, effects, slots, or controls; not for static raster/SVG, CSS-only motion, or video editing.

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

Knowledge base from the NASA Systems Modeling Handbook for Systems Engineering (NASA-HDBK-1009A Rev A, 2025). Use for model-based systems engineering (MBSE) wired into NASA's NPR 7123.1 SE processes: the three aspects of MBSE (language / methodology / framework), the NASA SE Engine and its two OOSEM-derived steps (Model Planning, Setting Up the Model), the Modeling Plan as a SEMP subset, the tool-agnostic NASA SE metamodel of elements and relationships across the four SysML pillars (structure / behavior / requirements / parametrics), worked SysML diagrams and tables for stakeholders, requirements, structure and V&V, generating SE work products (ConOps, MOE, MOP, TPM, V&V), the MBSE Grid framework, alternative modeling approaches (PBR, Scenario, System Specification, Verification), and the ConOps model-content template. Scope is bounded to four common technical processes (Stakeholder Expectation Definition, Technical Requirements Definition, Product Verification, Product Validation). Does NOT teach SysML itself, mandate a tool, define NPR 7123.1 processes, cover technical-management processes 10-17, or reproduce the OMG SysML specification.

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

Knowledge base from NASA Risk Management Handbook (NASA/SP-2011-3422). Use for risk-informed decision making, continuous risk management, performance commitments, risk scenario diagrams, risk disposition types, risk burn-down schedules, objectives hierarchies, deliberation and alternative selection, risk driver identification, and RM planning for space and safety-critical programmes. Does not cover domain-specific PRA methods (fault trees, event trees) in procedural depth — see NASA PRA Procedures Guide for those.

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

Knowledge base from the FAA Requirements Engineering Management Handbook (DOT/FAA/AR-08/32). Use for writing requirements for real-time, embedded control systems — the avionics/medical slant — via the Handbook's eleven recommended practices: system overview and boundary (monitored/controlled variables), operational concepts (use cases), environmental assumptions, change-tolerant functional architecture (dependency diagrams), safety-driven architecture revision (FHA/PSSA/fault tree), system modes, detailed behavior and performance requirements (ideal value + tolerance + latency), the four-variable model bridge to software requirements (MON/CON/NAT/REQ, IN'/REQ'/OUT', DO-178B mapping), subsystem allocation, and rationale. Carries the Isolette Thermostat and Flight Control System worked examples. Slanted toward control systems with sensors and actuators; thin on information-system / enterprise / agile requirements, on requirements-management tooling, and on the formal-methods internals of SCR/RSML/SpecTRM (it names them, does not re-teach them). Does not reproduce the IEEE/DO-178B/ARP standards it cites.

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

Reads a process flow diagram (image, PDF or native export) with its job header and returns a provenance-tagged extraction register: equipment, streams, tags, connectivity, instruments already shown, notes and legends, connectivity findings and an explicit UNKNOWN list, then holds at gate G1. Extracts and records only; never enriches, tags or proposes. Use when the user asks to "start a PFD to P&ID job", "read in the attached PFD", "extract the equipment and streams from this PFD" or "read this PFD into a register". Do not use for checking the model, use process-model-check instead; do not use to propose lines, instruments or tags, use piping-enrichment or instrumentation-and-control-enrichment after gate G2. Drafts for human review; never approves, authorises or signs off.

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

Drafts an architecture or design decision record (ADR) from the discussion notes, design review minutes, chat threads and diagram descriptions the user provides: context, decision drivers, options considered with arguments as stated, the decision as the group worded it, consequences and a review date, with every factual claim tagged evidenced, asserted or UNKNOWN so unsupported claims are marked for the author to substantiate. Use when the user asks to "write an ADR", "document the architecture decision", "record why we chose this design", "turn these design review notes into a decision record" or "draft the design decision log entry". Do not use for a business or governance decision with no technical design, use decision-memo-builder instead; for the change ticket that implements the decision, use change-request-pack. Drafts for human review; never approves, authorises or signs off.

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

画面遷移図の新規作成・更新を支援する。画面一覧の SCR-* を利用者ごとの Mermaid 図でつなぎ、画面間の遷移を表す D2 成果物。画面一覧の策定後に呼び出す。

You are a code education expert specializing in explaining complex code through clear narratives, visual diagrams, and step-by-step breakdowns. Transform difficult concepts into understandable expl...

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

You are a documentation expert specializing in creating comprehensive, maintainable documentation from code. Generate API docs, architecture diagrams, user guides, and technical references using AI...

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

Creating interactive data visualisations using d3.js. This skill should be used when creating custom charts, graphs, network diagrams, geographic visualisations, or any complex SVG-based data visua...

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

Expert C4 Context-level documentation specialist. Creates high-level system context diagrams, documents personas, user journeys, system features, and external dependencies.

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