1,585 件 ・ 関連度順
概要と使いどころ
[AUTO-INVOKE] MUST be invoked BEFORE writing or modifying any test files (*.t.sol). Covers test structure, naming conventions, coverage requirements, fuzz testing, and Foundry cheatcodes. Trigger: any task involving creating, editing, or running Solidity tests.
日本語の概要は準備中です。原文の説明を表示しています。
Enter explore mode - a thinking partner for exploring ideas, investigating problems, and clarifying requirements. Use when the user wants to think through something before or during a change.
日本語の概要は準備中です。原文の説明を表示しています。
Grill the user about a requirement, decision, or idea before implementation, then produce an actionable planning report without writing code. Use when the user wants to clarify requirements, stress-test an idea, compare approaches, or plan before coding.
日本語の概要は準備中です。原文の説明を表示しています。
Generate a custom checklist for the current feature based on user requirements.
日本語の概要は準備中です。原文の説明を表示しています。
Guidance for selecting appropriate AI model (sonnet vs haiku) based on task complexity, reasoning requirements, and performance needs. Use when implementing agents or justifying model selection.
日本語の概要は準備中です。原文の説明を表示しています。
Launches specialized Claude agents for targeted tasks. Analyzes requirements, selects appropriate agent, and executes with optimized configuration.
日本語の概要は準備中です。原文の説明を表示しています。
Assess MotherDuck security, permissions, isolation, residency, and compliance requirements against documented controls.
日本語の概要は準備中です。原文の説明を表示しています。
Use only for reviewing completed Biome PRs, branches, commit ranges, diffs, or working trees against business logic and requirements. Excludes broad code-quality and process audits, triage, reproduction, and implementation.
日本語の概要は準備中です。原文の説明を表示しています。
Use this skill whenever writing or editing Rust `//`, `///`, or `//!` comments in Biome, including comments added incidentally and end-user rustdoc inside lint/assist declarations. For lint/assist rustdoc, also load lint-rule-development for content requirements. Do not use for formatter handling of comments in user code.
日本語の概要は準備中です。原文の説明を表示しています。
INVOKE THIS SKILL before creating any PR to ensure compliance with branch naming, changelog requirements, and reviewer assignment.
日本語の概要は準備中です。原文の説明を表示しています。
编写完整的 Product Requirements Document（PRD）时使用。适用于完整功能模块需求定义、需求评审材料、给下游工作流的交付包。优先输出可开发、可测试、可验收的 14 节标准 PRD。
日本語の概要は準備中です。原文の説明を表示しています。
You MUST use this before any creative work or multi-step task. Explores intent, requirements, and design before implementation. Then documents the plan before coding.
日本語の概要は準備中です。原文の説明を表示しています。
Strategic codebase re-direction when requirements change, architecture doesn't fit, or tech debt blocks progress. TRIZ-powered pivot protocol for large codebases.
日本語の概要は準備中です。原文の説明を表示しています。
Evaluate an HLD note against linked ADRs, requirements, and architecture principles across six dimensions
日本語の概要は準備中です。原文の説明を表示しています。
Resolves AWS SDK v3 client commands and service endpoint signatures using @aws-sdk/client-* packages. Maps IAM permission requirements to specific API calls with request/response type definitions.
日本語の概要は準備中です。原文の説明を表示しています。
Scan Python requirements and environments for known vulnerable or malicious packages before they move further through delivery or promotion workflows.
日本語の概要は準備中です。原文の説明を表示しています。
Generates and validates Ansible playbooks from infrastructure requirements. Uses ansible-lint for validation and queries Ansible Galaxy API for discovering certified roles and collections.
日本語の概要は準備中です。原文の説明を表示しています。
Bridges asset requirements from motion design specs to production-ready assets. Parses specs for required assets, recommends free/paid sources, provides format conversion guidance, generates validated import code, and offers asset preparation checklists. Use when preparing assets for Remotion projects or when asked "where to get assets", "how to prepare assets", "asset formats for Remotion".
日本語の概要は準備中です。原文の説明を表示しています。
Expert product specification and documentation writer. Use when creating PRDs, user stories, acceptance criteria, technical specifications, API documentation, edge case analysis, design handoff docs, feature flag plans, or success metrics. Covers the full spectrum from high-level requirements to implementation-ready specifications.
日本語の概要は準備中です。原文の説明を表示しています。
Generates render and output configuration for Remotion videos. Focuses ONLY on output settings, codec, format, quality, resolution. Input is target platform/quality requirements. Output is RENDER_CONFIG.md with Remotion render settings.
日本語の概要は準備中です。原文の説明を表示しています。
Generate structured software specifications for features, bug fixes, and products. Use when the user wants to create a spec, PRD, feature brief, requirements document, or when starting any new implementation that needs a specification first. Invoke via /spec-writer or when the user says "write a spec", "spec this out", "create a spec", "I need a spec for...", or describes a feature they want to build. Produces adaptive-complexity specs with Job Stories, Gherkin acceptance criteria, and three-tier boundaries. Output is a markdown file ready for agent execution or human review.
日本語の概要は準備中です。原文の説明を表示しています。
Verification methodology and gate checklist for the tdmcp Connectors Directory submission — run the docs build, build and inspect the .mcpb bundle, sweep for stale .dxt references, and cross-check the form-answer draft against the real requirements. Use to validate the submission package before a human submits, by executing commands and quoting evidence, not by trusting that work was done.
日本語の概要は準備中です。原文の説明を表示しています。
生成芯片/IP 产品需求文档（PRD），从市场需求和技术约束输出专业 PRD 规范。Generate Product Requirements Document for chip/IP design projects. Trigger: /bb-prd, PRD生成, 产品需求文档, 芯片立项, IP需求, chiplet specification
日本語の概要は準備中です。原文の説明を表示しています。
Nature-style engineering manuscript reviewer skill for testing devices, robots, platforms, systems, algorithms embodied in physical systems and engineering methods against requirements, validation, benchmarking, uncertainty, robustness and failure modes.
日本語の概要は準備中です。原文の説明を表示しています。