「how to」の検索結果

Elite mobile app image-generation skill for creating premium, app-native screen concepts and flows. Designed for iOS, Android, and cross-platform mobile products. Prioritizes clean hierarchy, comfortably readable text, strong multi-screen consistency, controlled color palettes, non-generic creative direction, textured surfaces, image-led composition, tasteful custom iconography, and clean phone mockup framing. By default, screens should be shown inside a subtle premium iPhone or similar phone mockup with a visible frame, while the main focus stays on the app content itself. This skill generates images only. It does not write code.

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

Reconstruct workflow behind a past coding-agent artifact using local ax sessions/commits/skills/tool traces. Use when asked how X was built.

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

Guidance for instrumenting webapps with Azure Application Insights. Provides telemetry patterns, SDK setup, and configuration references. WHEN: how to instrument app, App Insights SDK, telemetry patterns, what is App Insights, Application Insights guidance, instrumentation examples, APM best prac...

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

Guidance for instrumenting webapps with Azure Application Insights. Provides telemetry patterns, SDK setup, and configuration references. USE FOR: how to instrument app, App Insights SDK, telemetry patterns, what is App Insights, Application Insights guidance, instrumentation examples, APM...

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

When the user wants to set up, improve, or audit analytics tracking and measurement. Also use when the user mentions "set up tracking," "GA4," "Google Analytics," "conversion tracking," "event tracking," "UTM parameters," "tag manager," "GTM," "analytics implementation," "tracking plan," "how do ...

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

When the user wants to set up, improve, or audit analytics tracking and measurement. Also use when the user mentions "set up tracking," "GA4," "Google Analytics," "conversion tracking," "event tracking," "UTM parameters," "tag manager," "GTM," "analytics implementation," "tracking plan," "how do...

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

Conduct a defensible cybersecurity risk assessment using the NIST SP 800-30 Rev 1 methodology: prepare scope and a risk model, identify threat sources and threat events, identify vulnerabilities and predisposing conditions, determine likelihood and impact, compute risk, and communicate results as a prioritized risk register. Use when an organization needs an actual risk *assessment* (not a maturity score), when a control framework (CSF, ISO 27001, RMF, SOC 2, PCI) requires a documented risk analysis as input, when leadership asks "what are our top risks and how bad are they", when assessing risk for a new system or major change, or when building a risk register from scratch. This is the methodology that feeds framework selection, ATO packages, and treatment decisions. Keywords: risk assessment, NIST 800-30, threat modeling, likelihood and impact, risk register, risk analysis, threat sources, vulnerabilities, risk determination, qualitative risk, risk matrix, residual risk, risk treatment.

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

Workshop how to break this card into smaller spawned cards and capture entries in the card breakdown

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

执行显式、编码前的 Product Discovery，把早期或模糊的软件想法转化为用户确认的 Intent、丰富方案卡片、对比矩阵、可编辑画布和可持续 D0 文档基线。仅当用户明确调用 $flight-brainstorm，准备在 Flight Control Run 之前探索空白、稀疏、不确定或方向发生重大变化的项目时使用；禁止因模糊请求或普通开发工作隐式触发。

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

Cross-reference project artifacts (WBS, meeting minutes, requirements docs) by date, participant, and action items. Extract commitments from meeting minutes and link to WBS tasks. Generate traceability reports showing which decisions were captured in which documents.

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

Write, validate, and (optionally) execute an NQL query against a Narrative dataset. Drafts the query from the user's question, runs `narrative_nql_validate` until it compiles, explains the query in plain English, and only runs it on explicit approval (or when invoked with `--run`). Use when: "write an NQL query for X", "query this dataset", "validate this NQL", "run NQL against dataset <id>", "how many rows match Y", "show me the top N records from <dataset>". (narrative-common)

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

Load when asked where code lives, how modules relate, what calls a symbol, what implements a feature, or for an architecture/codebase tour using the knowledge graph; not for bug diagnosis, diff review, or refactoring.

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

Explain a body of work plainly so a person actually understands it. Runs the `how` and `why` skills and weaves what they find into one clear explanation. Use for 'teach me this', 'help me really understand X', 'explain this change or subsystem to me'.

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

Scores inbound leads against the qualification rubric the user supplies (criteria, scale, weights, thresholds and disqualifiers as given): one DRAFT scorecard per lead with the evidence quoted per criterion, UNKNOWN wherever the lead's information is missing, totals shown with and without the UNKNOWN criteria, a ranked list and a suggested next step such as a qualification call, a request for missing details, nurture or a courteous decline. Use when the user asks to "score these inbound leads", "qualify this lead against our rubric", "run the web form submissions through our lead criteria", "which of these leads should sales call first" or "build a lead scorecard". Do not use for preparing the first call with a lead, use discovery-call-prep instead; for an existing account's growth plan use account-plan-builder. Drafts for human review; never approves, authorises or signs off.

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

