「main」の検索結果

Extract a DDD-style ubiquitous language glossary from the current conversation, flagging ambiguities and proposing canonical terms. Saves to UBIQUITOUS_LANGUAGE.md. Use when user wants to define domain terms, build a glossary, harden terminology, create a ubiquitous language, or mentions "domain model" or "DDD".

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

Collect and analyze public X posts from keywords, hashtags, OR queries, domains, or known post URLs, then trace them to primary sources, official docs, GitHub repos, benchmarks, and reusable images. Use for launch-day reactions to a new model or product, event hashtags, keynote coverage, new-technology use cases, popularity research, or turning noisy X posts into a source-backed research note. Triggers: X で調べて, X の反応, ハッシュタグ調査, キーワードで X 検索, X 投稿からネタ探し. Not for posting or account operations on X.

Set up and operate customer workspaces: route customer updates, record meetings, track questions and actions, manage workstreams, and prepare handoffs. Use when creating or maintaining a customer workspace, processing meeting notes or updates, reviewing next actions, or preparing a handoff. Triggers: customer workspace, 顧客ワークスペース, inbox 追加, 議事録管理, 案件更新, 宿題管理, 引き継ぎ.

Run a Duck Critic producer-critic loop: you (main) keep producing the plan/code/tests and gate your own work at checkpoints with a different-model critic, revising until it passes. Use when asked for rubber duck, ラバーダック, 別モデルレビュー, second opinion, critic, or a different-model code review, design review, plan critique, or review by another model/agent harness. Not for readability refactoring or code cleanup alone.

Create reproducible animated infographic GIFs from structured data or measured results, with audience-language labels, explicit timing semantics, representative-frame QA, and a static fallback. Use when asked for GIF生成, animated infographic, 動的インフォグラフィック, 結果が流れる図, animated benchmark, or a blog/SNS animation whose displayed metrics must remain traceable to source data.

Final-mile orchestrator - commit + push + PR creation. Run after /pre-commit passes. Chains: commit -> push -> /pr-creator (artifact check + PR). Use --issue N to auto-close a GitHub issue on merge. Use --main to ship directly to main with no PR (closes issue + deletes branch).

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

Build and maintain a Stakeholder Register per PMBOK 8 Stakeholder Performance Domain. Identify stakeholders, analyze using Power/Interest grid, plan engagement strategies, and define communication cadence. Use at project initiation and whenever stakeholder landscape changes.

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

Build and maintain a project Risk Register per PMBOK 8 Risk Performance Domain. Identify risks, assess probability and impact, define response strategies, and track residual risk. Use throughout the project lifecycle — not just at planning. Do not use for operational incident response or security vulnerability scanning.

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

Build and maintain a rolling financial forecast using a 12–18 month horizon. Lock actuals, reforecast remaining periods, extend the planning window, and generate a waterfall bridge showing prior-to-new variance. Use monthly or quarterly when the organization follows a continuous planning cadence instead of annual budgets.

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

Deep OSINT reconnaissance using the MITRE ATT&CK Reconnaissance framework. Email harvesting with SMTP verification, subdomain takeover detection, certificate transparency mining, Shodan/Censys intelligence, Wayback Machine historical analysis, social media profiling, cloud storage enumeration, document metadata extraction, DNS history, credential leak checks, and passive infrastructure mapping. Uses theHarvester, amass, dnsrecon, fierce, dnstwist, dmitry, whatweb, wafw00f, exiftool, metagoofil, smtp-user-enum, swaks, waybackurls, subfinder, and crt.sh. Pure reconnaissance — no active exploitation. Produces: confidence-scored findings, infrastructure diagram, employee roster, email pattern confirmation, subdomain takeover candidates. Chains into /pentester for active testing.

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

Application-level business logic security testing for any domain. Takes an understanding-first approach: map the intended workflows before probing them. Covers: value/quantity logic abuse (negative, zero, overflow, rounding on any numeric field), workflow and state machine bypass (skipping required steps, forcing illegal state transitions, reusing one-time tokens), trust boundary violations (BOLA horizontal/vertical, BFLA, cross-tenant access, negative ownership attacks), idempotency and replay attacks (duplicate submissions, double-spend, same-reference reuse), multi-step flow integrity (checkout, registration, approval, verification), quota and rate limit bypass, time/date manipulation, and authorization code / reference number predictability. Domain-agnostic — applies to SaaS, e-commerce, banking, gaming, social platforms, APIs, or any multi-user application with stateful workflows. Chains from /pentester; chains into /param-fuzz when boundary violations or mass assignment are confirmed.

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

