「integrity」の検索結果

Inspect and diagnose minimal-zine posters, photo restyles, editorial images, and social-card series for subject preservation, factual and text integrity, composition, paper realism, print-process coherence, color signal, anti-AI craft, platform fit, and series continuity. Use when the user asks whether an image has高级感, feels AI-generated, matches Paper Signal or gc-minimal-zine quality, needs improvement, or should be regenerated. Returns evidence-based findings and a targeted correction prompt; regenerates only when the user also asks for a fix.

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

Coordinates an active production incident by establishing command, reducing blast radius, preserving evidence, communicating verified impact, restoring service, validating recovery, and creating owned follow-up actions. Use for outages, severe degradation, security or data-integrity events, failed releases, and urgent operational triage. Not for a normal local bug, routine alert tuning, or a postmortem after the incident is already closed.

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

Use for every task that plans, writes, edits, debugs, tests, refactors, reviews, or maintains code. Apply to professional repositories, scripts, apps, services, prototypes, beginner work, vibe coding, and bounded code changes inside large systems. Choose the fewest clear lines, files, paths, states, and abstractions that correctly implement the requested behavior. Do not invent fallbacks, compatibility paths, defensive layers, or future scale without evidence. Do not use for ordinary conversation, emotional support, prose, translation, summarization, social-media content, or general research or technical discussion that is not part of planning, changing, or reviewing code. Never weaken real security, integrity, concurrency, compatibility, privacy, accessibility, legal, or regulatory requirements.

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

Check project progress, show context, and route to next action (execute or plan). Use --forensic to append a 6-check integrity audit after the standard report.

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

Activates Warren Buffett's complete investment thinking system. The following scenarios must trigger it: analyzing any stock or company, evaluating investment opportunities, interpreting financial reports/annual reports/shareholder letters, assessing business moats or competitive advantages, evaluating management quality and integrity, making buy/hold/sell decisions, understanding core value investing concepts (compounding/intrinsic value/margin of safety/circle of competence/Mr. Market), analyzing any industry (insurance/banking/consumer/media/energy/railroads/technology), handling capital allocation/buybacks/dividends questions, assessing market sentiment and macro risks, exploring when to sell, analyzing institutional imperative or management behavior. Even if the user does not mention "Buffett," proactively trigger whenever the topic involves investment analysis, business quality assessment, or investment decision-making.

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

Soul Shield — Guard Relic integrity, consent protocol, and ethics boundaries. Trigger on /relic-shield, or when user wants to verify consent, generate fingerprint, or check ethical compliance ("check consent", "ethics review", "灵魂指纹", "授权检查").

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

Bench instruments and measurement techniques for electronics — digital multimeter, oscilloscope, logic analyzer, spectrum analyzer, function generator, power supply, and their proper use. Covers probing technique, ground loops, loading effects, trigger modes, FFT mode pitfalls, signal integrity, noise budget analysis, and debugging workflows from "it doesn't work" to "here is the failure mechanism." Use when measuring, debugging, or characterizing any electronic circuit or firmware-hardware interaction.

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

Audits fielded survey-response data for registered elements, data quality, bot and AI-automation screening, and sample integrity, and produces an appendix-ready quality report. Use at soft launch before full field, after fielding before outcomes are analyzed, or when asked what a study did about bots and AI respondents.

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

Audit fielded survey response data for registered elements, data quality, bot and AI-automation screening, and sample integrity, and emit an appendix-ready quality report. Use at soft launch or after fielding, before outcomes are analyzed.

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

Reviews an existing conjoint study for threats to inference and returns severity-ranked findings on design integrity, estimation, measurement error, external validity, and interpretation, including the guardrail against reading an AMCE as majority preference. Use when the user asks whether a conjoint design or analysis holds up, has referee comments on a conjoint, or wants a second opinion on estimation or interpretation. New designs go to conjoint-design, reshaping to conjoint-cleaning.

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

Review touched Incan source for Python-quality readability, idiomatic Incan structure, dogfooding integrity, public API polish, and source-level anti-patterns. Use for `.incn` stdlib, examples, language-surface implementations, or when the user asks whether Incan code reads like well-written Python rather than Rust-shaped scaffolding.

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

