「ai safety」の検索結果

Select colormaps and qualitative palettes for scientific figures using perceptual-uniformity, color-vision-deficiency safety, and luminance-monotonicity criteria. Covers Crameri scientific colormaps, viridis/cividis/magma, Okabe-Ito categorical, ColorBrewer, and the rainbow/jet critique. Use when choosing palettes for heatmaps, scatter, networks, or any encoding where color carries quantitative or categorical meaning.

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

Read incoming retalk messages from this session's user's DESIGNATED sender(s) — one-shot, or as a background --follow reader that surfaces new messages in the session as they arrive (on your next turn). agent-talk only ever receives from specific saved peers, never the whole mailbox (safety). `<user>` is this session's user directory (absolute path; from init). Always renders the conversation (sent + received) as a beautiful chat transcript so the user can track it. Use to check mail or stay reachable.

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

Suede AI combined code review and ship grade in one pass: findings with file:line evidence plus an A-F lane grade, Instant-F security triggers, OWASP checks, a deploy-safety gate, and fix briefs. Use when asked to review this, grade this, security-check this, is this safe to ship, or check this PR before merge: whenever the caller wants both what is wrong and whether it ships. Runs only when explicitly invoked; never auto-fires on a diff, save, or commit. NOT FOR: findings only with accessibility and SEO lanes (use suede-code-review); the letter grade alone (use suede-code-grader); making CI enforce the verdict on merge (use suede-ci-gate); LLM, RAG, or agent behavior coverage (use suede-ai-eval).

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

Implement safety interlocks and protective mechanisms to prevent equipment damage and ensure safe control system operation.

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

Design database schemas with Prisma/Drizzle, PostgreSQL index strategy (B-tree, GIN, GiST, BRIN, Hash), query optimization (EXPLAIN ANALYZE), migration safety (expand/contract, zero-downtime), and sharding/partitioning. Use when user asks to design schema, create migrations, optimize slow queries, add indexes, choose between SQL/NoSQL, or set up Prisma/Drizzle. Do NOT use for data warehouse dimensional modeling, ETL pipeline design, or non-relational (MongoDB, DynamoDB) schema design.

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

Simplifies recently changed or explicitly scoped code while preserving observable behavior, error semantics, side effects, ordering, and public contracts. Use for readability cleanup, dead-code removal, reducing nesting, eliminating redundant wrappers, or making an implementation easier to maintain. Not for architecture redesign, new behavior, speculative cleanup, or a refactor without an adequate safety net.

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

Designs approval and sandbox policy for local coding agents: permission modes, isolation, network and destructive-command guards. Use when setting approvals. Not cloud sandboxes.

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

Testing Craft CMS 5 plugins and modules with Pest — test isolation, database safety, and the markhuot/craft-pest-core harness. ALWAYS load when writing, running, fixing, or reviewing tests for a Craft plugin or module, and whenever a suite touches a real Craft install. Covers why rollback is opt-in, tests/Pest.php + tests/bootstrap.php wiring, phpunit.xml.dist <env> pins (force DB name + table prefix, default connection coordinates, pin CRAFT_ENVIRONMENT against server-scoped locks), why --configuration= defeats DB isolation, throwing fail-closed DB guards, installing the plugin under test, process-timezone pinning, per-test site fixtures, idempotent Install migrations, stale service caches when components get swapped, muting audit sinks, queue stubs, factories, HTTP/DB assertions, CI jobs.

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

Use when parallel agents in a convoy or across git worktrees hit a write conflict on shared state — a git tree, a config, or a shared document — and you must decide whether the conflict is semantically real. Classifies each conflicting hunk as independent (keep both), redundant (pick one), or a genuine clash (escalate), instead of blind locks, abort-and-retry, or escalate-everything. Sits ABOVE refinery-merge and NEVER blind auto-merges: it wraps an LLM judgment, defaults to escalate on any uncertainty, and unconditionally escalates any hunk touching .planning/, config, credentials, or safety-critical paths. Backed by CoAgent (arxiv 2606.15376v1). Triggers on write conflicts between parallel agents on shared repo state.

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

Codified expertise for demand forecasting, safety stock optimization, replenishment planning, and promotional lift estimation at multi-location retailers. Informed by demand planners with 15+ years experience managing hundreds of SKUs. Includes forecasting method selection, ABC/XYZ analysis, seasonal transition management, and vendor negotiation frameworks. Use when forecasting demand, setting safety stock, planning replenishment, managing promotions, or optimizing inventory levels.

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

Idiomatic Kotlin patterns, best practices, and conventions for building robust, efficient, and maintainable Kotlin applications with coroutines, null safety, and DSL builders.

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

