「ble」の検索結果

Use when exposure, outcome, covariate or eligibility definitions and cutoffs need a citable basis before the protocol. Reads the data dictionary first, then maps each variable to a guideline or published definition and the database columns in a citation-backed table.

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

Use when someone has a business problem, strategic question, or founder challenge they need to think through clearly. Triggers on "I'm stuck on", "should I", "what's wrong with my", "diagnose", "strategy problem", "business problem", "founder problem", "help me think through". Runs structured consulting-style diagnostic lenses to produce a comprehensive analysis.

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

Core Blender modeling specialist for Edit Mode, modifiers, collections, precision modeling, and scene organization. Use for general 3D modeling, blockouts, cleanup, non-destructive workflows, and scene structure in Blender via MCP.

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

Use when starting any Blender asset task, planning a production pipeline, coordinating multiple disciplines, or matching a reference photo/concept art. Invoke for game-ready assets, hard surface, environment, character, creature, export, or any multi-skill Blender workflow.

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

Cosmic, eldritch, and Lovecraftian horror art direction for Blender with non-Euclidean cues, impossible scale, and incomprehensible forms.

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

Blender Geometry Nodes for procedural modeling, scatter systems, vegetation, buildings, pipes, cables, and reusable node groups. Use for procedural asset generation and instancing pipelines via MCP.

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

Art direction for puzzle and platformer games in Blender with readable interactables, jump volumes, and clear hazard language.

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

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.

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

Produces a human-readable, progressive-disclosure overview of unfamiliar code or a pull request's changes — why it exists (the real problem it solves or goal it serves for the business or a user), and from there what it does, how it flows, and where to start — so you can get up to speed before working on or reviewing it. Use when you want to understand, get oriented in, make sense of, explain, or get up to speed on a chunk of code, a file, a directory, a symbol, or a PR's changes. Writes the overview to a scratch file and changes no code. Does not review code quality or raise findings — use code-review for auditing changes or post-code-review-to-pr for posting them. Does not produce durable feature or system documentation — use project-documentation. Does not assess architecture or structural risk — use architectural-analysis. Does not diagnose bugs or root-cause failures — use investigate. Does not pace a person through the code one step at a time in conversation — use code-walkthrough.

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

Fix "count shows X but list shows empty" bugs when querying related events (comments, reactions, zaps, reposts) for Nostr addressable events (Kind 30000-39999). Use when: (1) REST API shows engagement count > 0 but WebSocket query returns empty, (2) Comments/reactions exist but app shows "No comments yet" or similar, (3) Working with NIP-22 comments, NIP-25 reactions, or NIP-18 reposts on Kind 34235/34236 video events or other addressable events. Root cause: clients may reference addressable events using either E tag (event ID) or A tag (kind:pubkey:d-tag format), and querying only one tag misses events tagged with the other.

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

Fix duplicate Nostr events (Kind 30000+ parameterized replaceable events) caused by missing d-tag. Use when: (1) Same content appears multiple times on relay for same pubkey, (2) Events aren't being replaced/updated as expected, (3) Publishing NIP-71 video events (Kind 34236) or other addressable events and seeing duplicates. The d-tag is REQUIRED for addressability - without it, each publish creates a new non-replaceable event.

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

Fix silent data loss when mutating Nostr replaceable events (Kind 0 profile, Kind 3 contact/follow list, Kind 10002 relay list, etc.) in client apps. Use when: (1) Following someone wipes the user's entire follow list, (2) Updating profile metadata loses existing fields, (3) Fresh browser session or mobile login causes data loss on first action, (4) Replaceable event mutation uses stale or null cached state. Root cause: Nostr replaceable events are full-replace (no partial update), so publishing based on stale/unloaded cache overwrites the canonical version. Applies to any Nostr client using React, Flutter, or similar reactive frameworks where query state may not be loaded when a mutation fires.

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

