「only」の検索結果

Signpost (not a knowledge pack) for OMG modelling specifications — UML, SysML, BPMN, UAF, SoaML, MOF, OCL, XMI, DDS. Contains NO source content: it only points to where the official specs live and what each is for. Use when you need an OMG modelling/architecture specification — the OMG licence forbids redistributing or transforming the text, so these cannot be reconstituted into a pack; download them from OMG directly.

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

Knowledge base from DOE Systems Engineering Methodology (SEM) Version 3 — the DOE SDLC for IT investments. Use for staged systems lifecycle planning through maintenance, Stage Exits, Structured Walkthroughs, In-Stage Assessments, requirements traceability, and CMM-aligned process discipline. Covers SEM3 (2002) guidance only; does not replace modern DevSecOps tooling standards, DOE O 413.3B capital-asset directives, or current CIO policy supersessions.

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

Signpost (not a knowledge pack) for the automotive standards landscape: ISO 26262, ASPICE, SAE J3016, UNECE R155, UNECE R156, and the NHTSA vehicle set. Contains NO source content: designation, edition, owner, status, and an official catalogue URL only. Use when you need to identify or locate an automotive standard. Most are paywalled or carry no redistribution grant and cannot be packaged; the one open path is the nhtsa-vehicle pack.

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

Knowledge base from DAFMAN 63-119 (15 April 2021), Mission-Oriented Test Readiness Certification. Use for continuous MOTRC replacing single-point OTRR thinking: framework/applicability, Certification Official vs PM roles, review cycle and exit criteria, certification memo/decertify gates, DT&E/contractor evidence, ITT integration and cyber resiliency, and the 31-template matrix. DAF T&E readiness process only—does not replace DoDI 5000.89, AFI 99-103, or multi-service lead policies.

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

Signpost (not a knowledge pack) for the functional safety standards landscape: IEC 61508, ISO 26262, ISO/SAE 21434, UL 4600, SAE J3016, and ASPICE. Contains NO source content: designation, edition, owner, status, and an official catalogue URL only. Use when you need to identify or locate a functional safety standard. All six are paywalled or carry no redistribution grant and cannot be packaged; open paths point at US Government packs, which are not equivalents.

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

Knowledge base from IS-GPS-200 Rev N (NAVSTAR GPS Space Segment / Navigation User Segment Interfaces). Use as a worked ICD/IS exemplar: what an interface specification is, DIST-A and IRN/CCB change control, interface definition vs identification, composite-signal criteria patterns, NAV data as payload families, and time/definition hygiene. Covers Rev N synthesized notes only; does not transcribe Apps II–IV bit fields or PRN/Gold-code tables, and does not replace faa-std-025 preparation rules.

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

Knowledge base from OMB Circular A-94 (revised 2023-11-09) on guidelines and discount rates for benefit-cost and cost-effectiveness analysis of federal programs. Use for BCA principles, benefit/cost measurement, discount-rate policy, uncertainty/sensitivity, distributional incidence, and decision reporting. Rescoped at build to A-94 only (Army CBA Guide unreachable). Does not replace A-11 budget preparation detail, agency-specific statutory BCA rules, or Army CEAC process templates.

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

Knowledge base from MIL-HDBK-338B (Electronic Reliability Design Handbook). Use for electronic reliability engineering: R/M/A theory, reliability specification/allocation/prediction, parts management and derating, reliable circuit and fault-tolerant design, environmental and human performance reliability, FMEA/FMECA/FTA/sneak circuit analysis, design reviews and testability, FRACAS, reliability demonstration and growth testing, and systems-level R&M parameters. Covers selected Part 2 design-guidance topics only; skips large annex/part-stress tables. Guidance handbook — not a contractual requirement text. Does not replace MIL-HDBK-217 prediction libraries, service-specific reliability regs, or safety standards (see mil-std-882).

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

