「only」の検索結果

Checks an extracted PFD register as a process model and returns findings and unknowns only: connectivity closure, stream numbering, presence of design conditions, equipment duty text, phase and service labels, package and off-sheet scope, boundaries, operating cases, and agreement between the drawing and attached process documents, then holds at gate G2. Creates no design values. Use when the user asks to "check the process model", "verify connectivity" or "is the PFD ready for enrichment" after gate G1 and before enrichment. Do not use for extraction from the drawing, use pfd-intake-and-extraction instead; do not use to propose lines or instruments, use piping-enrichment. Drafts for human review; never approves, authorises or signs off.

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

Synthesises a batch of customer feedback (survey answers, reviews, ticket and chat comments) into a DRAFT themed report: coded themes with record counts and shares, anonymised verbatim quotes cited to record codes, contradictions and unverified claims, and the follow-up questions to answer next. Produces no sentiment score or percentage positive as fact; ratings appear only as distributions with n. Use when the user asks to "theme this feedback", "what are customers saying", "summarise these survey answers", "analyse these reviews", "find the top complaints in these comments" or "code this voice of the customer data". Do not use for exit interviews, use exit-interview-synthesis instead; for sorting a live queue and drafting replies, use ticket-triage-pack; for project retrospectives, use lessons-learned-synthesis. Drafts for human review; never approves, authorises or signs off.

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

Reads a process flow diagram (image, PDF or native export) with its job header and returns a provenance-tagged extraction register: equipment, streams, tags, connectivity, instruments already shown, notes and legends, connectivity findings and an explicit UNKNOWN list, then holds at gate G1. Extracts and records only; never enriches, tags or proposes. Use when the user asks to "start a PFD to P&ID job", "read in the attached PFD", "extract the equipment and streams from this PFD" or "read this PFD into a register". Do not use for checking the model, use process-model-check instead; do not use to propose lines, instruments or tags, use piping-enrichment or instrumentation-and-control-enrichment after gate G2. Drafts for human review; never approves, authorises or signs off.

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

Prepares a DRAFT management-of-change intake record from a change description (email, meeting note, marked-up drawing or request form): what changes from what to what and where, the identifiers named, the candidate affected documents matched against the register, the disciplines to consult with the reason for each, and the numbered questions reviewers must answer, with UNKNOWN wherever the description is silent. Prepares the record only: never approves, classifies the change, decides replacement in kind or makes any hazard or safety judgement. Use when the user asks to "raise an MoC for this", "prepare the change request intake", "which documents does this change touch", "who needs to review this change" or "draft the MoC form from this email". Do not use for tracking who owes information to whom across disciplines, use interface-register-builder instead. Drafts for human review; never approves, authorises or signs off.

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

Maps every proposed P&ID object from an accepted enrichment draft to the generic family, catalogue class and required attributes the project's intelligent P&ID authoring tool would need, as a readiness table with UNKNOWN wherever the project catalogue extract is not provided, plus connectivity readiness per line and a numbered list of import blockers. Mapping only: it never writes to the tool, never produces an import file and never claims a class exists in the catalogue. Use when the user asks to "build the readiness map", "show how far the draft is from a sandbox import", "list what would block the import", "map the objects to the tool catalogue" or "check attribute readiness against the catalogue extract" after gate G3. Do not use for validating the discipline sections or assembling the review package, use validation-and-review-package instead. Drafts for human review; never approves, authorises or signs off.

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

Read and understand PDF documents with the pdf_* tools - inspect a document before reading it, extract text in reading order or as reconstructed layout, search a document without reading all of it, recognize scanned pages that have no text layer, and render pages as pictures. Covers scanned documents, chat attachments, page-range and character caps, and the read-only and untrusted-content rules.

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

Render a web page on the host and measure it - screenshots, computed styles, element boxes and post-script text - when a page only exists after its scripts run or when the question is about layout. Covers choosing between web_fetch and a render, reading a design's real measurements, comparing viewports, and the egress policy that decides what may be reached.

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

Drive the user's host machine directly through Cua, with no sandbox. Maps to Cua's Localhost API. Higher risk - the agent can click, type, and run shell commands on the real desktop. Use only when the user explicitly opts in and read the safety section first. Triggers - "control my computer", "click here", "use my real Chrome", "no sandbox", "내 컴퓨터 자동화".

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