Fix ClickHouse Cloud migration failures caused by multi-table RENAME statements. Use when: (1) Migration fails with "Database X is Shared, it does not support renaming of multiple tables in single query", (2) golang-migrate or other migration tools show dirty database version after a table-swap migration on ClickHouse Cloud, (3) Schema migration works on self-hosted ClickHouse but fails on ClickHouse Cloud. ClickHouse Cloud uses SharedMergeTree engine which has restrictions not present in regular MergeTree.

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

Create iMandalArt 2.2 pure-text 3x3 Mandala index cards with a five-character center axis, eight orthogonal surrounding angles labeled Ⓐ-Ⓗ, compact title cells such as Ⓐ健康復節, hard-line CJK layout, optional の字型 ordering, and 井字號 compass ordering. Use when the user asks for iMandalArt, iMandalart, I MandalArt, の字型, ◊字型, 井字號, 中國城市方位, 64＋8＋1, 手機方形曼陀羅, 正方形九宮索引卡, 五字定格, ◎中心, Ⓐ-Ⓗ 九宮卡, TheBrain/Cerebro preview-safe hard-line cards, or a square 3x3 card that is not a Markdown table, visible-border PE2 card, or 81-cell Mandala.

Convert Chinese or mixed-language text, iMandalArt cards, Obsidian 九宮, 表格, Mandala notes, or eight-domain outlines into a Markdown 3x3 nine-grid table with an ◎ center, then copy, save, append, or hand it to apps that render Markdown tables such as Obsidian and AIDA. Use when the user asks for Markdown 九宮格, Obsidian 九宮, Markdown table 九宮, 曼陀羅表格, nine-grid clipboard, AIDA table output, or conversion between Markdown 九宮, iMandalArt, and 81-grid workflows.

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

Build and validate Eevee 3D-to-2D rendering with discrete Shader to RGB lighting bands and a deformation-following inverted-hull Geometry Nodes outline. Use for anime, cel-shaded, toon, hand-drawn, or stylized real-time assets that need editable object-space outlines in Blender Eevee.

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

Analyze reference-image illumination and build accountable Blender lighting from shadow direction, shadow length, softness, exposed faces, environment fill, bounce, practical sources, and material response. Use for reference matching, daylight, interiors, exterior environments, product scenes, atmospheric lighting, or any task where lights must be physically and visually justified instead of added as arbitrary fill or rim lights.

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

Define production-ready visual intent for Blender scenes and standalone assets, including focal hierarchy, depth layers, visual flow, scale and repetition rhythm, camera mobility, representation fidelity, and performance budgets. Use for original or reference-guided Blender work before construction choices are executed, especially environments, architecture, products, hero assets, or scenes whose modeling quality depends on coordinated spatial design rather than isolated objects.

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

Recommends appropriate software design patterns based on problem descriptions, requirements, or code scenarios. Use when designing software architecture, refactoring code, solving common design problems, or choosing between design approaches. Analyzes the problem context and suggests suitable creational, structural, behavioral, architectural, or concurrency patterns with implementation guidance and trade-off analysis.

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

Profile and debug Hermes sessions from their JSONL transcripts. Find a session and its subagents, build a queryable event table, summarize the work as a hierarchical table of contents, break down wall time, inference, tools, tokens, and estimated cost per agent, identify errors and improvement opportunities, and export a shareable Perfetto trace. Use when a user wants to inspect what a Hermes session did, debug agent or subagent activity, understand session cost or latency, create a session timeline, generate a trace, or learn how to improve the next agent run.

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

Apply stable-baselines3 in reproducible local data workflows with version-aware APIs, explicit assumptions, and validation. Use when the user chooses stable-baselines3 or its strengths fit the task.

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

Master problem solver for systematic problem-solving methodologies. Use when the user asks to talk to Dr. Quinn or requests the Master Problem Solver.

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

Apply systematic problem-solving methodologies to complex challenges. Use when the user says "guide me through structured problem solving" or "I want to crack this challenge with guided problem solving techniques"

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

Automate motion capture and tracking workflows in Blender with Python. Use when the user wants to import BVH or FBX mocap data, retarget motion to armatures, track camera or object motion from video, solve camera motion, clean up motion capture data, or script any tracking pipeline in Blender.

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