Execute a Kerberoasting attack to extract and systematically crack the NTLM hashes of Service Principal Name (SPN) accounts in an Active Directory environment. Uses tools like Rubeus, Impacket (GetUserSPNs), and Hashcat to achieve domain privilege escalation domain: cybersecurity

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

Build and maintain a persistent, interlinked markdown wiki (second brain / research notebook / personal knowledge base) from raw sources. Use this skill when the user wants to ingest an article / paper / note / URL / PDF into their wiki, ask a question against their wiki, lint/health-check their wiki, or set up a new wiki from a folder. Triggers include phrases like "add this to my wiki", "ingest this", "file this article", "update my notes with this", "what does my wiki say about X", "health-check my wiki", "find stale/orphan pages", or any workflow involving a `raw/` source folder, `wiki/` markdown folder, `index.md`, or `log.md`. Compatible with Obsidian vaults.

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

Establish project thesis before first code. Infer product type from domain/folder/README. Identify users, business model, pSEO strategy, AI-native dev approach. Maintain PROJECT_BRIEF.md as source of truth.

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

Use when introducing, reviewing, or renaming a top-level type, table, or domain concept; or choosing where state lives (in-memory vs persistent)

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

LlamaIndex.TS data framework for RAG, indexing, retrieval, query engines, chat engines, and agentic workflows in TypeScript

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

Cuts the next release of the unified Prisma CLI: bumps the root package.json version (on the Prisma 8 RC line: 8.0.0-rc.N → rc.N+1), propagates it to every lockstep workspace package, and opens a PR titled "chore(release): bump to <next-version>". When the maintainer merges the PR, the `Publish to npm` workflow ships @prisma/cli-engine and @prisma/cli under dist-tag `latest` (RC versions get a pre-release GitHub Release). Use when a maintainer asks to "cut the next RC", "cut the next release", "bump to the next version", "open a release PR", or "prepare a publish PR".

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

Pick up one bounded Gaia Steward maintenance dispatch, do exactly it, and hand the result back for independent verification. Use when the user says "check the steward lane", "pick up maintenance work", "is there anything for me to fix", "run the steward lane", "/gaia-steward-lane", or when a scheduled routine wakes you with no other instruction. Also use before starting speculative repository cleanup: if Steward has not found the work, the work probably does not exist.

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

Detects DNS-based tunneling and data exfiltration in DNS logs: scoring high query volume to single domains, long/high-entropy subdomains, unusual record types, and encoded payload labels. Activates for requests to hunt DNS tunneling, detect DNS exfiltration, or analyze suspicious DNS query patterns.

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

Prepare an outside contribution to Pulp or Forge that a maintainer can land with minimal rework — routing (Core vs Forge), local build and test on a plain Mac, the checks that are worth running without Shipyard/Tart/VMs, and the handoff format. Use when contributing without write access or without the maintainer CI fleet.

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

Use when moving expensive browser work off the main thread with Web Workers, SharedWorker, worker pools, Comlink, transferable objects, Vite/Webpack worker integration, or UI responsiveness fixes. Do not use for lightweight synchronous work or DOM manipulation; Chinese triggers include Web Worker, background thread, main thread blocking.

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

Use when a task needs the judgment of a Diesel Truck Mechanic — diagnosing a DPF/DEF/SCR derate or fault code, deciding whether a defect meets CVSA out-of-service criteria, sequencing a PM-A/PM-B preventive maintenance interval, triaging a roadside breakdown against downtime cost, or writing up a DOT annual inspection failure.

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

Use when a task needs the judgment of a Dispatcher — assigning a new job to the best available driver/technician in real time, managing an ETA slip and deciding who to notify, triaging a coverage gap in a service territory, sequencing a driver's remaining stops after a delay, or deciding whether a job needs to be reassigned versus the customer rescheduled.

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

Use when a task needs the judgment of a Coil Winder, Taper, or Finisher — cross-checking a mechanical turn counter against an independent method rather than trusting it blindly, maintaining wire tension within a specified range rather than by feel, avoiding wire handling that risks invisible insulation damage, or performing post-winding electrical testing rather than relying on visual/mechanical inspection alone.

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