1.5万 件 ・ 関連度順
概要と使いどころ
Load when orchestrating Multi-Agent Debate (MAD), adversarial code reviews, or pull-request deliberation to enforce Response Anonymization, expert persona assignment, and weighted post-hoc voting.
日本語の概要は準備中です。原文の説明を表示しています。
Load when configuring GitBook documentation sites, authoring GitBook-flavored markdown pages and custom blocks, integrating OpenAPI/Swagger specs, driving GitBook Change Request workflows (create, review, comment, resolve), or building GitBook platform integrations. Do not use for general repository code reviews, general .NET OpenAPI schema generation, or non-GitBook markdown.
日本語の概要は準備中です。原文の説明を表示しています。
Load for native CQS commands, queries, immutable request/result contracts, handlers (ICommandHandler, IQueryHandler), validators, cache invalidation, idempotency, or specification-driven reads in Explore.Application; not for controller-only or repository-only edits.
日本語の概要は準備中です。原文の説明を表示しています。
Resolve App Store Connect IDs (apps, builds, versions, groups, testers) from human-friendly names using asc. Use when commands require IDs.
日本語の概要は準備中です。原文の説明を表示しています。
Collapse meaningful ambiguity with contrastive examples. Use when a plan/design has several plausible meanings, requirements feel vague, examples would clarify intent faster than grilling, or the user asks to disambiguate, find ambiguity, use behavioral kernels, or ask contrastive questions.
日本語の概要は準備中です。原文の説明を表示しています。
Plan a refactor as a sequence of tiny safe commits via interview and codebase exploration. Use when restructuring working code, or when the user says 'plan a refactor'.
日本語の概要は準備中です。原文の説明を表示しています。
Non-streaming and streaming SSR, RouterClient/RouterServer, renderRouterToString/renderRouterToStream, createRequestHandler, defaultRenderHandler/defaultStreamHandler, HeadContent/Scripts components, head route option (meta/links/styles/scripts), ScriptOnce, automatic loader dehydration/hydration, memory history on server, data serialization, document head management.
日本語の概要は準備中です。原文の説明を表示しています。
Chrome DevTools CLI for browser automation via shell commands. Use when interacting with web pages from the command line — navigating, clicking, filling forms, inspecting console/network, taking screenshots, or extracting page content. Triggers on: browse a page, automate Chrome, inspect console, check network requests, take a screenshot, fill a form, click a button.
日本語の概要は準備中です。原文の説明を表示しています。
Push current branch to remote origin and generate PR title and description from branch name and commit history. Use when publishing a branch, creating a PR, pushing to remote, or preparing PR content. Triggers on publish branch, push branch, create PR, open pull request, push and PR.
日本語の概要は準備中です。原文の説明を表示しています。
Build a music-led video sequence by planning beats, creating or accepting an audio track, animating ordered visuals, and assembling a reviewable draft.
日本語の概要は準備中です。原文の説明を表示しています。
Select a current video model and endpoint against duration, references, motion, audio, ratio, quality, cost, and continuity requirements using live schemas.
日本語の概要は準備中です。原文の説明を表示しています。
Knowledge base from the NIST Framework for Cyber-Physical Systems (SP 1500-201/202/203, v1.0, 2017). Use for engineering and analyzing cyber-physical systems (CPS) and IoT: the CPS Framework's aspect × facet grid (nine aspects of concern examined through conceptualization, realization, and assurance facets), cross-property trustworthiness risk management (safety/security/privacy/reliability/resilience together), data interoperability (syntactical/semantic/contextual, canonical models, identifiers, provenance), the timing aspect (time-interval classes, time domains, time-aware networking) and secure/resilient time (GNSS jamming/spoofing, PTP/NTP attacks, holdover, the clock-error model and Allan/MTIE metrics), plus the use-case requirements method. Bridges IT and OT under a clock. Scope limits: a 2017 living/draft document, thin on post-2017 standards and on detailed control catalogs; it names but does not reproduce ISO/IEC/IEEE 42010 and 15288 process text or permission-licensed third-party figures.
日本語の概要は準備中です。原文の説明を表示しています。
Knowledge base synthesized from the Guide to the Systems Engineering Body of Knowledge (SEBoK) v2.14 by the BKCASE Project. Use for the established systems-engineering canon: SE fundamentals and foundations (systems science, systems thinking, the systems approach, modelling/MBSE), the life cycle (ISO/IEC/IEEE 15288/24748/24774 process, development & agile approaches, model selection/tailoring), technical management, concept definition, architecture/realization (the Vee), V&V, maintenance/sustainment, SE standards, and the application contexts (product, service, enterprise, systems-of-systems, healthcare), plus enabling SE (business/team/individual), related disciplines, quality attributes/specialty engineering, implementation examples, and emerging knowledge. Good for grounding background, vocabulary, and prior-art positions across all eight SEBoK Parts. SCOPE LIMITS: this pack is SEBoK v2.14 only (released 2026-05-18); it synthesizes and signposts rather than reproducing the source — it does not reproduce ISO/IEC/IEEE standard text, is a curated guide (not a complete textbook), and is thin on AI-integration depth (Part 8 is a staging area, not settled practice). LICENCE: content is CC BY-NC-SA 3.0 — non-commercial use only, attribution to the BKCASE Project required, share-alike obligations carry forward.
日本語の概要は準備中です。原文の説明を表示しています。
Knowledge base from the NIST/SEMATECH e-Handbook of Statistical Methods (NIST HB 151) — the practical statistics reference for engineering, metrology, and quality. Use for: exploratory data analysis and the four univariate assumptions (4-plot); measurement process characterization including bias/precision, calibration designs, gauge R&R, and ISO/GUM uncertainty budgets; production process characterization (stability vs. capability); process modeling and regression (LS/WLS/NLS/LOESS); design of experiments (screening, fractional/factorial, response-surface, Taguchi); statistical process control (Shewhart/CUSUM/EWMA charts, capability indices, acceptance sampling); product/process comparisons (hypothesis tests and confidence intervals for 1/2/3+ groups, ANOVA, multiple comparisons); and reliability (lifetime & repair-rate models, accelerated testing, reliability growth). Scope limits: this is applied frequentist statistics for measurement and quality — it does NOT reproduce the per-distribution formula galleries, worked case studies, datasets, plot images, or Dataplot/R code of the original web Handbook (those are described, not copied); it is thin on modern machine learning, Bayesian methods beyond conjugate reliability priors, time-series/forecasting, and Bayesian experimental design.
日本語の概要は準備中です。原文の説明を表示しています。
Synthesized reference notes from three US Government vehicle-safety sources: NHTSA Cybersecurity Best Practices for the Safety of Modern Vehicles (updated 2022, final), NHTSA Automated Driving Systems 2.0: A Vision for Safety (2017), and a 16-section selection of 49 CFR Part 571 (FMVSS) pinned at eCFR versioner date 2025-01-01. Use for voluntary vehicle cybersecurity practices, the ADS 2.0 twelve priority safety design elements, and FMVSS occupant protection, brakes/stability/lighting, and fuel/EV integrity requirements. Not ISO 26262, not ASPICE, not ISO/SAE 21434, not UNECE R155/R156, not SAE J3016, and not the full Part 571; the FMVSS material is a selection of vehicle-level minimum performance standards, not a process standard.
日本語の概要は準備中です。原文の説明を表示しています。
Knowledge base from NIST SP 800-37 Revision 2, the Risk Management Framework (RMF) for information systems and organizations. Use for the seven RMF steps (Prepare, Categorize, Select, Implement, Assess, Authorize, Monitor) and their tasks; the three-tier organization-wide risk model; authorization boundaries; the requirements-to-controls relationship; security categorization (FIPS 199/200 high-water mark) and control selection/tailoring (SP 800-53/53B baselines); assessment, the authorization decision and risk acceptance, continuous monitoring and ongoing authorization; the security/privacy distinction; and supply chain risk management. This is the security-and-privacy-risk-governance edge of systems engineering — it governs how much protection and whether to accept residual risk, complementing the disciplines that decide how protection is built. Does NOT reproduce the SP 800-53 control catalog or its baselines, the FIPS impact tables, or the ISO/IEC/IEEE 15288 process text; it names and routes to them rather than restating them.
日本語の概要は準備中です。原文の説明を表示しています。
Knowledge base from the FAA Systems Engineering Manual (SEM) v1.0.1. Use for civil-agency systems engineering as the FAA practices it inside the Acquisition Management System (AMS) and the National Airspace System (NAS): the five-phase AMS lifecycle and its decision points; operational concept development and implementation-free functional analysis (ConOps, FFBD/N², CMLs); requirements analysis and architectural design synthesis (PRS→MRS, the PRD ratchet pPRD→iPRD→fPRD, RAM, ISEF/DoDAF views, CPRs); the seven technical management disciplines (Integrated Technical Management/SEMP, Interface Management/IRD-ICD, Risk-Issue-Opportunity, Configuration Management, SE Information Management, Decision Analysis, Verification & Validation); and the specialty disciplines (RMA via Service Threads/STLSC, Life Cycle Engineering, E3/Spectrum, Human Factors, Information Security via the NIST RMF, System Safety via the SMS, and Hazardous Materials/Environmental/EOSH). Scope limits: this is FAA-specific guidance, not policy — it is a tailorable menu that points outward to companion handbooks (FAA-HDBK-006A for RMA, the SMS Manual, the NIST 800-series) rather than restating generic SE theory; it is thin on detailed cost estimating, contracting/FAR law, software-development methodology, named anti-pattern catalogues, and any non-FAA or non-civil-aviation lifecycle. Source has no page numbers in the extracted text (~360 pp.).
日本語の概要は準備中です。原文の説明を表示しています。
Knowledge base from EU Artificial Intelligence Act — Regulation (EU) 2024/1689. Use for AI system classification (high-risk vs prohibited vs general), conformity assessment procedures, GPAI model obligations, transparency and disclosure requirements, governance structure (AI Office / AI Board), penalty tiers, value-chain operator obligations, post-market monitoring, and Annex III use-case analysis. Does not cover EU liability rules for AI (separate proposed directive) or implementation guidance documents issued after July 2024.
日本語の概要は準備中です。原文の説明を表示しています。
Knowledge base from MIL-HDBK-516C (Airworthiness Certification Criteria). Use for DoD air-system airworthiness planning: tailoring a certification basis, systems engineering criteria, and domain clusters for structures, flight technology, propulsion/installation, avionics/electrical/E3/diagnostics, computer systems/software, and crew systems (including applicable UAS control-station elements). Qualitative guidance handbook — not raw contractual requirements. Does not replace service airworthiness authority policy, civil FAA certification rules as authorities, or detailed JSSG/MIL performance specs.
日本語の概要は準備中です。原文の説明を表示しています。
Knowledge base from the GAO Agile Assessment Guide (GAO-24-105506, 2023). Use for assessing and managing Agile software development in federal programs: the Agile Manifesto and framework family (Scrum, Kanban, XP, SAFe, DA, DSDM, Lean, DevOps); the three adoption perspectives (team dynamics, program operations, organization environment); requirements decomposition (epics, features, user stories, INVEST, MoSCoW, definition of done); Agile-aware federal contracting (FAR, modular contracting, SOO/PWS/SOW, product owner vs. COR); program monitoring and control (WBS, cost, schedule, EVM at the feature level); Agile metrics (velocity, lead/cycle time, CFD, burn charts); and the auditor's key-question bank. Oversight- and acquisition-oriented: it tells you how to *assess and govern* Agile programs, not how to code. Thin on hands-on engineering practice, deep cost/schedule checklists (see gao-cost, gao-schedule), and any non-US-federal context.
日本語の概要は準備中です。原文の説明を表示しています。
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 the FAA AMS Lifecycle V&V Guidelines (verification and validation), Version 3.0, dated April 2017. Use for applying verification and validation across the FAA Acquisition Management System (AMS) lifecycle: the verify-vs-validate distinction (built right vs. right thing), the work-product/component/product tiers, the nine V&V planning elements, the four method catalogs (Appendix C), decision-point-gated V&V (SASP, CRD, Investment Analysis, Solution Implementation, In-Service Management), the Appendix B document checklists (PRD/APB/ISPD/PMP), and the DT/OT/IOA test triad. Scope limits: this is an FAA acquisition-V&V doctrine, NOT a general SE process model, requirements-engineering manual, or test-design textbook. It borrows its core V&V definitions from CMMI v1.2 (SEI, paraphrased) and presumes the surrounding AMS lifecycle (see the FAA SEM pack); its phase tables are policy snapshots as of April 2017 and it is thin on detailed test methods, tool specifics, and anything outside FAA acquisition governance.
日本語の概要は準備中です。原文の説明を表示しています。
Knowledge base from the NASA Schedule Management Handbook (2024 edition, Revision 2). Use for program/project schedule management of aerospace and large engineering efforts: the five sub-functions (Planning, Development, Assessment & Analysis, Maintenance & Control, Documentation & Communication); the Integrated Master Schedule (IMS) and the WBS/OBS/CBS breakdown structures; the Schedule Management Plan (SMP) and Basis of Estimate (BoE); Critical Path Method, logic, durations, float and margin; tiered schedule assessment (Requirements/Health/Basis checks, the Shock Test) and the Dimensions of Schedule Reliability; Schedule Risk Analysis (SRA), Integrated Cost-Schedule Risk Analysis (ICSRA), Monte Carlo, correlation, merge bias, and the Joint Confidence Level (JCL); baselining, replan vs. rebaseline, EVM schedule metrics (SPI, BEI, CEI, HMI, Earned Schedule, CPLI), and status/progress/forecast reporting. This is NASA's scheduling doctrine grounded in NPR 7120.5 and the GAO Schedule Assessment Guide. Thin on the underlying mechanics of CPM, statistics, and EVM (it points to companion handbooks); aerospace/space-flight-centric; anchored to the 2024 second edition.
日本語の概要は準備中です。原文の説明を表示しています。
Knowledge base from the DOE Order on Program and Project Management for the Acquisition of Capital Assets (DOE O 413.3 series). Use for Critical Decisions CD-0–CD-4, performance baselines, acquisition strategy and IPTs, cost/schedule/EVMS/PARS controls, risk-informed governance, reviews, and contractor requirements. Built from O 413.3C (2026-08-05), which cancels O 413.3B Chg 7 (2023-06-21); does not replace site-specific procedures, nuclear safety rules detail, or full estimating standards.
日本語の概要は準備中です。原文の説明を表示しています。