「requirements」の検索結果

Comprehensive toolkit for preparing ISO 13485 certification documentation for medical device Quality Management Systems. Use when users need help with ISO 13485 QMS documentation, including (1) conducting gap analysis of existing documentation, (2) creating Quality Manuals, (3) developing required procedures and work instructions, (4) preparing Medical Device Files, (5) understanding ISO 13485 requirements, or (6) identifying missing documentation for medical device certification. Also use when users mention medical device regulations, QMS certification, FDA QMSR, EU MDR, or need help with quality system documentation.

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

GGUF format and llama.cpp quantization for efficient CPU/GPU inference. Use when deploying models on consumer hardware, Apple Silicon, or when needing flexible quantization from 2-8 bit without GPU requirements.

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

Install the ToolUniverse Claude Code plugin in one step — provides MCP server with 1000+ scientific tools, 120+ research skills, slash commands, hooks, and the research agent. Use for first-time plugin install, troubleshooting plugin not loading, verifying MCP server connection, listing API key requirements, or configuring auto-update.

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

Authors portable, strongly-typed bioinformatics pipelines in the Common Workflow Language (CWL v1.2) as CommandLineTool/Workflow/ExpressionTool documents, validated with cwltool and run at scale on Toil/Arvados/Calrissian. Use when deciding CWL (portability/provenance/regulated) vs Nextflow/WDL/Snakemake; declaring secondaryFiles for indexed companions (.bai/.fai/.dict/.tbi and the caret rule); putting resources/containers under requirements (must-hold) vs hints (advisory) to avoid silent OOM; choosing scatterMethod (dotproduct vs flat_/nested_crossproduct); preferring $(...) parameter refs over ${...} JavaScript for portability; pinning DockerRequirement images; or emitting a CWLProv provenance object for audited/clinical settings.

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

Break requirements into epics and user stories. Use when the user says "create the epics and stories list"

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

Product manager for PRD creation and requirements discovery. Use when the user asks to talk to Nicole or requests the product manager.

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

Strategic business analyst and requirements expert. Use when the user asks to talk to Justin or requests the business analyst.

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

Enter explore mode - a thinking partner for exploring ideas, investigating problems, and clarifying requirements. Use when the user wants to think through something before or during a change.

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

Builds production-quality, accessible, responsive user-facing UIs. Use when building or modifying interfaces and pages, creating components, implementing layouts, meeting WCAG accessibility requirements, managing state, or when the output needs to look and feel production-quality rather than AI-generated.

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

Turn product requirements into scoped tasks with dependencies and acceptance criteria. Use for implementation planning and prioritization.

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

PM planning workflow — analyze requirements, select tech stack, decompose into prioritized tasks with dependencies, and define API contracts

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

Guide 1031 exchange processes and requirements. TRIGGERS - Use when user needs help with 1031-exchange-guide related tasks.

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

Prepare a product photo to meet Amazon's main image requirements: pure white background, square format, 2000×2000px, JPEG.

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

Extract role title, location, salary range, requirements, and application details from a public job posting.

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

Installs CARLA's ScenarioRunner (the official scenario engine) and picks the branch that matches the CARLA in use — master for 0.9.14-0.9.16 (UE4), ue5-master for 0.10.0 (UE5), leaderboard-1.0/2.0/2.1 when driving the Leaderboard. Clones or checks out the branch, installs requirements, wires PYTHONPATH (including the `agents` package the carla wheel does not ship), and verifies the import. Use when the user asks to "install scenario runner", "set up SR", "run CARLA scenarios", "use OpenSCENARIO", or has a scenario_runner that fails to import.

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

Expert fintech engineer specializing in financial systems, regulatory compliance, and secure transaction processing. Masters banking integrations, payment systems, and building scalable financial technology that meets stringent regulatory requirements.

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

Automated compliance checking for affiliate marketing content. Verifies FTC disclosure requirements, link tracking, and ethical affiliate practices.

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

SQLite-based ticket tracking for structured development workflows. Use this skill when the user asks to initialize a ticket database, import requirements, list tickets, get the next ticket to work on, mark tickets as done, or check ticket status. Essential for managing epics, user stories, and acceptance criteria.

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

Ensures designs meet accessibility requirements including WCAG compliance, color contrast, keyboard navigation, screen reader support, and focus management. Reviews designs for accessibility issues and provides recommendations.

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

German Impressum requirements under DDG and MStV. All Rechtsformen including GmbH, AG, UG, GbR, OHG, KG.

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

International legal notice requirements. UK, Switzerland, USA, and worldwide best practices for multi-jurisdiction websites.

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

Austrian Impressum (legal notice) requirements for all company types. Covers ECG, UGB, GewO, MedienG, and Offenlegungspflicht for public media. Use when working with impressum, legal notice, imprint, austria, österreich, ECG, mediengesetz, offenlegung.

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

Use before implementing any feature, behavior change, or refactor - settles requirements and design, then gets the design independently reviewed and approved by the user before code is written

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

Reply to an applicant for an employer's Otameshi Tenshoku listing: match the application against the listed requirements item by item on what the applicant actually stated, list the questions still open, and draft an invitation, a request for clarification, a hold notice or a decline that sticks to the listed conditions, keeps other applicants and internal notes out, and presents any new work or dates as a proposal rather than an agreed term. Use when a hiring manager, recruiter or small-business owner has applications to answer, wants to know what to ask before inviting, or has to decline; do not use to judge an applicant's aptitude or predict hiring outcomes, to screen on personal attributes unrelated to the work, to design the work (trial-work-design) or the listing (trial-listing-draft), or to send the message or update applicant records on the user's behalf.

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