Knowledge base from FAA-STD-025f (Preparation of Interface Documentation). Use for IRD/ICD family definitions, common format and content, IRD shall-requirements, ICD design characteristics, verification/VRTM, and CM/revision/approval of FAA Enterprise Subsystem interfaces. Covers rev F preparation rules only; does not replace FAA-STD-005 drawing/spec prep, Order 1800.66 full CM procedures, or non-FAA interface standards.

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

Knowledge base from NASA-STD-7009B (Standard for Models and Simulations) with implementation depth from NASA-HDBK-7009B. Use for M&S criticality and programmatics, development evidence and capability assessment, verification/validation domains, uncertainty and sensitivity, use-phase results assessment, risk-informed decision reporting, and handbook life-cycle products. Covers STD-7009B (2024-03-05) + HDBK-7009B (2026-02-03) synthesized notes only; does not replace program-specific TA direction, NPR 7150.2 software requirements detail, or full PRA methodology.

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

Knowledge base from CISA Cross-Sector Cybersecurity Performance Goals 2.0. Use for prioritized IT/OT baseline cyber goals aligned to NIST CSF 2.0 (including GOVERN), critical-infrastructure hygiene, MSP/supply-chain expectations, and board-friendly outcome language. Covers CPG 2.0 goals only; does not replace full CSF programs, sector-specific goals (SSGs), or CSET tooling detail.

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

Knowledge base from MIL-STD-40051-2C (15 Dec 2015), Preparation of Digital Technical Information for Page-Based Technical Manuals. Use for TM/TDP structure, work packages, front/back matter, style/format, warnings/HAZMAT, change packages, content selection matrices, and plate exemplars. Primary Training & Documentation pack (cluster 25) with Ops & Maintenance procedure use—page-based (-2C) only, not IETM 40051-1.

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

Knowledge base from the DoD Test & Evaluation Enterprise Guidebook (August 2022 edition 8.02) with DOT&E-facing enterprise emphasis. Use for T&E enterprise roles (DOT&E vs USD(R&E)), DT&E/OT&E/LFT&E, cybersecurity T&E, MOSA/automation/digital enablers, suitability/reliability growth, and TEMP/Strategy/STE planning. Distinct routing from dod-te-guidebook (same guidebook family, pathway-deep pack). Guidance only—defer to DoDI 5000.89 and Title 10 for binding requirements.

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

Graded exposure for anxiety disorders: Fear hierarchy, SUDs scale, exposure planning and guidance. Psychoeducation only, not implementation.

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

Manages your own skill landscape: surveys and compares existing skills (Audit mode), researches the web for new skills/plugins (Explore mode), and is at the same time the installer that generates lean subskills (Skill-Finder, family umbrella, maintenance skills) instead of loading a monolith. Use this skill for "compare/audit skills", "which skills are duplicated", "form skill families", "clean up/consolidate skills", "maintain the skill register", "find skills/plugins for topic X", "install new skills", "browse the skill marketplace", or for `/skill-explorer`. Delivers a sub-report per family and a globally numbered decision list; installs/uninstalls only after a security check and explicit approval.

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

How game development works as a process — roles, subtasks, workflows and role descriptions, especially (but not only) for Roblox. Use this skill when it's about the ORGANIZATION of game dev rather than concrete code: Which roles exist (Creative Director, Engineer, Artist, Polish/Audio, Business, QA-Tester, Game Critic)? Who does which subtask? What does a development chain (concept → backend → frontend → polish → test) look like? How do you write a Game Design Document / KONZEPT.md? How do several (AI) agents divide up a game? Also trigger on "plan a new game", "create Game Design Document", "which roles do I need for my game", "development workflow for a game", "who tests the game", "structure a game idea", "Roblox genre/monetization".

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

Flexible Bedingungssprache für Ziele, Prompts und Aufträge. Übersetzt Bedingungen, Zeitpunkte und Reihenfolge-Abhängigkeiten in prüfbare Gates, damit ein Teilschritt erst nach belegter Freigabe ausgeführt wird. Immer verwenden bei /condition, /if, /if-only, /when, /after, /and oder /or sowie bei Formulierungen wie "erst wenn", "sobald", "nur falls", "nachdem", "warte bis", "danach" oder "vorher nicht". Auch verwenden, wenn mehrere Teilziele voneinander abhängen oder ein Goal eine spätere Freigabe enthält.

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

