「helper」の検索結果

Write or change Go code in a repository that runs declscope, which shows as a .declscope.y*ml or baseline file, //declscope: comments, or declscope in CI. Read this before adding, naming or moving a declaration, a helper that several files use, or a test. Read it too before splitting a file, writing a //declscope: directive, or acting on a declscope diagnostic. Covers where code belongs, naming it accurately, and fixes that hide a problem.

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

ผู้ช่วยสัตวแพทย์ — species-specific reference (สุนัข/แมว/exotic) + DDx + drug dosing weight-based + clinical pearl สำหรับสัตวแพทย์ที่มีใบประกอบวิชาชีพเท่านั้น

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

ผู้ช่วยเภสัชกร — drug dictionary (Thai/Generic), interaction matrix, pediatric/geriatric/renal dosing, counseling script สำหรับเภสัชกรที่มีใบประกอบวิชาชีพเท่านั้น

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

ผู้ช่วยนักจิตวิทยา — session note (SOAP) + CBT worksheet + case conceptualization + DSM-5 reference สำหรับนักจิตวิทยาที่มีใบประกอบวิชาชีพเท่านั้น

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

ผู้ช่วยทันตแพทย์ — dental code reference + treatment planning + materia medica dental + clinical pearl สำหรับทันตแพทย์ที่มีใบประกอบวิชาชีพเท่านั้น

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

ผู้ช่วยแพทย์แผนจีน — ตำรับสมุนไพรจีน, เส้นลมปราณ, การวินิจฉัยแบบ TCM (ดู/ฟัง/ถาม/คลำ), patient intake form

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

ผู้ช่วยสรุปงานวิจัย + differential diagnosis list + drug interaction check + clinical pearl สำหรับบุคลากรการแพทย์เท่านั้น

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

สร้าง Dockerfile CI/CD yaml และ monitoring config ที่ production-ready ไม่พัง

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

Convert Claude's Markdown output to each channel's native text syntax before delivery. Adds zero-dependency formatting for WhatsApp, Telegram, and Slack (marker substitution). Also ships a Signal rich-text helper (parseSignalStyles) used by the Signal skill.

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

Review a diff against dynamic-neural-field-composer's own standards - backwards compatibility, Clean Code, tools/ helper reuse, C++20 idiom, hot-path performance, and test coverage. Use before opening a PR or when asked to review a branch or change.

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

Create and operate ChatDOC Studio knowledge bases through pd_router using a Bearer API key and JavaScript helpers. Use when Codex needs to upload one or more PDF/DOC/DOCX files, skip failed files without aborting the whole job, create a knowledge base from successful uploads, or call the ChatDOC Studio knowledge-base skill endpoints through `https://platform.paodingai.com/openapi/chatdoc-studio/...`.

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

Use when writing or reviewing TypeScript frontend tests — Jest unit/integration tests for React components and hooks built with Chakra UI, React Query, Zustand, and Next.js App Router. Triggers on edits to `*.test.tsx`, React component/hook test files (`.tsx`, not `.ts`) under `**/__tests__/`, custom test render helpers, or mentions of "frontend test", "component test", "hook test", "React test", "UI test".

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

Write and debug spreadsheet formulas (Excel/Google Sheets), pivot tables, and array formulas; translate between dialects; use when users need working formulas with examples and edge-case checks.

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

Power batch-sprint helper — hosts the two behaviours that distinguish the `power` workflow track from spec-entry. (1) Per-ticket iteration: security runs once PER TICKET over workflow.json.tickets[] while the mechanical phases run once for the batch. (2) Commit split: at the commit phase, group the batch's working tree into ordered Conventional Commits via commit-split.mjs, closure last. Invoked within a `power`-track workflow; not a standalone feature. Opt-in via velocity.power_mode.enabled; requires git.

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