Financial statements, business segments, dividends, valuation multiples (PE/PB/PS), industry comparison, operating data, corporate actions, company and executive profiles, cross-stock comparison, and valuation ranking via Longbridge. Also: DCF models, value investing screens (low PE/PB, margin of safety), and behavioral finance analysis frameworks. Triggers: "财报", "三表", "利润表", "资产负债", "现金流", "估值", "PE", "PB", "分红", "公司信息", "高管", "行业估值", "并购", "DCF", "内在价值", "低估值", "安全边际", "行为金融", "小盘成长", "专精特新", "主营业务", "业务构成", "收入结构", "业务分析", "是做什么的", "是干嘛的", "公司画像", "行业排名", "行业龙头", "市场份额", "收入占比", "业务结构", "財報", "估值", "分紅", "內在價值", "安全邊際", "主營業務", "業務構成", "收入結構", "行業排名", "行業龍頭", "financial report", "income statement", "balance sheet", "valuation", "dividend", "company info", "industry valuation", "DCF", "value screen", "behavioral finance", "main business", "business composition", "revenue structure", "what does XX do", "industry ranking", "market share", "利潤表", "資產負債", "現金流", "行業估值", "併購", "行為金融", "小盤成長"

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

Ensure agent safety - guardrails, content filtering, monitoring, and compliance

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

Pre-landing PR review. Analyzes diff against the base branch for SQL safety, LLM trust boundary violations, conditional side effects, and other structural issues.

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

Discover and install agent skills from the open ecosystem (skills.sh), optimized for Japanese users. Use when the user asks 'how do I do X', 'is there a skill for X', or in Japanese 「〜できる？」「〜のスキルある？」「スキルを探して」「〜を自動化したい」「〜を効率化したい」. Always converts Japanese intent into short English search keywords before searching (the registry matches English keywords only), and verifies skill quality and safety before recommending installation.

生产数据操作、备份恢复、批量修复、数据导出和高风险变更前使用。适用于上线门禁、恢复验证、脱敏边界和操作风险评估。融合 SRE 双人复核 + 灰度执行 + 三层备份 + GDPR 脱敏。

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

Use before any deployment or completion claim. Enforces test gates, evidence-based verification, and frontend safety checks. No deploy without passing. No claims without evidence.

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

Write operator-facing and public documentation plans for AI-Controlled Party mixer/Soundcraft Ui24R scene arming. Use for runbooks, rehearsal checklists, show-day checklists, EN/PT docs updates, demo scripts, safety wording, and follow-up documentation revisions.

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

Interactive code simulation engine that spawns ghost personas to review your code before it ships. Each ghost walks through your code line-by-line from a different failure perspective: The Adversary (race conditions, double-submit, idempotency), The Enterprise Edge (business logic gaps, multi-currency, B2B tax exemptions, locale), Chaos Monkey (timeouts, partial failures, network partitions, OOM). Produces a chaos timeline, structured bug report with severity ratings, and three resolution tiers (quick fix, robust architecture, generated test suite). Use this skill whenever the user mentions code review, PR review, "find bugs", "what could go wrong", "will this break", "is this safe", "stress test", "edge cases", design review, pre-merge check, dry run, chaos test, or wants a second opinion on any code — even if they don't explicitly ask for "ghost personas" or "simulation". Also trigger when someone pastes a code snippet with any question about its correctness or safety.

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

Field identification of fungi using morphological features, spore prints, habitat analysis, and seasonal context with a safety-first approach. Covers cap, gill, stem, and spore characteristics, look-alike differentiation, toxicity risk assessment, and the critical rule of absolute certainty before consumption. Use when encountering an unknown fungus, foraging for edible mushrooms and needing to confirm species before consumption, assessing whether fungi in a garden or property are harmful, or differentiating an edible species from a dangerous look-alike.

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

Prepare herbal remedies from Hildegard von Bingen's Physica. Covers plant identification, preparation methods (tinctures, poultices, infusions, decoctions), dosage guidance, contraindications, and safety review based on 12th-century medieval pharmacopeia. Use when needing an herbal remedy for a specific ailment using Hildegardian pharmacopeia, seeking guidance on preparation methods and dosage, researching medieval herbal medicine, or integrating Hildegard's plant wisdom into holistic health practice.

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

Query the FDA's public openFDA APIs for post-market drug data — FAERS adverse-event reports, Drugs@FDA approval and submission history, Structured Product Labels including boxed warnings, the National Drug Code directory, recall enforcement reports, and drug shortages. Use this skill to check what a regulator has already concluded about a molecule or its class, to date an approval and count its efficacy supplements, to read an approved indication or boxed warning, and to score a drug-event pair for disproportionate reporting with PRR, ROR, and chi-squared. Also trigger on openFDA, api.fda.gov, FAERS, Drugs@FDA, SPL, NDC, pharmacovigilance, boxed warning, adverse event report, drug recall, or safety signal.

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

Use when a repository needs Git safety controls: guard destructive commands, set up gitignore or fix gitignore when untracked files keep appearing, or install or repair a repository-local pre-commit hook from project gates, including package-manager-native commit-time checks. Not for remote, credential, publish, deploy, or irreversible changes.

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

Pre-landing PR review. Analyzes diff against the base branch for SQL safety, LLM trust boundary violations, conditional side effects, and other structural issues. Use when asked to "review this PR", "code review", "pre-landing review", or "check my diff".

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