Every product will be AI-powered. The question is whether you'll build it right or ship a demo that falls apart in production.
日本語の概要は準備中です。原文の説明を表示しています。
6,024 件 ・ 関連度順
概要と使いどころ
Every product will be AI-powered. The question is whether you'll build it right or ship a demo that falls apart in production.
日本語の概要は準備中です。原文の説明を表示しています。
Pedagogical patterns for enriching notebooks (GameTheory model). Use when adding interpretations, structuring notebooks, or creating educational content in Jupyter notebooks.
日本語の概要は準備中です。原文の説明を表示しています。
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.
日本語の概要は準備中です。原文の説明を表示しています。
Implement randomization methods for RCTs. Use when user mentions: random assignment, treatment allocation, stratification, blocking, permutation randomization, cluster randomization, randomization balance, misfit handling, re-randomization.
日本語の概要は準備中です。原文の説明を表示しています。
Systematic literature review methodology for social science research. Use when conducting systematic reviews, research synthesis, meta-analyses, scoping reviews, or comprehensive literature searches across economics, political science, sociology, education, public health, and development. Produces structured notebook cells with search strategy, evidence table, thematic synthesis, and gap analysis.
日本語の概要は準備中です。原文の説明を表示しています。
研究倫理審査の要否判定、申請準備、差し戻し対応を支援する
Teacher mode — turn a session recap / article / docs / concept / piece of code / bug into an incremental mini-course with comprehension checks, quizzes, and an auto-saved summary note. Invoke /teach [topic or URL]. Triggers — "explain it like a teacher", "walk me through what we did", "turn this into a lesson", "quiz me", "teach me", "let's learn this together".
日本語の概要は準備中です。原文の説明を表示しています。
Council — 5 independent AI perspectives + mutual critique + synthesis (adapted from karpathy/llm-council for Claude Code). For high-stakes decisions where the answer does NOT follow unambiguously from the data — go/no-go before real consequences, critiquing a methodology, choosing between competing approaches, pressure-testing a conclusion you're attached to, designing risk controls. NOT for log/data analysis (the council has no data access) and not for factual lookups. Triggers — "convene the council", "run it past the council", "go/no-go", "pressure-test this".
日本語の概要は準備中です。原文の説明を表示しています。
DRY (Don't Repeat Yourself) review rules for code reviews: find the same knowledge — a rule, a constant, a parser, a validation, a protocol detail — implemented in several places that must change together, and tell it apart from code that merely looks alike. Use when reviewing a diff, a pull request or recent changes for duplication, on "DRY review", "is this duplicated", "copy-paste check", or when a review checklist asks for DRY. Pair it with the solid skill for design and with owasp-asvs for security.
日本語の概要は準備中です。原文の説明を表示しています。
Makes the agent reconsider a task it just handed back to the human and find a way to do it itself, checking memory, CLI tools, skills, MCP servers, and documentation in turn. Use when the user invokes `/you` or `$you`, or replies that the agent should do something itself rather than asking them.
日本語の概要は準備中です。原文の説明を表示しています。
Find and address all unresolved GitHub PR review comments on the current branch's pull request. Use when the user asks to resolve, address, respond to, or reply to PR review feedback — whether from humans, CodeRabbit, Copilot, Claude Code reviewer, or any other source. Triggers on "/rr", "resolve review comments", "address PR feedback", "reply to review threads", "deal with CodeRabbit", etc.
日本語の概要は準備中です。原文の説明を表示しています。
Creates a Beads issue for a described problem or piece of work without doing the work itself. Use when the user invokes `/bc` or `$bc`, or asks to file, log, or record a bead for something. To also carry out the work, use the `bx` skill instead.
日本語の概要は準備中です。原文の説明を表示しています。
Structures git branches and worktrees: keeps unrelated changes on separate branches, isolates each in its own worktree created so the repository's setup runs, records dependencies with git-machete, and recombines them into a temporary mixdown branch for local testing. Use before creating any branch or worktree in a codebase that works on more than one branch, including branching off the default branch to start a change; when starting work in a fork, clone, or third-party checkout; when choosing what a new branch should be based on; when a branch is growing a second unrelated concern; when deciding whether to stack branches or keep them independent; when preparing a change for a pull request or patch submission; when handed an existing worktree or branch to implement and commit in a fork; or when a local build needs several in-progress branches combined. Not needed where the repository clearly commits everything to the trunk, or holds notes or personal data rather than code.
日本語の概要は準備中です。原文の説明を表示しています。
CEO/founder-mode plan review. Rethink the problem, find the 10-star product, challenge premises.
日本語の概要は準備中です。原文の説明を表示しています。
Systematic debugging methodology. Reproduce → Isolate → Hypothesize → Verify → Fix → Confirm.
日本語の概要は準備中です。原文の説明を表示しています。
Drive a real browser from the command line — open pages, snapshot the interactive elements as refs, click and fill by ref, read text, run JS, screenshot. Use when a task needs a live browser: checking a page renders, walking a login or checkout flow, scraping something that only exists after JavaScript runs, or reproducing a UI bug.
日本語の概要は準備中です。原文の説明を表示しています。
Use when stuck on a hard problem, decomposition is unclear, a related problem is needed, or explicit looking-back review will improve transfer. NOT for routine execution with a known procedure, rote checklist work, or domain questions that need specialized subject matter expertise instead of heuristic search.
日本語の概要は準備中です。原文の説明を表示しています。
Patterns for vibe coding that produce production-quality output instead of garbage. Covers prompt engineering for AI coding, verification without reading every line, accept/reject/refine decision framework, architectural guardrails, context management (CLAUDE.md, .cursor/rules), TDD-driven vibe coding, screenshot-driven development, diff review discipline, and the anti-patterns that destroy quality. Activate on: "vibe coding", "AI coding quality", "Claude Code workflow", "AI-assisted development", "how to use AI for coding", "coding with AI", "agentic engineering workflow", "AI code quality", "vibe code without garbage", "production quality AI code", "CLAUDE.md setup", "cursorrules setup", "pre-commit hooks for AI", "TDD with AI", "test-driven vibe coding". NOT for: multi-person collaborative coding sessions (use cooperative-vibe-coding), building AI/LLM applications (use ai-engineer), prompt engineering for non-coding LLM use cases (use prompt-engineer).
日本語の概要は準備中です。原文の説明を表示しています。
Foundational theory for process-oriented concurrency through synchronous message-passing, applicable to multi-agent coordination and parallel decomposition
日本語の概要は準備中です。原文の説明を表示しています。
Structured interview and observation techniques for extracting tacit knowledge from domain experts
日本語の概要は準備中です。原文の説明を表示しています。
Domain-Driven Design methodology using bounded contexts, ubiquitous language, and strategic/tactical patterns
日本語の概要は準備中です。原文の説明を表示しています。
Digital equity and trauma-informed design for marginalized populations. Activate on "accessibility", "offline-first", "trauma-informed", "reentry", "recovery population", "shared device", "unstable phone", "digital equity", "design justice", "low-literacy", "intermittent access". NOT for general UX, marketing optimization, or enterprise SaaS design.
日本語の概要は準備中です。原文の説明を表示しています。
Star schema, snowflake schema, SCD types, and Kimball methodology for analytical data modeling. Activate on: dimensional model, star schema, snowflake schema, SCD, fact table, dimension table, Kimball, grain, surrogate key. NOT for: dbt implementation (use dbt-analytics-engineer), warehouse tuning (use data-warehouse-optimizer).
日本語の概要は準備中です。原文の説明を表示しています。
Review of Cognitive Systems Engineering applications and current practice in safety-critical domains
日本語の概要は準備中です。原文の説明を表示しています。