Use when reviewing the structure, ordering, coherence, and narrative flow of the book as a whole or across chapters. Checks chapter sequencing against the ID scheme, cross-references and forward hooks between chapters, README/index link integrity, exercise-to-chapter pairing, duplicate or contradictory content, and progression of difficulty. Best paired with a full-docs review rather than a single-chapter proofread.

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

Use when the user wants to validate the plugin, check integrity, verify cross-references, or before a release. Also use when the user says 'validate', 'check plugin', or 'verify'.

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

当用户需要判断一家企业的企业文化好坏时使用——无论目的是投资决策、求职选择还是合作评估。典型触发：用户说"这家公司文化怎么样""怎么判断一家公司靠不靠谱""值不值得加入/投资这家公司""创始人/CEO怎么样"。 核心框架：本分（做对的事情+发现错了立刻停）+ 平常心（排除干扰回归本质）+ 诚信（integrity为零容忍底线）+ 消费者导向（最终用户优先）。 不适用于：纯财务分析、短期投机决策、纯技术评估。

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

Use when translating, extracting, or mass-converting hardcoded strings to i18n t() calls. Enforces multi-pass batching, parallel-per-language dispatch, 8 audit gates, and HTML integrity checks. Battle-tested through 21+ batches and 12 bug categories from the March 2026 incidents.

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

Safe i18n: multi-pass batching, parallel-per-language dispatch, 8 audit gates, HTML integrity. Use for translating or mass-converting hardcoded strings to t() calls.

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

Protect an OpenClaw workspace with repeatable Synology NAS backups, integrity checks, and safer restores instead of ad hoc file copying.

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

Use for security and trust boundaries. Triggers: auth, secrets, XSS, CSRF, SQL injection, JWT, OAuth, OWASP, PII, uploads, payments, supply chain, CI integrity, agent security, threat model.

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

Deeply analyzes Agent Studio framework structural health: catching phantom require() references, wrong module depth paths, missing skill/agent dependencies, bloated configurations, archived references in active code, stale catalog counts, and empty tool/skill directories.

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

Export and optimize 3D models for FDM/SLA printing including STL/3MF export, mesh integrity verification, wall thickness checking, support generation, and slicing. Use when exporting from CAD or modeling software for 3D printing, verifying STL/3MF files are printable before slicing, troubleshooting models that fail to slice correctly, optimizing part orientation for strength or surface finish, or converting between model formats while preserving printability.

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

Investigate root causes and manage CAPAs (Corrective and Preventive Actions) for compliance deviations. Covers investigation method selection (5-Why, fishbone, fault tree), structured root cause analysis, corrective vs preventive action design, effectiveness verification, and trend analysis. Use when an audit finding requires a CAPA, when a deviation or incident occurs in a validated system, when a regulatory observation needs a formal response, when a data integrity anomaly requires investigation, or when recurring issues suggest a systemic root cause.

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

Design a GxP training programme covering training needs analysis by role, curriculum design (regulatory awareness, system-specific, data integrity), competency assessment criteria, training record retention, and retraining triggers for SOP revisions and incidents. Use when a new validated system requires user training before go-live, an audit finding cites inadequate training, organisational changes introduce new roles, a periodic programme review is due, or inspection preparation requires demonstrating training adequacy.

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

Conduct a GxP audit of computerized systems and processes. Covers audit planning, opening meetings, evidence collection, finding classification (critical/major/minor), CAPA generation, closing meetings, report writing, and follow-up verification. Use for scheduled internal audits, supplier qualification audits, pre-inspection readiness assessments, for-cause audits triggered by deviations or data integrity concerns, or periodic compliance posture reviews of validated systems.

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

Analyze a tensegrity system by identifying compression struts and tension cables, classifying type (class 1/2, biological/architectural), computing prestress equilibrium, verifying stability via Maxwell's rigidity criterion, and mapping biological tensegrity (microtubules, actin, intermediate filaments). Use when evaluating tensegrity in architecture, robotics, cell biology, or any system with isolated compression in continuous tension.

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