'navigation' 검색 결과

When the user wants to plan, map, or restructure their website's page hierarchy, navigation, URL structure, or internal linking. Also use when the user mentions "sitemap," "site map," "visual sitemap," "site structure," "page hierarchy," "information architecture," "IA," "navigation design," "URL structure," "breadcrumbs," "internal linking strategy," "website planning," "what pages do I need," "how should I organize my site," or "site navigation." Use this whenever someone is planning what pages a website should have and how they connect. NOT for XML sitemaps (that's technical SEO — see seo-audit). For SEO audits, see seo-audit. For structured data, see schema.

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

Bevy ECS skill for navigation. Keywords: Bevy, navigation, pathfinding, ECS.

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

Bevy ECS skill for AI navigation policy. Keywords: Bevy, AI, chase, patrol, navigation, ECS.

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

Configure React Navigation 6+ stacks, tabs, and deep linking for React Native. Use when implementing React Navigation stacks, tabs, or deep linking in React Native.

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

Implement UIKit navigation, Auto Layout, and Apple Human Interface Guidelines in iOS. Use when implementing UIKit navigation, Auto Layout constraints, or HIG compliance.

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

Implement context-less navigation, named routes, and middleware using GetX. Use when building navigation with GetX routing in Flutter.

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

Implement screen routes and deep-link/App Link routing with Jetpack Compose Navigation on Android. Use when the primary task is Compose route configuration or external URL routing; defer typed-route APIs, XML/fragments, generic back-stack, and transition questions to their specific navigation skills.

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

Implements navigation patterns and routing for both frontend (React/TS) and backend (Python) including menus, tabs, breadcrumbs, client-side routing, and server-side route configuration. Use when building navigation systems or setting up routing.

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

Guide ROS/Gazebo Velodyne mobile-robot navigation with the DRL-robot-navigation TD3 implementation, including simulator setup, environment contracts, bounded training, checkpoints, and policy evaluation.

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

Connect user journeys to screens, defining the UI structure and navigation paths during PRD v0.4 User Journeys. Triggers on requests to define screens, design screen flows, map UI structure, plan navigation, or when user asks "what screens do we need?", "define screens", "screen flow", "UI structure", "information architecture", "navigation design", "wireframe planning". Consumes UJ- (User Journey Mapping), FEA- (Feature Value Planning), BR- (constraints). Outputs SCR- entries for screens and DES- entries for design system elements. Feeds v0.5 Red Team Review.

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

Hotwire Turbo for Symfony UX -- SPA-like speed with zero JavaScript. Covers Drive (navigation), Frames (partial page sections), and Streams (multi-target updates). Use when building ajax navigation, lazy-loaded sections, inline editing, pagination without reload, modals from the server, flash messages via streams, or real-time updates via Mercure/SSE. Code triggers: turbo-frame, turbo-stream, data-turbo-frame, data-turbo, data-turbo-action, turbo-stream-source, TurboStreamResponse, <twig:Turbo:Frame>, <twig:Turbo:Stream:Append>, <twig:Turbo:Stream:Replace>, turbo:before-fetch-request. Also trigger when the user asks "how to update part of the page without reload", "how to make navigation feel like SPA", "how to lazy-load a section", "how to do inline editing", "how to push real-time updates from server", "how to use Mercure with Turbo". Do NOT trigger for client-side JS behavior (use stimulus), server-rendered reactive components (use live-component), or reusable static UI (use twig-component).

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

World-class accessibility design expertise combining the inclusive design principles of Microsoft's Inclusive Design team, the technical rigor of the W3C WCAG working group, and the lived experience perspective of disability advocates. Accessibility is not a feature - it's a fundamental quality attribute that makes products usable by everyone. Great accessibility design is invisible to those who don't need it and essential to those who do. It benefits everyone: captions help in noisy environments, keyboard navigation helps power users, high contrast helps in bright sunlight. When you design for the extremes, you improve the experience for all. Accessibility is not a checklist - it's a mindset that asks "who are we excluding?" at every design decision. Use when "accessibility, a11y, wcag, screen reader, keyboard navigation, color contrast, alt text, aria, focus management, skip link, assistive technology, inclusive design, ada compliance, section 508, accessible, voiceover, nvda, jaws, tab order, focus trap, accessibility, a11y, wcag, inclusive-design, screen-reader, keyboard-navigation, color-contrast, aria, focus-management, assistive-technology" mentioned.

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