Generic plugin system for Python applications. Auto-discovery, validation, fault tolerance. Zero dependencies (Python stdlib only).

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

Use when the user wants to send the same prompt to several LLMs and compare the answers - sequentially (stopwatch, clean per-lane timing) or in parallel (true race), with optional repetitions per model, judged by the starting model across quality, correctness, completeness, instruction fidelity and latency (time is only one dimension). Triggers on /compare-race, 'model race', 'vergleiche modelle', 'gleicher prompt an mehrere modelle'.

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

Hosting-Muster, um eine lokal gebaute Anwendung (eigene Datenbank, eigener API-Key, In-Process-State) sicher hostbar zu machen, ohne Nutzerverwaltung zu bauen. Kernzug — der Host speichert nichts, der Browser des Besuchers speichert alles — sodass Pro-Besucher-Accounts, Zugriffsprüfungen und Löschfristen gegenstandslos werden, statt gelöst werden zu müssen. Nutzen, wenn eine lokal gebaute App für mehrere Besucher gehostet werden soll, bei "mach das ohne Login hostbar", "keine Nutzerkonten bauen", "Datenschutzerklärung für ein gehostetes Tool verkleinern", "wer ist verantwortlich, wenn wir nichts speichern" oder beim Wählen/Implementieren eines Server-Modus (`local`, `huckepack-gift`, `huckepack-only-host`, `pay-membership`). Liefert eine Data-Flow-Plan-Vorlage, eine Datenschutz-Vorlage und eine rechtliche Ersteinschätzung (DSGVO/TDDDG/UWG, deutsch) als Referenzen.

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

Automated software development pipeline. Scans projects, prioritizes tasks, analyzes code, and orchestrates development loops. Zero dependencies (Python stdlib only).

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

Turns sustainability or ESG reports the user provides into a DRAFT question pack for reviewers: every quantitative disclosure as stated with unit, period, boundary and page, year-over-year changes computed only from the stated figures with the arithmetic shown, targets with stated and computed progress, restatements and inconsistencies, gaps and specific questions to the report owner. No assurance, accuracy or conformance verdict. Use when the user asks to "prepare review questions on our sustainability report", "what changed year on year in this ESG report", "check the figures in this report before it goes to the board", "find the gaps in this ESG disclosure" or "build a question pack for the report owner". Do not use for reviewing marketing text against environmental-claim rules, use green-claims-review instead. Drafts for human review; never approves, authorises or signs off.

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

Turns a list of merged changes, closed work items or commit messages the user provides into DRAFT release notes under the version heading and date the user supplies, grouped as features, fixes and other, in the organisation's tone from the style guide or prior notes given, with every entry traced to its source item, breaking changes and required actions flagged first, and internal-only items held back for the release owner to confirm. Use when the user asks to "write the release notes for this version", "turn these merged pull requests into a changelog", "summarise what shipped this sprint for customers", "draft the what's new for this release" or "group these closed tickets into release notes". Do not use for an announcement email or intranet post about a launch, use announcement-drafter instead; for a change ticket, use change-request-pack; for a how-to article about one fix, use knowledge-article-drafter. Drafts for human review; never approves, authorises or signs off.

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

Prepares a DRAFT vendor risk screening brief from the material the user provides on one vendor (questionnaire answers, certificates, assurance reports, policies, contract extracts): per screening topic, what a document evidences with reference, date and scope, what is only asserted, what is missing or contradicted, certificate and report details as stated, and ready-to-send questions for the vendor and the internal owners. No web research, no risk rating, tier, score or recommendation. Use when the user asks to "screen this vendor", "review the vendor's questionnaire answers", "check what the vendor's certificate covers", "what is missing from this due diligence pack" or "draft the follow-up questions for the vendor". Do not use for answering a customer's questionnaire about your own organisation, use vendor-security-questionnaire-prefill instead. Drafts for human review; never approves, authorises or signs off.

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