「directions」の検索結果

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.

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

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'.

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

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.

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

GStack design-shotgun method for rapidly exploring multiple distinct design directions before choosing one to implement or polish.

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

Throwaway design probe for logic, state models, UI variations, and affordances before production work. Use when the user wants to prototype, sanity-check a model, make something playable, compare UI directions, or explore a design before ln-spec/ln-plan/ln-scope.

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

Sweeps the last 24 hours of email, chat messages and meeting transcripts for commitments in both directions, what the user promised others and what others promised the user, reconciles them against a running commitments ledger (open, done, overdue), lists overdue items first and returns the updated ledger plus a proposed task list as Markdown for the user to save. Use when the user asks to "check my commitments", "what did I promise", "what am I owed", "did anything slip" or "run the commitment sweep". Do not use for a general morning summary of mail, calendar and mentions, use custom-daily-brief instead. Drafts for human review; never approves, authorises or signs off.

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

Azure Maps SDK for .NET. Location-based services including geocoding, routing, rendering, geolocation, and weather. Use for address search, directions, map tiles, IP geolocation, and weather data.

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

Azure Maps SDK for .NET. Location-based services including geocoding, routing, rendering, geolocation, and weather. Use for address search, directions, map tiles, IP geolocation, and weather data.

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

Azure Maps SDK for .NET. Location-based services including geocoding, routing, rendering, geolocation, and weather. Use for address search, directions, map tiles, IP geolocation, and weather data.

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

Orchestrator + builder for distinctive, production-grade frontends that don't look AI-generated. Derives stack and design context from product-soul/PRD/specs, then runs the anti-slop chain — explore distinct directions, lock a DESIGN.md system, build from golden examples with mandatory polish + every interactive/empty/loading/error state, then review. Load when the user asks to build a UI, design a frontend, build a landing page or dashboard or web app, beautify or redesign a page, make a UI look premium/playful/editorial, says "build me a frontend", "make this not look AI-generated", "design this interface", "give this real polish", or "frontend design". Routes to design-direction, design-system, design-review.

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

Azure Maps SDK for .NET. Location-based services including geocoding, routing, rendering, geolocation, and weather. Use for address search, directions, map tiles, IP geolocation, and weather data.

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

Orchestrator that runs one UI brief through all four ui-* posture skills in parallel, then picks and merges a winner. Use when a screen matters enough to explore several directions, or the user says 'build it a few ways', 'design options', 'bake-off', 'show me variations', or 'compare approaches'.

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

Azure Maps SDK for .NET. Location-based services including geocoding, routing, rendering, geolocation, and weather. Use for address search, directions, map tiles, IP geolocation, and weather data.

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

Geocode, POIs, routes, timezones via OpenStreetMap/OSRM.

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

Requires OFOX_API_KEY — create one at https://app.ofox.ai, plus a publicly reachable reference video the user is authorized to use. Use when a user has a rough 3D white-model, clay, wireframe, blockout, previs, or animatic clip and wants a finished visual treatment that preserves its shot order, cut timing, camera framing, spatial layout, and motion directions. Distinguishes that structure-preserving job from a continuation beginning at the reference's final state. Do not use for two still endpoints (keyframe-animation), for appending and locally joining a new ending (video-extend-edit), or when still-image references must be combined with the video in one request — first/last-frame anchors conflict with video references in the shipped core, while mixed image/video references are untested.

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

Refute-before-prove research discipline: automated counterexample sweeps before any formalization, meter-integrity audits for information-bound experiments, mutation-tested model checkers, pre-registered commit-or-cut gates for speculative directions, wrong-turn reporting, and numeric-claim provenance. Use when validating any new theorem, bound, equilibrium, or security claim; when building or trusting a checker, simulator, or experiment; or when deciding whether a speculative research direction lives or dies. NOT for exploratory brainstorming, product prioritization, writing style, or literature review.

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