2,397 件 ・ 関連度順
概要と使いどころ
Guide a structured thought record with tentative thinking-pattern labels and one question at a time. Use for this Bot Generator Bot template; creates drafts or simulations within its declared scope.
日本語の概要は準備中です。原文の説明を表示しています。
Draft episode outlines, show notes and guest preparation from supplied source material. Use for this Bot Generator Bot template; creates drafts or simulations within its declared scope.
日本語の概要は準備中です。原文の説明を表示しています。
Implements permissions and tenant or owner scoped resource access while preserving approved grants; not authentication or role redesign.
日本語の概要は準備中です。原文の説明を表示しています。
Maps acceptance criteria to implementation evidence, tests, and scope creep. Use during review when a diff, PR, ticket, or story includes numbered ACs.
日本語の概要は準備中です。原文の説明を表示しています。
Implement Python database access with parameterized SQL, transaction scope, connection helpers, and repository seams. Use when editing Postgres queries, repositories, transactions, pooling, or persistence boundaries in Python.
日本語の概要は準備中です。原文の説明を表示しています。
Investigate requirements via atomic AC decomposition, actor/permission matrices, and truth-table edge cases; enforce User Story standards (scope fences, platform tags, toggles). Use when writing/reviewing Stories or AC with multi-condition logic, feature toggles, or market variants (VN/MY/SG).
日本語の概要は準備中です。原文の説明を表示しています。
Write safe, structured concurrent code with Kotlin Coroutines. Use for suspend functions, coroutine scopes, cancellation, and coroutine leaks; defer Java Virtual Threads, Android WorkManager/Fragment lifecycle, Compose state hoisting, and Detekt/tooling configuration.
日本語の概要は準備中です。原文の説明を表示しています。
Core Kotlin patterns for scope functions, backing properties, and read-only collection interfaces. Use for let/apply/run/also/with choices or encapsulating mutable state; defer general language constructs, extension functions, coroutines/runCatching, Android/Room recipes, and testing/tooling setup.
日本語の概要は準備中です。原文の説明を表示しています。
Implement modern concurrency with Virtual Threads and Structured Concurrency in Java. Use when implementing Java Virtual Threads (Java 21), Structured Concurrency with StructuredTaskScope, CompletableFuture pipelines, or debugging race conditions.
日本語の概要は準備中です。原文の説明を表示しています。
Write idiomatic Kotlin 1.9+ with null safety, sealed classes, data classes, extension functions, delegates, collections, inline/reified generics, and expression syntax. Use for Kotlin language constructs, Java-to-Kotlin migration, lazy delegates, data classes, backing properties, or inline/reified generics; keep language constructs in scope even inside response models, and defer coroutine configuration, Android Context/framework, Retrofit/OkHttp client setup, and other library-specific recipes.
日本語の概要は準備中です。原文の説明を表示しています。
Standardize PRD discovery and drafting for product scope, user outcomes, requirement IDs, and acceptance criteria. Use when creating PRD, product requirements, feature specification, or acceptance criteria plan.
日本語の概要は準備中です。原文の説明を表示しています。
Drafts bounded cybersecurity engagement plans with objectives, scope, exclusions, roles, authorization, runtime controls, evidence, stop criteria, and restart gates. Use when preparing an exercise or assessment plan before execution.
日本語の概要は準備中です。原文の説明を表示しています。
NIST SP 800-61r3-aligned incident triage that preserves evidence, separates analysis from authorization, and records status. Use for incident intake, severity assessment, containment readiness, or evidence preservation; not generic debugging or unscoped response.
日本語の概要は準備中です。原文の説明を表示しています。
Standardize BRD and BRD-lite discovery for business goals, stakeholder impact, current-to-future state, and measurable value outcomes. Use when creating BRD, business case, project justification, ROI narrative, or AS-IS to TO-BE scope.
日本語の概要は準備中です。原文の説明を表示しています。
Configure Hilt dependency injection with proper scoping, modules, and constructor injection in Android. Use when changing the production Hilt graph; defer test overrides, Room wiring, navigation-specific scopes, and generic DI explanations to their specific skills.
日本語の概要は準備中です。原文の説明を表示しています。
Implements one scoped product feature or fix using existing contracts; not upgrades, performance tuning or establishing cross-cutting technical foundations.
日本語の概要は準備中です。原文の説明を表示しています。
Builds, updates or retires scoped acceptance tests and verifies execution; does not repair product code.
日本語の概要は準備中です。原文の説明を表示しています。
Designs user flows, interaction states and mockups for a defined product scope; does not implement UI code.
日本語の概要は準備中です。原文の説明を表示しています。
Quick execution for small tasks — minimal run lifecycle (start + done) with evidence recording. Full LLM capability, scoped to mechanically clear tasks.
日本語の概要は準備中です。原文の説明を表示しています。
Phoenix context design — creating/splitting contexts, Scope (1.8+); Use when editing contexts, routers, or designing…
日本語の概要は準備中です。原文の説明を表示しています。
Phoenix context design — creating/splitting contexts, Scope (1.8+), Ecto.Multi, PubSub, routers, plugs, controllers. Use when editing contexts, routers, or designing boundaries.
日本語の概要は準備中です。原文の説明を表示しています。
Scope or freeze which files Claude can edit during debugging, a refactor, or review. Use when edits should stay in specific dirs, or for a read-only investigate lock. Backed by a sentinel + PreToolUse hook.
日本語の概要は準備中です。原文の説明を表示しています。
Guide for drafting issue closure and decline responses as an open-source package maintainer. Use when helping compose a reply that says "no" to a feature request, closes an issue as won't-fix, redirects a user to a different package, explains why a design choice is intentional, or otherwise declines or closes a community contribution. Also use when the maintainer needs to explain a deprecation, point out a user misunderstanding, or communicate an effort/scope tradeoff to a contributor.
日本語の概要は準備中です。原文の説明を表示しています。
Stress-tests a fuzzy or vague feature idea before any PRD, spec, or ticket is written. TRIGGER when: the user has a fuzzy feature idea — one or two paragraphs, vague on users / scope / success — and wants to harden it, or says "grill / stress-test / pressure-test this idea." DO NOT TRIGGER when: the idea is already turned into a spec or PRD; bug fixes or refactors; the idea is hardened and you are ready to write the PRD → creating-prd.
日本語の概要は準備中です。原文の説明を表示しています。