「direction」の検索結果

Work up Malignancy-Associated Hypercalcemia (MAH) — distinguish humoral hypercalcemia of malignancy (HHM, PTHrP-driven), local osteolytic hypercalcemia, 1,25(OH)2D-mediated lymphoma hypercalcemia, ectopic PTH secretion, and multiple myeloma — and pick the right confirmatory tests and therapy direction. Trigger when a clinician asks "is this hypercalcemia from cancer", "PTHrP positive what now", "hypercalcemia in lung cancer / breast cancer / lymphoma / myeloma", "humoral hypercalcemia of malignancy", "MAH workup", or any hypercalcemia case with suppressed PTH and a known or suspected malignancy.

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

Draft a Workflow Phase 4 technical spec from an intake (and optionally a BRD + scout + research memo). The spec defines how the system will change: design (C4 + UML + dependency graph in PlantUML), data, APIs, tests, rollout, rollback. Output lives at `docs/specs/<slug>.md`. Never self-approves — approval happens via `/approve-direction`.

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

Extract every PlantUML block from docs/specs/<slug>.md and render each to SVG under docs/specs/_rendered/<slug>/, with an index.md listing them in order. Run this before /approve-direction so the reviewer sees pictures instead of raw PlantUML.

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

End-to-end workflow orchestrator. Walks the 11-phase pipeline, invoking each phase skill in order inside an internal loop, yielding at consent gates (/approve-direction, /approve-swarm, /grant-commit), and exiting cleanly on yield/failure/done. Decides swarm-vs-solo at Phase 6. Auto-loops /tdd on integrate failures that don't require a spec change. The harness_continuation Stop hook is a safety net that re-fires harness only when the loop exited mid-flow.

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

Orchestrates `impeccable` for every design task inside a workflow phase. Captures intent in natural language, classifies it (design / development / copy), translates design intents into a sequence of impeccable subcommand invocations, runs them in main context with state persistence at `.claude/state/design/<slug>.json`, and returns a structured report. ALWAYS invokes `impeccable` under the hood for the underlying design move; never picks aesthetic direction itself; never writes product code directly. Per CLAUDE.md Article X.2, all design tasks in workflow phases route through this skill.

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

Azure AI Voice Live SDK for .NET. Build real-time voice AI applications with bidirectional WebSocket communication.

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

Azure AI Voice Live SDK for JavaScript/TypeScript. Build real-time voice AI applications with bidirectional WebSocket communication.

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

Build real-time voice AI applications with bidirectional WebSocket communication.

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

Azure AI VoiceLive SDK for Java. Real-time bidirectional voice conversations with AI assistants using WebSocket.

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

Use for strategic thinking, or when the user must choose a direction under constraints: "where should we focus?", "how do we win?", "roadmap for next year", "what should we not do?". Ends in explicit bets and risks. Skip for step-by-step implementation.

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

Shape or update a rolling-wave engineering project before slice preparation. Use when the user wants to start a rolling-wave project, define the finish line, clarify success criteria, create or update docs/rolling-wave/{project}/project.md, sketch a broad roadmap, or interrogate project-level direction without implementation details.

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

Turn briefs, mockups, and product context into Stitch UI screens, design systems, variants, prototypes, Tailwind-friendly HTML, and screenshots. Use when the user wants to explore a screen, edit an existing Stitch project, compare visual directions, build a multi-screen prototype, or save local design/code-export artifacts from natural-language input.

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

Generate beautiful, on-brand HTML artifacts — reports, diagrams, diff reviews, slide decks, plans, recaps, dashboards. Loads on creation intents ("create a plan", "make me an implementation plan", "generate a diagram", "build a slide deck", "draft a recap", "visualize this", "render this as HTML", "make me a status update") and exploration intents ("show me three layouts", "explore document shapes", "compare visual treatments", "explore a new design system", "compare replacement brand directions") and iteration intents ("make this beautiful", "polish this report", "make this less generic", "design this", "theme this", "use my brand", "iterate on this design", "review this artifact", "make this bolder", "make this quieter", "simplify this design", "animate this", "improve the look of", "give this a refresh"). Captures brand from the user's codebase, asking, or live site, then applies it to every artifact.

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

Get detailed routing between two points with distance, duration, and optional turn-by-turn directions.

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

Plan the UX and UI for a feature before writing code. Runs a structured discovery interview, then produces a design brief that guides implementation. Use during the planning phase to establish design direction, constraints, and strategy before any code is written.

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

Explore a flow or layout with 3+ disposable lo-fi greyscale wireframes on a named axis. Use when the user wants to sketch directions or explore structure.

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

Use when stakeholders pull a decision in different directions — frames each lens, builds a trade-off matrix, surfaces the cost of every choice — even if the user just says 'PO and ops disagree'.

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

Use when a diff may break system boundaries, dependency direction, or cross-service contracts — fifth judge dispatched by /review-changes alongside the four standard judges.

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

Use when creating or editing raster images, visual concepts, product graphics, launch assets, diagrams, posters, thumbnails, reference sheets, UI mock images, or image prompts that need source-grounded claims, readable text, brand direction, and post-generation verification.

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

Project-level visual direction skill for WeChat Official Account articles. Use when planning, improving, diversifying, generating, or reviewing cover images and body illustrations for公众号文章, especially when Codex image generation should be used without being constrained by repetitive preset-based illustration skills.

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

Create or refresh screenshot-led product hero images, localized interface captures, and image-led README sections for GitHub repositories. Use whenever a user asks to make a GitHub README show a GUI product visually, add software screenshots, design a README hero image, reproduce a screenshot-collage reference, or prepare repository-bound visual documentation. For GUI applications, default to the deterministic product-proof split hero with real software screenshots unless the user explicitly requests another visual direction.

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

Create distinctive, production-grade frontend interfaces with high design quality. Use when the user asks to build web components, pages, or applications and the visual direction matters as much as the code quality.

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

Non-animation creative direction for HyperFrames videos. Use for design spec (frame.md / design.md) handling, palettes, typography, narration, beat planning, audio-reactive visuals, composition patterns, and brand / style decisions. For atomic motion patterns and scene blueprints, use `hyperframes-animation`.

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

Use this skill when planning, redesigning, or reviewing Xiaohongshu carousel visuals, covers, 3:4 image posts, page-by-page visual direction, image-generation prompts, style selection, layout critique, or XHS captions. It acts as a senior visual director for 小红书图文, not a generic copywriting assistant.

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