PM-mode brainstorm helper. Captures the requirement via Socratic dialogue before any entry phase (`/intake`, `/spec`, `/tdd`) drafts its artifact. Stage 0 skip-check, Stage 1 gap-analysis, Stage 2 probe-loop, Stage 3 confirm-and-persist. Output lives at `docs/brief/<slug>.md`. Never proposes solutions — Stage 2 dialogue discipline is structurally enforced via `discipline.mjs`.

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

Split a dirty working tree into single-concern Conventional Commits. The deterministic inventory.mjs helper groups dirty paths by concern (docs, source + paired test, config, governance); main context refines the grouping and presents a commit plan. Read-only until the user approves the plan — it never stages, never commits, never touches consent paths. Disjoint from the commit skill (Phase 11 executor): the planner proposes a split; the executor lands one consented commit. Use when a working tree has accumulated heterogeneous changes that should not land as one commit.

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

Drift check between the baseline implementation on disk and the claims in `docs/init/seed.md` + cross-references in CLAUDE.md, README.md, and the rendered docs site. Verifies hook/agent/skill/command names + counts, settings.json wiring, project.json key presence, .mcp.json servers, vendored license files, and helper script presence. Exit 0 PASS / 1 FAIL — suitable for CI. Read-only; safe to invoke any time.

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

Derive an execution roadmap from a project's vision/spec docs by first principles, then diff that fresh derivation against the existing roadmap to prove the task ORDER is correct. Use this whenever the user wants to review, validate, re-derive, or sanity-check an execution roadmap or delivery plan; asks whether the tasks/epics are "in the right order"; suspects a task is scheduled before its prerequisite (a producer-after-consumer / dependency-inversion error like "OpenAPI after the web client that consumes it", OR a cross-cutting inherited default like observability/auth/tenancy scheduled after the feature work that inherits it — a seam-after-consumer error); wants to find missing tasks, circular dependencies, or over-fragmented epics; or wants to compact a plan to raise velocity. Also trigger on "review the roadmap", "re-derive the plan from the spec", "is this the right build order", "check the dependency graph of our epics", "which task should come first". It reads the vision + spec corpus, decomposes actors → use-cases → modules → epics → typed tasks, identifies cross-cutting inherited-default seams, builds a real dependency graph with hard + soft (seam) edges (deterministic helper), breaks cycles, topologically orders, compacts, and emits a derived roadmap PLUS a delta report against the current one — it never blindly overwrites a hand-crafted roadmap.

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

PyAutoGUI와 OpenCV를 결합하여 화면 고속 캡처, 고정밀 템플릿 매칭, 멀티스레딩 병렬 제어 및 다국어 텍스트 입력 우회를 지원하는 강력한 GUI 자동화 스킬입니다.

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

Use when the user asks how to build with OpenAI products or APIs, asks about Codex itself or choosing Codex surfaces, needs up-to-date official documentation with citations, help choosing the latest model for a use case, or model upgrade and prompt-upgrade guidance; use OpenAI docs MCP tools for non-Codex docs questions, use the Codex manual helper first for broad Codex self-knowledge, and restrict fallback browsing to official OpenAI domains.

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

Use when configuring Laravel task scheduling — cron expressions, frequency helpers, overlap prevention, maintenance mode, or output handling.

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

Join the Antigravity CLI (agy, Gemini 3.5 Flash) to the Interlateral mesh as a native CLI peer with its own tmux session, identity stamping, and the agy.js send helper. Use this instead of the Antigravity desktop-app CDP path.

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

Operate or troubleshoot Interlateral CLI mesh transport: tmux socket discovery, direct-send helpers, comms.md ledger, identity stamping, idle checks, ACK proof, and safe prompt injection. This is comms mechanics only, not a collaboration workflow.

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

Load this skill whenever the project contains static or interactive maps, embedded map widgets (Google Maps, Leaflet, Mapbox, OpenStreetMap), or any geographic visualizations. Under no circumstances embed a map without a text-based alternative conveying the same information. Absolutely always ensure map controls are keyboard-accessible and that all meaningful map content is available without the visual map.

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