'directions' 검색 결과

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

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

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.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

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

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

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

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

tasteskill v2, the anti-slop frontend skill. Art direction for websites, distilled from a study of 247 curated gallery sites (One Page Love, Awwwards Sites of the Day). Deals researched directions (idea, composition, type, palette, photographs, section blueprints) from a library, enforces a strict no-slop house style with a real-browser inspector, and runs a look-and-fix loop on screenshots. Use this whenever you build, design, redesign, restyle, polish or review a landing page, marketing site, portfolio, product page, one-pager, hero or any public-facing web page, in any stack (HTML/CSS, React, Next.js, Vue, Svelte, Astro, Tailwind) — also when the user says a page looks generic, templated, "AI-made", sloppy, or asks to make it look designed, premium, award-level or less like every other site. Not for dashboards or app screens.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Generate three radically distinct, on-trend brand concepts for any app or product and present them as a single no-scroll hero webpage — a bento "brand book" (logo + tagline, in-app screen, out-of-home, merch, palette, type, voice) that assembles itself with a staggered pop on every toggle. Grounded in 2024-2026 design trends, not safe defaults. Triggers: "brand kit", "brand book", "brand concepts", "show me a few directions", "make it look like an agency did it", "build a brand for my app".

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Cascades strategy from boardroom to individual contributor. Detects and fixes misalignment between company goals and team execution. Covers strategy articulation, cascade mapping, orphan goal detection, silo identification, communication gap analysis, and realignment protocols. Use when teams are pulling in different directions, OKRs don't connect, departments optimize locally at company expense, or when user mentions alignment, strategy cascade, silo, conflicting OKRs, or strategy communication.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

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.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

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.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

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.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

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.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

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.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.