「requirements」の検索結果

Reviews CRE insurance certificates (ACORD 25) and endorsements against Access Agreement insurance requirements, producing a pass/fail compliance determination with broker-ready deficiency instructions. Verifies coverage limits, Additional Insured status, primary/non-contributory language, waiver of subrogation, umbrella alignment, and carrier qualifications. Use when reviewing COIs, ACORD forms, vendor or contractor insurance, site access insurance, or Additional Insured endorsements in commercial real estate transactions.

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

Regulatory compliance guidelines for life insurance policy administration transactions. Use when processing address changes (state-change impacts), beneficiary changes (community property, ERISA, minors), or any transaction that may trigger compliance review. Covers NAIC model regulations, state-specific rules, OFAC screening, and suitability requirements.

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

Manage month-end and year-end close (Monats-/Jahresabschluss) with checklists, task sequencing, and status tracking. Adapted for Swiss OR requirements including MWST and social insurance.

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

Validates certificates of insurance against lease and contract requirements. Compares coverage types, limits, endorsements, and expiration dates field-by-field, flags deficiencies, and generates cure notices.

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

Drafts a compliant Commercial Invoice for Export satisfying customs, banking (L/C), logistics, and insurance requirements. Enforces Incoterms 2020, HS tariff classification, country-of-origin determination, export control referencing, and certification language. Use when preparing export invoices for customs authorities, freight forwarders, banks, or insurance underwriters.

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

Drafts U.S. commercial real estate access and indemnity (right-of-entry) agreements for pre-closing due diligence. Covers license grants, non-invasive vs invasive testing gates, insurance/endorsement requirements, indemnity with discovery carve-outs, restoration and lien remedies, confidentiality, and anti-indemnity guardrails. Trigger: access agreement, right of entry, due diligence access, Phase I/II, invasive testing, pre-PSA site inspection.

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

Review aviation insurance coverage and requirements. TRIGGERS - Use when user needs help with aviation-insurance-review related tasks.

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

Head of product — orchestrate the product team, write briefs, plan initiatives, hand off to Apex. Use when asked to "write a product brief", "plan the roadmap", "decide what to build", or hand off requirements to engineering.

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

Design or audit B2B sales pipeline — define stage names, entry/exit criteria, qualification standards, and CRM field requirements. Use when asked to "design our pipeline", "audit our CRM stages", "define what qualified means", or "build a sales process".

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

Spark Studio's team-culture Relic — a 5-person AI product startup that existed 2022–2025: roast first then work, hotpot on Fridays, used Feishu while cursing Feishu daily, requirements always changing but versions always shipping. 星火工作室（Spark Studio）的团队文化 Relic。一个 2022-2025 年间存在过的 5 人 AI 产品创业团队： 先吐槽再开工，周五点海底捞，用飞书但天天骂飞书，需求总在变但总能把版本扛上线。

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

Technical writing, engineering specifications, reports, presentations, and documentation standards for engineering practice. Covers document types (requirements documents, test reports, design rationale, operations manuals), writing style, data visualization, engineering drawing standards, and oral presentation techniques. Use when writing engineering documents, presenting technical results, creating specifications, or learning documentation best practices.

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

Bias detection and mitigation, fairness metrics, privacy frameworks, consent models, transparency requirements, and accountability structures for data science practice. Covers algorithmic bias sources, disparate impact testing, differential privacy, GDPR principles, model cards, datasheets for datasets, responsible AI frameworks, and the organizational governance needed to make ethics actionable. Use when auditing models for bias, designing privacy-preserving systems, establishing governance processes, or evaluating the social impact of data-driven decisions.

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

Reliability engineering for cloud systems — SLIs, SLOs, error budgets, SRE practices, runbooks, incident response, on-call rotation, blameless postmortems, chaos engineering, and the NASA Systems Engineering methodology (MCR/SRR/PDR/CDR/ORR phase gates, TAID verification, requirements tracing) adapted to cloud operations. Use when establishing SLOs for a new service, running an incident, writing a runbook, preparing a launch readiness review, or bringing NASA SE discipline to cloud deployments.

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

Traces decisions and requirements through GSD artifacts. Use when user asks "why did we...", "what happened to...", or mentions decision history.

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

Deep symmetries and unifying principles — gauge theory, Lie groups, Noether's theorem, and the Standard Model. Constructs field theories from symmetry requirements, derives conservation laws, and traces force unification. Use when working with gauge symmetry, Lie groups (U(1), SU(2), SU(3)), conservation laws via Noether's theorem, the Higgs mechanism, or Standard Model structure.

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

Clarify requirements before implementing. Use when serious doubts araise.

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

Guided workflow for building custom AI agents using the OpenHands Software Agent SDK. Use when you want to create a new agent through an interactive interview process that gathers requirements and generates implementation plans.

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

Validates and corrects Python shebangs and PEP 723 inline script metadata by applying four shebang-selection rules. Use when auditing or fixing shebangs in Python files — choosing between plain python3 and the uv shebang for standalone scripts with external dependencies, adding or removing PEP 723 metadata blocks to match actual import requirements, checking execute bit presence, or avoiding redundant transitive dependencies when typer is declared.

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

Shared Python 3.11+ development rules — type safety and the boundary policy for `Any` (ty, native generics, Protocol, TypeIs, Pydantic), layered architecture and SOLID, error handling, security, performance, identifier naming, PEP 723 script dependencies, Rich/Typer output, tooling defaults (uv, ruff, ty, hatchling, pytest), and testing requirements (behavioral coverage, TDD). Activates when any Python skill or agent needs the shared rules for implementation, code review, refactoring, or test authoring.

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

Executes a four-phase feature addition workflow (Discovery, Planning, TDD Implementation, Verification) for Python projects. Use when adding a new feature end-to-end — discovering project structure and integration points, drafting a feature spec with MoSCoW-prioritized requirements and BDD acceptance criteria, implementing via test-first TDD cycles, then verifying with ruff lint, ty type checks, and behavior-focused regression and contract coverage.

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

You MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or when users request help with ideation, marketing, and strategic planning. Explores user intent, requirements, and design before implementation using research-validated prompt patterns.

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

Design, create, run, monitor, and maintain Vapi Simulations for assistants and squads. Use for turning plain-language requirements into a coverage plan, simulation personalities, scenarios, structured-output success criteria, simulations, suites, extending an existing suite, chat or voice runs, tool mocks, target variables, lifecycle webhooks, regression coverage, launch readiness, CI quality gates, run-result analysis, and simulation API validation errors. Do not use for fixed-turn mock-conversation Evals unless the user is deciding between Evals and Simulations.

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

Python testing strategies using pytest, TDD methodology, fixtures, mocking, parametrization, and coverage requirements.

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

[AUTO-INVOKE] MUST be invoked BEFORE creating git commits, PRs, or code reviews. Covers Conventional Commits, PR templates, review requirements, and AI-assisted development rules. Trigger: any task involving git commit, git push, PR creation, or code review.

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