4,246 件 ・ 関連度順
概要と使いどころ
Diff a live page's accessibility violations against a baseline — by default compares uncommitted changes (stash-based), or pass --branch [<name>] to diff against a branch. Reports only new violations introduced, violations fixed, and pre-existing count. Use `scan` for a full audit with no diffing.
日本語の概要は準備中です。原文の説明を表示しています。
Use this skill whenever the user wants to create, read, edit, or manipulate Word documents (.docx files) or Word templates (.dotx files). Triggers include: any mention of 'Word doc', 'word document', '.docx', '.dotx', or requests to produce professional documents with formatting like tables of contents, headings, page numbers, or letterheads. Also use when extracting or reorganizing content from .docx or .dotx files, inserting or replacing images in documents, performing find-and-replace in Word files, working with tracked changes or comments, or converting content into a polished Word document. If the user asks for a 'report', 'memo', 'letter', 'template', or similar deliverable as a Word or .docx file, use this skill. Do NOT use for PDFs, spreadsheets, Google Docs, or general coding tasks unrelated to document generation.
日本語の概要は準備中です。原文の説明を表示しています。
Use when implementing Kafka, RabbitMQ, Pulsar, or JMS producers and consumers in Spring Boot 3. Covers event contracts, idempotency, retries, dead-letter handling, ordering, and outbox delivery.
日本語の概要は準備中です。原文の説明を表示しています。
Use when implementing Kafka, RabbitMQ, Pulsar, or JMS producers and consumers in Spring Boot 4. Covers modular starters, event contracts, idempotency, retries, dead letters, and outbox delivery.
日本語の概要は準備中です。原文の説明を表示しています。
Analyze liquid markets with a strict ICT/SMC framework that combines multi-timeframe bias, liquidity sweeps, displacement, close-confirmed MSS/BOS, FVG/OB/Breaker/OTE retracements, premium-discount location, session timing, invalidation, targets, and risk-to-reward. Use for ICT chart reviews, live-market analysis, OHLCV scans, or validating a user's trade thesis. Return an auditable setup status and conditional plan; do not use for generic indicator analysis, order execution, or claims of proven institutional intent.
日本語の概要は準備中です。原文の説明を表示しています。
Pre-deployment privacy compliance checklist for AI/ML systems covering DPIA completion, lawful basis verification, transparency notices, human oversight mechanisms, bias testing, and post-deployment monitoring setup. Keywords: AI deployment, privacy checklist, go-live, model deployment, compliance gate.
日本語の概要は準備中です。原文の説明を表示しています。
Guides privacy audit report writing including executive summary drafting, findings classification (critical, high, medium, low), evidence referencing, root cause analysis documentation, recommendation formulation, management response tracking, and report distribution protocols. Covers report structure from scope definition through appendices and sign-off. Keywords: audit report, findings documentation, executive summary, recommendations, report structure, privacy audit deliverables.
日本語の概要は準備中です。原文の説明を表示しています。
Create or update a runbook for an operational scenario — an incident an alert fires for, a recurring scheduled task, or a known failure mode on a live service — using a consistent template. Use when writing, drafting, authoring, or updating a runbook for an alert, incident, on-call procedure, scheduled maintenance, or operational SOP. Applies a YAGNI preflight requiring the scenario to be real before producing the runbook. Does not produce feature or system documentation — use project-documentation. Does not record architectural decisions — use architectural-decision-record. Does not create coding standards — use coding-standard.
日本語の概要は準備中です。原文の説明を表示しています。
Builds a feature implementation plan from an existing feature specification (or equivalent context) through a facilitated team conversation. Use when the user wants to plan how to implement, build, deliver, or ship a feature that has already been specified. Does not specify what the feature should do — use plan-a-feature first. Does not design the contract for an interface — use design-an-api. Does not refine or stress-test an already-written plan — use iterative-plan-review. Runs its resolution rounds to completion and holds its questions until after they finish; to review each round as it lands, use pairing.
日本語の概要は準備中です。原文の説明を表示しています。
Designs the contract for an API change inside one codebase — a component's props, a function surface, URL or query parameters, an event payload, or a module boundary — through a discovery pass, an options document with one recommendation, a question round, and an adversarial validation round, with every element of the contract justified from one stated goal. Use when you want to design, shape, decide, or nail down an interface, contract, signature, or API change for a capability you can already describe, sized for roughly one pull request. Produces a design document and changes no code. Does not specify what a feature should do — use plan-a-feature. Does not plan delivery or sequencing — use plan-implementation. Does not assess the architecture of existing code — use architectural-analysis. Does not write the code — use tdd. Does not restructure existing code — use refactor. Runs its rounds without pausing for review; to review each round as it lands, use pairing.
日本語の概要は準備中です。原文の説明を表示しています。
Discovers the core attributes of the current code repository and its projects — languages, frameworks, tooling, and where things live — and writes a concise reference section directly into the project's AGENTS.md or CLAUDE.md for other skills, agents, and hooks to consume. Use when scanning, analyzing, or detecting the project's technology stack, build tools, or repository structure. Does not create or update project documentation — use project-documentation for writing feature or system docs.
日本語の概要は準備中です。原文の説明を表示しています。
Break a trusted implementation plan (or other provided context) into independently-grabbable, atomic work items, written to a single work-items.md file. Use when the user wants to convert a plan into work items, create implementation tickets or tasks, divide a plan into work units, or break the plan down into grabbable pieces. Do not use when there is no implementation plan yet or the plan is not yet trusted — use plan-implementation to produce the plan or iterative-plan-review to harden it first. Does not sequence work into demoable delivery phases — use plan-a-phased-build for that. Does not write code — use tdd to implement a work item.
日本語の概要は準備中です。原文の説明を表示しています。
Create or improve procedural risograph still art, illustrations, posters, print series and images in this repo. Develops reference-led composition, perspective, pose and ink plates; delivers a native-resolution PNG and self-contained Canvas 2D source. Use for standalone still requests; use riso-film for moving work.
日本語の概要は準備中です。原文の説明を表示しています。
Design, build or improve procedural risograph animations and videos in this repo, including narrative films, abstract shorts, motion effects and visual inspection. Delivers self-contained Canvas 2D HTML and a verified MP4. For standalone still art use riso-still; for sound use riso-score. Not for editing tools/.
日本語の概要は準備中です。原文の説明を表示しています。
Internal ClaudeMap runtime for turning a repository into a live architecture map and driving that map during walkthroughs. Prefer the public commands in .claude/commands for normal use.
日本語の概要は準備中です。原文の説明を表示しています。
Create original short videos using the 实拍印刷层接力｜人物、商品细节与字卡共同推进 Creative DNA for MiniMax H3 or Seedance 2.0. Use when the user wants this causal, camera, motion, rhythm, or payoff structure with new subjects and surfaces.
日本語の概要は準備中です。原文の説明を表示しています。
Turn a narration line, knowledge point, opinion, story beat, or abstract concept into a Seedance 2.0 editorial paper-collage clip with a clear visual metaphor, approved final composition, tactile stop-motion assembly, controlled paper texture, purposeful depth, and synchronized collage sound effects. Use for 4–15 second explainer or B-roll clips; not for realistic presenter ads or editable-layer delivery.
日本語の概要は準備中です。原文の説明を表示しています。
Plan and prompt a stylized 3D animated short for Seedance 2.0 with stable character identities, environment continuity, causal story beats, shot-specific performance, camera, sound, and clip handoffs. Use when a story needs one 4–15 second generation or a longer multi-clip plan; not for photoreal live action, a single still, or generic prompt polishing.
日本語の概要は準備中です。原文の説明を表示しています。
Design a Seedance 2.0 science, education, or general-knowledge explainer using layered handmade papercraft, miniature diorama depth, physical paper mechanisms, clear knowledge beats, restrained miniature camera, tactile sound, and stable reference roles. Use for one 4–15 second clip or a longer multi-clip plan; not for flat vector cartoons, live action, or paper-texture-only styling.
日本語の概要は準備中です。原文の説明を表示しています。
Use when scanning code for security vulnerabilities. Use when user says "scan security", "kiểm tra bảo mật", "security audit", "review security", or invokes `/vbs-scan-security`. Auto-delegates to sub-agents for large scans (>20 main-language files OR >30 total OR >14 days). Outputs bilingual reports (vi/en). Optional `--auto-fix` (agentic patch + verify loop) and `--sca` (live CVE lookup via OSV.dev).
日本語の概要は準備中です。原文の説明を表示しています。
Use when scanning code for security vulnerabilities. Use when user says "scan security", "kiểm tra bảo mật", "security audit", "review security", or invokes `/vbs-scan-security`. For large scans (>20 main-language files OR >30 total OR >14 days) processes chunks sequentially. Outputs bilingual reports (vi/en). Optional `--auto-fix` (agentic patch + verify loop) and `--sca` (live CVE lookup via OSV.dev).
日本語の概要は準備中です。原文の説明を表示しています。
Investigate how a concept, code path, application, network flow, system, incident, document, or local artifact actually works, then deliver a two-depth visual HTML explainer with a dead-simple big-picture first layer and source-backed technical depth behind it. Use when the user invokes $xray, asks how something works under the hood, wants a module or app behavior traced across boundaries, requests web, code, network, or safe static artifact research before explanation, or asks for an evidence-backed explainer. Do not use for answer-only definitions, general web design, full codebase audits, or invasive binary reverse engineering without explicit authorization.
日本語の概要は準備中です。原文の説明を表示しています。
Review whether a repository's coding-agent harness can reliably carry work from intent through controlled execution, verification, delivery, and learning. Use when asked to assess agent readiness, repeated agent failures, Rules/Skills/Hooks/Memory effectiveness, missing validation or recovery loops, or whether a harness repair improved later outcomes. Do not use for code-only audits, AGENTS-only audits, individual skill reliability reviews, or executing the task itself.
日本語の概要は準備中です。原文の説明を表示しています。
Use claudraband CLI and daemon workflows programmatically to send prompts, resume sessions, inspect status, and manage live session state. Use when running, scripting, or automating Claude Code via claudraband/`cband`, including startup prompt handling, `--connect` daemon mode, and ACP sessions.
日本語の概要は準備中です。原文の説明を表示しています。