「eth」の検索結果

Estate Planning & Legacy Protection for the Owens family. Tracks wills, trusts, beneficiary designations, life insurance, survivor benefits, and powers of attorney. Ensures Lindsey and the kids are protected if something happens to Tory. Triggers on: "Estate plan", "Will", "Life insurance", "Beneficiaries", "What happens if", "Legacy", "Survivor benefits", "Power of attorney", "Trust", "Estate check", "Beneficiary audit", "SGLI", "FSGLI", "Dependent education", "Chapter 35". The only estate plan that fails worse than a bad one is no plan at all.

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

Use when the user mentions flood zone, flood risk, FEMA, SFHA, floodplain, property due diligence, natural hazard disclosure, flood insurance, base flood elevation, or asks whether a property is in a flood zone.

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

Cyber Risk Quantification engineer for CyberRadar. Implements FAIR (Factor Analysis of Information Risk) methodology, Monte Carlo simulation for loss distribution modeling, financial impact quantification in multi-currency (SAR, USD, EUR, GBP), loss exceedance curves, risk treatment ROI calculation, insurance premium optimization, and board-ready financial risk reporting. Transforms qualitative risk assessments into monetary terms for executive decision-making. Triggers on: CRQ, FAIR, Monte Carlo, financial impact, loss modeling, risk quantification, cyber insurance, risk treatment ROI, financial risk.

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

Quantify cyber risk using FAIR methodology with Monte Carlo simulation, assess control effectiveness against NIST CSF/CIS/ISO 27001 frameworks, evaluate risk appetite alignment, and analyze cyber insurance coverage adequacy. Covers threat landscape mapping, asset valuation, loss event frequency and magnitude estimation, annualized loss expectancy calculation, control gap analysis with ROI ranking, residual risk assessment, and insurance policy gap modeling at 90th/95th/99th percentile loss scenarios. Use when building risk registers, preparing board-level risk dashboards, evaluating security investment priorities, assessing cyber insurance coverage, or auditing any organization's risk quantification maturity per NIST RMF, ISO 27005, or FAIR standards.

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

Fast Instagram lead generation using Brave Search API. Scrapes 100+ insurance agent leads from Instagram via Google search results. Use when user wants quick lead volume via Brave search method, needs 100+ leads fast, or says 'brave instagram', 'brave search leads', 'get 100 leads', or wants high-volume lead generation without browser automation.

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

Evaluates loss reserve adequacy with development triangle analysis and actuarial methods. Use when analyzing reserves, interpreting loss triangles, or assessing reserve adequacy.

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

Inspect, schema, and fill true AcroForm PDFs using sciClaw's pdf_form_inspect, pdf_form_schema, and pdf_form_fill tools. Use when: (1) checking whether a PDF is a real fillable AcroForm, (2) listing form field names, types, and choices, (3) filling a supported form from structured values, (4) preparing reviewable insurance, legal, administrative, or clinical form drafts, (5) reporting skipped fields or unused input keys after a fill. Do not use for scanned PDFs, OCR tasks, or XFA-only forms.

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

Generates Domain Entities following DDD principles with factory methods, private setters, domain events, and proper encapsulation. Supports aggregate roots, child entities, and value objects.

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

Use when asked to analyze a funnel, find where users drop off, diagnose low conversion or activation rates, design a metrics framework, set up OKRs, or measure whether a feature is working. Examples: "analyze our funnel", "why is activation low", "where are users dropping off", "design OKRs for this quarter", "is this feature working", "set up metrics for this launch".

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

Use when asked to write a product brief, turn a feature idea into a spec, define requirements for something to build, or clarify what a product should do and why. Examples: "write a brief for X", "turn this idea into a spec", "what should we build here", "help me define requirements".

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

Design a compromise assessment — hunting scope, methodology, and evidence collection. Use when asked "are we compromised", "run a compromise assessment", or "scope a threat hunt".

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

Design direction advisor — generates 3 differentiated visual directions with live HTML demos for selection. Use when the brief is vague ("make something nice", "pick a style", "explore directions"), when no design system exists, or when the user wants to compare visual approaches before committing. Richer than /form-style: produces actual visual demos, not just recommendations. Trigger words: "design direction", "style exploration", "pick a direction", "what should this look like", "give me options", "explore styles", "design philosophy".

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

Design a hyperparameter tuning strategy for a model — search space, method, and budget. Use when asked to "tune hyperparameters", "define a search space", or "set a tuning budget".

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

Elite frontend design taste for building, reviewing, and polishing web interfaces. Use whenever the user wants to design, redesign, shape, critique, audit, polish, or improve any UI (landing pages, portfolios, dashboards, product UI, components, forms, onboarding, empty states) or asks to make something look better / premium / modern, fix the styling, add or fix animations, or make a design feel less generic ("AI slop"). Covers typography, color, spacing, layout, visual hierarchy, motion, micro-interactions, component states, accessibility, responsive behavior, UX copy, and anti-pattern detection.

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

Methodological guide for the AI Agent to safely and systematically translate, refactor, and modernize giant legacy codebases (PHP, Python 2, old React) into modern stacks.

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

Expert guide for Web3 and blockchain dApp integration — viem, wagmi v2, ethers.js v6, RainbowKit, smart contract interactions, and EVM wallet state / Panduan ahli integrasi Web3 dan blockchain.

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

Ship the Seekter kit to git. Branch, commit and push the tracked, person-independent files (skills, references, scripts, templates) after a run has taught the kit something. Use when the user runs /seekter-git or asks to commit, push, or open a PR for the changes made to Seekter itself.

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

Show a table and its map, diagram, timeline or chart together, with selection synced both ways. Use when data appears in two representations at once.

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

Group controls with Gestalt principles so users see what belongs together. Use when laying out components, navigation, toolbars, forms or dashboards.

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

Comprehensive markdown planning methodology for software projects. Use when starting a new project, creating implementation plans, or refining architecture before coding.

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

Iterative UI/UX polishing workflow for web applications. The exact prompt and methodology for achieving Stripe-level visual polish through multiple passes.

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

The discipline of keeping a field notebook — words, pictures, numbers, metadata, and questions captured during sustained outdoor observation. Covers the Laws notebook method, the sit-spot practice, phenology recording, sketch-first-name-later discipline, and the long-term research value of accumulated journals. Use when the task is to teach or structure ongoing field observation rather than answer a one-shot identification.

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

A survey of the best-known active scientific controversies in nutrition — saturated fat and cardiovascular disease, dietary cholesterol, low-carb vs low-fat, ultra-processed foods, red meat and cancer, salt and blood pressure, and the replication status of popular single-nutrient claims. Use when a question asks whether a widely reported nutritional claim is settled, or when the department needs to distinguish "contested but plausible" from "settled" from "disproven."

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

Methods for assessing what people actually eat — 24-hour recall, food frequency questionnaires, diet diaries, biomarkers, duplicate-plate studies, and controlled feeding. Covers the relative strengths and biases of each instrument, how to choose among them for a given question, and how to interpret results in the presence of measurement error. Use when a user wants to estimate population-level intake, individual-level intake, or evaluate the plausibility of a dietary claim that depends on how intake was measured.

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