When the user wants to plan, map, or restructure their website's page hierarchy, navigation, URL structure, or internal linking. Also use when the user mentions "sitemap," "site map," "visual sitemap," "site structure," "page hierarchy," "information architecture," "IA," "navigation design," "URL structure," "breadcrumbs," "internal linking strategy," "website planning," "what pages do I need," "how should I organize my site," or "site navigation." Use this whenever someone is planning what pages a website should have and how they connect. NOT for XML sitemaps (that's technical SEO — see seo-audit). For SEO audits, see seo-audit. For structured data, see schema.

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

Use when adding a screen, a tab, a deep link, or back-navigation handling - the per-stack navigation APIs, state preservation, auth-boundary resets, and how to verify a deep link actually opens the right screen.

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

When the user wants to plan, map, or restructure their website's page hierarchy, navigation, URL structure, or internal linking. Also use when the user mentions "sitemap," "site map," "visual sitemap," "site structure," "page hierarchy," "information architecture," "IA," "navigation design," "URL structure," "breadcrumbs," "internal linking strategy," "website planning," "what pages do I need," "how should I organize my site," or "site navigation." Use this whenever someone is planning what pages a website should have and how they connect. NOT for XML sitemaps (that's technical SEO — see seo-audit). For SEO audits, see seo-audit. For structured data, see schema.

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

Use this skill when the user needs official desktop Obsidian CLI workspace, vault, tab, navigation, and utility operations, including workspace save/load/delete, tab and recent-file handling, vault info/listing, random/unique note navigation helpers, web viewer, and wordcount. Keep this skill separate from note CRUD/tasks/properties/history, runtime admin, devtools diagnostics, and Sync/Publish operations.

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

Unity 6 AI and navigation guide. Use when working with NavMesh, pathfinding, NavMeshAgent, NavMeshSurface, NavMeshObstacle, off-mesh links, or Unity Sentis (ML model inference). Covers AI navigation package, runtime NavMesh baking, and common AI patterns like state machines and behavior trees. Based on Unity 6.3 LTS documentation.

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

Flutter state management expert with BLoC/Cubit, Riverpod, Provider, and Navigation 2.0 (GoRouter). Activate on: Flutter state management, BLoC pattern, Cubit, Riverpod, Provider, GetX, GoRouter, Flutter navigation, flutter_bloc. NOT for: React Native (use react-native-architect), SwiftUI (use swiftui-data-flow-expert), Jetpack Compose (use jetpack-compose-navigation-expert).

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

Implement WCAG 2.2 AA/AAA compliance with automated testing, keyboard navigation, screen reader support, and focus management. Activate on: accessibility audit, WCAG compliance, keyboard navigation, screen reader, aria attributes, axe-core, focus trap. NOT for: design-level accessibility review (use design-accessibility-auditor), color contrast only (use css-in-js-architect).

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

Link component, useNavigate, Navigate component, router.navigate, ToOptions/NavigateOptions/LinkOptions, from/to relative navigation, activeOptions/activeProps, preloading (intent/viewport/render), preloadDelay, navigation blocking (useBlocker, Block), createLink, linkOptions helper, scroll restoration, MatchRoute.

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

When the user wants to plan, map, or restructure their website's page hierarchy, navigation, URL structure, or internal linking. Also use when the user mentions "sitemap," "site map," "visual sitemap," "site structure," "page hierarchy," "information architecture," "IA," "navigation design," "URL structure," "breadcrumbs," "internal linking strategy," "website planning," "what pages do I need," "how should I organize my site," or "site navigation." Use this whenever someone is planning what pages a website should have and how they connect. NOT for XML sitemaps (that's technical SEO — see seo-audit). For SEO audits, see seo-audit. For structured data, see schema.

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

Implements type-safe Flutter routing using AutoRoute v11 with code generation and @RoutePage annotations. Activates when setting up AutoRoute navigation, configuring AutoRouterConfig or RootStackRouter, generating route files with build_runner, using @RoutePage, @PathParam, or @QueryParam annotations, implementing AutoTabsRouter for bottom navigation tabs, adding navigation guards with AutoRouteGuard, setting up nested or child routes, handling type-safe route parameters, or migrating from string-based Navigator routing to compile-time-verified routes. Ideal for large apps requiring refactoring confidence and zero string-based routing errors.

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

Use this skill when changing routes, tabs, guards, back-button behavior, or any navigation flow including notification-tap navigation.

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

Sidebar layouts: AdwNavigationSplitView vs OverlaySplitView, sidebar widths, collapse breakpoints, navigation-sidebar styling. Use when adding a sidebar or master-detail layout to a GNOME app.

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