Builds a DRAFT quiz from the training content the user supplies (slide deck, manual, e-learning script, session transcript, procedure): numbered questions with the correct answer, distractors drawn from the content itself, an explanation quoting the source passage with its location, a difficulty tag (Recall, Apply, Analyse) with its basis, and a coverage table showing which sections and objectives each question tests and which are left uncovered. Use when the user asks to "build a quiz from this deck", "write knowledge check questions for this module", "create an assessment from this training", "test understanding of this procedure" or "which sections does this quiz cover". Do not use for a reader-facing question and answer page built from documents, use faq-builder instead; for writing the procedure itself from notes or a walkthrough, use sop-drafter. Drafts for human review; never approves, authorises or signs off.

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

Reads a contract list (spreadsheet, CSV or pasted table) and returns a DRAFT renewal radar: each active contract's end date, notice deadline with its arithmetic, days remaining, renewal type, owner and the decision it needs as options, sorted by urgency, with owner action lists and a deadline calendar. Never renews, terminates, serves notice or recommends. Use when the user asks to "build a renewal tracker", "tell me what comes up for renewal", "work out when notice is due", "show me which contracts auto-renew" or "run the quarterly contract review". Do not use for reviewing one contract's full text or clauses, use contract-review-pack instead. Drafts for human review; never approves, authorises or signs off.

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

Builds a DRAFT course outline from a training need and audience: learning objectives with an observable verb, condition and standard, modules in a stated order with a duration basis and sources, activities and an assessment plan aligned objective by objective, and a coverage table showing what each objective still lacks. Never sets a pass mark, declares learners competent or invents content. Use when the user asks to "build a course outline", "design a training programme for", "turn this need into modules and objectives", "draft the curriculum for this workshop" or "what should this training cover". Do not use for quiz items from finished content, use training-quiz-builder instead; for needs from surveys and manager notes, use training-needs-synthesis; for a new starter's first weeks, use onboarding-plan-builder. Drafts for human review; never approves, authorises or signs off.

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

Turns a list of KPIs or metrics into a DRAFT definition sheet: one row per KPI with the name as stated, formula quoted from a source, source system, owner, refresh cadence, unit, filters and known caveats, with UNKNOWN in every cell no source fills and a gap list grouped by data owner. Never composes a formula, sets a target or names an owner the sources do not state. Use when the user asks to "define these KPIs", "build a metrics definition sheet", "document how each KPI is calculated", "which of our KPIs have no owner or formula" or "reconcile the two KPI lists". Do not use for the weekly numbers report, use kpi-weekly-report-writer instead; for field-level definitions of a table, use data-dictionary-builder; for logging a wrong figure as a defect, use data-quality-issue-log. Drafts for human review; never approves, authorises or signs off.

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

Report this machine's file-synchronization state with the whole fleet: peers connected, per-share state and files still needed, folder errors, and how many sync-conflict files piled up, which is the silent sign two machines are fighting over a file. Read-only and zero tokens. Triggers: "/sync-check", "is sync alive", "sync status".

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

Read this machine's cross-machine mailbox, the messages another computer's agent left here over a file-synced bus folder, and send messages back the same way. A session-start hook shows new mail automatically; this is the on-demand mid-session re-check. Triggers: "/inbox", "check inbox", "messages from the other machine".

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

Answer 'what happened on that day' instantly from a daily ledger that night robots assemble from free traces (git commits, session logs, vault writes, bus messages), with zero LLM tokens spent on retrieval. Use when asked what was done yesterday, on a given date or during a week. Triggers: /ledger, what did we do yesterday, what happened on <date>, show the day, daily summary.

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

- Build an entity-relationship link-analysis graph of an investigation — nodes, typed edges carrying source and confidence, aliases, and temporal validity — to expose shared infrastructure, bridging nodes and the real principal behind a [человек]. Use when an investigation has outgrown a list and needs a graph, or when asked how a set of people, companies and domains connect

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

Show what the background agents across every machine are doing right now, what they have built or committed, and whether anything is stuck or burning tokens. Read-only diagnostic. Triggers: "/fleet", "what are my agents doing", "is anything stuck".

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

Rebuild the canon mirror for a second coding agent (AGENTS.md) after a rules-file version bump: show the changelog delta, write in only the new rules, then enforce the size cap, version stamp, structural anchors, a copy into the shared folder and the linter run. Triggers: "/codex-mirror", "update the codex mirror", "AGENTS.md is stale".

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