Recall past work across Claude Code and Codex sessions. Finds decisions, research, fixes, and conversations by intent; with only a project and no question, orients on that project's recent state.

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

Audit and repair a kohya-style LoRA dataset before training. Use when the user asks to check, validate, inspect, fix, clean, 体检, or 修 a dataset, captions, or tags. Inspect image count, repeats and step budget, resolution and aspect buckets, duplicates, corrupt or non-RGB images, missing or empty captions, trigger consistency, and tag-frequency hygiene. Return a structural PASS, WARN, or FAIL report and apply only confirmed fix_dataset.py actions, dry-run first with displaced originals quarantined.

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

Navigate the user through reading code stop by stop to pay down understanding debt left by AI tooling. Explicit invocation only.

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

Tutor the user step by step on a plan, implementation, codebase, or topic to pay down understanding debt left by AI tooling. Explicit invocation only.

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

Quiz the user on a plan, implementation, or codebase to pay down understanding debt left by AI tooling. Explicit invocation only.

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

Refresh WhatsApp text into an Obsidian vault (data layer, dashboard, group labels, contact notes). Text only, never downloads media, and pulls the recent window the live companion bridge exposes rather than a full multi-year archive. Semi-automatic by design: it drives the live bridge and needs the phone nearby. Triggers: "/whatsapp-sync", "pull whatsapp".

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

Fold a fresh export of an already-imported Telegram chat into a vault, adding only the new messages. Idempotent by message id, so it never duplicates. Triggers: "re-import <chat>", "update the telegram import".

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

Quality gate immediately after building: prove that what was just built actually works, while the context is still hot. Six steps: scope what changed, run live on real data, break it on purpose, show a counter or log proving it ran, root-cause any failure and re-run, then a verdict with evidence. Only a green verdict earns the word done. Supports an external multi-vendor review panel as a mid-step. Triggers: "/tt", "/test", "prove it works", "test what we built".

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

Squeeze three to five durable lessons out of the owner's own words from the last seven days into a weekly note in the insights folder. The LLM reads only a collector's digest, never the raw corpus. Triggers: "/wisdom-distill", "distill my week", "weekly wisdom".

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

Weave a new node (concept, framework, theory, project, principle) into the whole vault graph rather than just creating a note. Mode A links one new node against the vault by top-K retrieval, with the LLM judging only those candidates; mode --deep finds orphaned islands and wires them in. Backup before edits, preview before writing. Triggers: "/relink", "integrate this concept".

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

Work leads in Telegram: find prospects by topic, keep only those who self-mentioned it, resolve their handle including through shared groups, pitch personalized and grounded in real templates, run a two-step scheduling close, triage follow-ups, and capture everyone in the CRM. Triggers: "find leads for <topic>", "pitch this prospect", "run outreach".

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

Audit recent agent work for recurring manual patterns that have no skill yet, cross-check against installed skills and public skill catalogs (installing beats building), and propose the top two or three as before/after. Read-only analysis. Triggers: "/skill-gap", "what skills should I build", "audit my skills".

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

Report this machine's file-synchronization state with the whole fleet: peers connected, per-share state and files still needed, folder errors, and how many sync-conflict files piled up, which is the silent sign two machines are fighting over a file. Read-only and zero tokens. Triggers: "/sync-check", "is sync alive", "sync status".

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

Draft short, in-voice reply candidates to a fresh community shortlist: read the nightly detector report, pick posts in safe or opinion topics, pull a grounding snippet from the local corpus, and write the drafts. Drafts only, and the owner posts. Triggers: "/sostav-comments", "draft replies to the shortlist".

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

Health-check, audit and, on approval, fix a self-hosted n8n automation stack. Health is read-only; any workflow edit goes preview, approval, apply. Triggers: "/n8n", "/n8n health", "/n8n fix <id>", "which workflows are failing".

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

Mine the day's sessions for the owner's intentions, cluster them into distinct ones, store them, and write two or three detailed posts with an explicit ask per channel, plus a loop tracking who answered. Drafts only. Triggers: "/intention", "mine today's intentions", "intention posts".

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