[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6KRDXH64V5MSFWJC7WZ1X5V":3,"skill-same:01M6KRDXH64V5MSFWJC7WZ1X5V":85},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":28,"publishedAt":39,"linkOnly":40,"markdownContent":41,"markdownBody":42,"frontMatter":43,"refName":44,"commitSha":45,"skillDirectory":46,"forksCount":47,"repositoryHtmlUrl":48,"repositoryHomepageUrl":6,"ownerHtmlUrl":49,"ownerBlogUrl":50,"ownerDescription":51,"updatedAt":52,"install":53,"resources":66},"01M6KRDXH64V5MSFWJC7WZ1X5V","responsive-ui",null,"Use when handling multiple resolutions — stretch modes, aspect ratios, DPI scaling, and mobile\u002Fdesktop adaptation","jame581\u002FGodotPrompter","jame581","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F21112138?v=4","01M6KR3KEQ9Z30WVJRR2E2ZVXE","Jan Mesarč","01M6KR3KJVRMPDSMASQPBCBVK3",964,"MIT","https:\u002F\u002Fgithub.com\u002Fjame581\u002FGodotPrompter\u002Fblob\u002Fmaster\u002Fskills\u002Fresponsive-ui\u002FSKILL.md",[18,23],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000008","测试与质量","SCENARIO","使用场景",{"categoryNo":24,"categoryName":25,"taxonomyType":26,"taxonomyTypeDesc":27},"01JBSEEDCAT000000000000032","设计师","PROFESSION","适用职业",[29,30,31,32,33,34,35,36,37,38],"ui","responsive","responsive ui","desktop","use","mobile","adaptation","scaling","modes","when","2026-11-10 10:12:30",false,"---\nname: responsive-ui\ndescription: Use when handling multiple resolutions — stretch modes, aspect ratios, DPI scaling, and mobile\u002Fdesktop adaptation\n---\n\n# Responsive UI in Godot 4.3+\n\nAll examples target Godot 4.3+ with no deprecated APIs. GDScript is shown first, then C#.\n\n> **Related skills:** **godot-ui** for Control node layout and themes, **export-pipeline** for platform-specific export settings, **godot-project-setup** for initial project resolution settings, **input-handling** for touch vs desktop input adaptation, **localization** for layout adjustments per locale, **mobile-development** for safe-area and notch handling.\n\n---\n\n## 1. Project Settings for Resolution\n\nConfigure base resolution and stretch behaviour in `Project > Project Settings > Display > Window`.\n\nKey settings and their keys in the `[display]` section of `project.godot`:\n\n| Setting | project.godot key | Recommended value |\n|---|---|---|\n| Viewport width | `window\u002Fsize\u002Fviewport_width` | `1920` (or your base design width) |\n| Viewport height | `window\u002Fsize\u002Fviewport_height` | `1080` (or your base design height) |\n| Stretch mode | `window\u002Fstretch\u002Fmode` | `canvas_items` (most games) |\n| Stretch aspect | `window\u002Fstretch\u002Faspect` | `expand` (fill screen) or `keep` (letterbox) |\n| Scale factor | `window\u002Fstretch\u002Fscale` | `1` |\n| Scale mode | `window\u002Fstretch\u002Fscale_mode` | `fractional`; `integer` for pixel art |\n\n> **Godot 4.7+:** Projects **newly created** in Godot 4.7 already default `display\u002Fwindow\u002Fstretch\u002Fmode` to `canvas_items` and `display\u002Fwindow\u002Fstretch\u002Faspect` to `expand` (previously `disabled` \u002F `keep`) — the recommendations above are now the out-of-the-box values. Projects created on older versions are unchanged (the property default is still `disabled`), so set both explicitly when upgrading. See the [4.7 migration guide](https:\u002F\u002Fdocs.godotengine.org\u002Fen\u002Flatest\u002Ftutorials\u002Fmigrating\u002Fupgrading_to_godot_4.7.html).\n\nThe engine reads these settings once at startup; changing them with `ProjectSettings.set_setting()` later has no effect. At runtime, set the matching `Window` properties instead:\n\n**GDScript:**\n\n```gdscript\n# Read current viewport size\nvar viewport_size: Vector2 = get_viewport().get_visible_rect().size\n\n# Change stretch mode at runtime (takes effect immediately)\nget_window().content_scale_mode = Window.CONTENT_SCALE_MODE_CANVAS_ITEMS\n```\n\n**C#:**\n\n```csharp\n\u002F\u002F Read current viewport size\nVector2 viewportSize = GetViewport().GetVisibleRect().Size;\n\n\u002F\u002F Change stretch mode at runtime (takes effect immediately)\nGetWindow().ContentScaleMode = Window.ContentScaleModeEnum.CanvasItems;\n```\n\n---\n\n## 2. Stretch Mode Comparison\n\n| Mode | `project.godot` value | Rendering | Best For |\n|---|---|---|---|\n| `canvas_items` | `\"canvas_items\"` | Rendered at the window's resolution; 2D nodes and UI are scaled from the design resolution, so text stays sharp | Most 2D and UI-heavy games |\n| `viewport` | `\"viewport\"` | Entire viewport is rendered at design resolution and stretched; no sub-pixel blending | Pixel art games needing pixel-perfect output |\n| `disabled` | `\"disabled\"` | No automatic scaling; the viewport is the window size, so a bigger window shows more at the same pixel size (anchors and containers still lay out) | Complex custom scaling, 3D games with a Control HUD |\n\n**When to choose each:**\n\n- **`canvas_items`** — Default recommendation. Smooth scaling at any resolution. UI built with `Control` nodes and anchors responds naturally. Text and icons stay crisp at high DPI when combined with `content_scale_factor`.\n- **`viewport`** — Locks rendering to the design resolution. Combined with integer scaling and nearest-neighbour filtering it gives a classic pixel-perfect look. Avoid for high-DPI displays unless you intentionally want chunky pixels.\n- **`disabled`** — Use when you need full manual control, e.g. a 3D game where the UI must adapt to safe areas or unusual aspect ratios without Godot scaling it.\n\n---\n\n## 3. Aspect Ratio Handling\n\nSet via `Project > Project Settings > Display > Window > Stretch > Aspect` or the `window\u002Fstretch\u002Faspect` key.\n\n| Mode | Visual Result | When to Use |\n|---|---|---|\n| `keep` | Letterbox (black bars top\u002Fbottom) or pillarbox (bars left\u002Fright) — design rect is preserved exactly | Games with a fixed layout that must not be cropped (e.g. score-based arcade, puzzle) |\n| `expand` | Screen is fully filled; the visible game area grows on wider or taller displays | Action games, platformers — more visible play area is a bonus, not a problem |\n| `keep_width` | Width is fixed; height expands on taller screens (mobile portrait) | Portrait mobile games where horizontal alignment is strict |\n| `keep_height` | Height is fixed; width expands on wider screens (landscape) | Landscape games where vertical alignment is strict (e.g. side-scroller HUD) |\n\n**`expand` with adaptive UI** is the most versatile choice for games targeting both desktop and mobile. Anchor your HUD elements to screen edges so they follow the expanded visible area.\n\n---\n\n## 4. Pixel Art Setup\n\nFor crisp pixel-art games: `Project Settings → Display → Window → Stretch → Mode = viewport`, base resolution at native pixel size (e.g., 320×180), `Window Width\u002FHeight Override` (e.g. 1280×720) for a larger window when testing. Use integer scaling (`Stretch → Scale Mode = integer`) to avoid uneven pixels.\n\n> See [references\u002Fpixel-art-setup.md](references\u002Fpixel-art-setup.md) for full project settings, integer-scaling script, nearest-neighbour filter overrides.\n\n---\n\n## 5. DPI Scaling\n\nFor retina \u002F high-DPI displays: set `content_scale_factor` to scale the entire UI proportionally. Query `DisplayServer.screen_get_dpi()` at runtime for adaptive scaling per device.\n\n> See [references\u002Fdpi-scaling.md](references\u002Fdpi-scaling.md) for the `content_scale_factor` recipe and DPI-querying patterns.\n\n---\n\n## 6. Mobile Considerations\n\nFour mobile-specific concerns: **touch input** (tap, swipe, multi-touch), **safe-area insets** (notch \u002F dynamic island avoidance), **orientation lock** (portrait\u002Flandscape pinning), **virtual keyboard** (handle show\u002Fhide to avoid covering UI).\n\n> See [references\u002Fmobile.md](references\u002Fmobile.md) for full GDScript on each concern, plus iOS \u002F Android nuances.\n\n---\n\n## 7. Adaptive Layouts\n\nAnchor presets + Container nodes do most of the work. Use `size_flags_horizontal`\u002F`vertical` (`FILL`, `EXPAND`, `SHRINK_CENTER`, `SHRINK_END`) to control how children consume container space. Detect runtime resolution changes via `get_viewport().size_changed`.\n\n> See [references\u002Fadaptive-layouts.md](references\u002Fadaptive-layouts.md) for the anchor + container strategy, resolution-change detection, and the full `size_flags` reference.\n\n---\n\n## 8. Testing Multiple Resolutions\n\n### Editor Preview Sizes\n\nIn the editor viewport, use **Editor > Editor Settings > Run > Window Placement** to start the game at specific sizes, or use the viewport size selector in the 2D editor toolbar.\n\nSet a test window size under **Project > Project Settings > Display > Window > Size > Window Width\u002FHeight Override** — the game window opens at that size while the base viewport size stays the same.\n\n### `--resolution` CLI Flag\n\nLaunch from the command line with an override resolution:\n\n```bash\n# Windows\ngodot.exe --path \"C:\u002Fprojects\u002Fmygame\" --resolution 1280x720\n\n# Linux \u002F macOS\ngodot --path \u002Fprojects\u002Fmygame --resolution 1280x720\n\n# Run an exported binary at a specific size\n.\u002Fmygame.x86_64 --resolution 375x812\n```\n\n### Common Test Resolutions\n\n| Resolution | Aspect | Common Use |\n|---|---|---|\n| `1920×1080` | 16:9 | Standard 1080p desktop \u002F TV |\n| `2560×1440` | 16:9 | 1440p high-DPI desktop |\n| `1280×720` | 16:9 | Low-end desktop \u002F minimum target |\n| `640×360` | 16:9 | Pixel art base resolution (2× of 320×180) |\n| `2732×2048` | 4:3 | iPad Pro — tests non-16:9 aspect ratios |\n| `390×844` | ~19.5:9 | iPhone 14 portrait |\n| `844×390` | ~19.5:9 | iPhone 14 landscape |\n| `1080×2400` | 20:9 | Android tall portrait |\n| `360×800` | ~20:9 | Android low-end portrait |\n\n> **Strategy:** Always test at your base design resolution, one resolution wider than 16:9 (e.g. 21:9 ultrawide), and one taller (e.g. mobile portrait). These three cases catch the most layout bugs.\n\n---\n\n## 9. Checklist\n\n- [ ] Base viewport size (`viewport_width` \u002F `viewport_height`) matches the design canvas in the editor\n- [ ] Stretch mode chosen deliberately: `canvas_items` for most games, `viewport` for pixel art\n- [ ] Aspect ratio mode chosen: `expand` unless fixed-layout content requires `keep`\n- [ ] Pixel art games use `viewport` stretch + `Nearest` texture filter + `integer` stretch scale mode\n- [ ] All HUD `Control` nodes use anchors anchored to the nearest edge, not fixed `position` values\n- [ ] `custom_minimum_size` set on buttons and interactive elements to prevent collapse below tap target size (minimum 44×44 px recommended for mobile)\n- [ ] `size_flags_horizontal` \u002F `size_flags_vertical` set to `SIZE_EXPAND_FILL` on elements that should fill space\n- [ ] `get_viewport().size_changed` signal connected where layout must respond to window resize\n- [ ] Safe area insets read from `DisplayServer.get_display_safe_area()` and applied to a root `MarginContainer`\n- [ ] `content_scale_factor` set at startup based on `DisplayServer.screen_get_dpi()` for high-DPI \u002F Retina displays\n- [ ] Touch input handled via `InputEventScreenTouch` \u002F `InputEventScreenDrag`, not mouse events alone\n- [ ] Orientation locked to the correct mode (`SCREEN_LANDSCAPE` \u002F `SCREEN_PORTRAIT`) or `SCREEN_SENSOR` where rotation is intended\n- [ ] Virtual keyboard height queried after show and used to shift UI content upward on mobile\n- [ ] Tested at minimum: design resolution, one ultra-wide (21:9), and one mobile portrait resolution\n- [ ] `--resolution` flag used in CI or playtest scripts to automate multi-resolution smoke tests\n","# Responsive UI in Godot 4.3+\n\nAll examples target Godot 4.3+ with no deprecated APIs. GDScript is shown first, then C#.\n\n> **Related skills:** **godot-ui** for Control node layout and themes, **export-pipeline** for platform-specific export settings, **godot-project-setup** for initial project resolution settings, **input-handling** for touch vs desktop input adaptation, **localization** for layout adjustments per locale, **mobile-development** for safe-area and notch handling.\n\n---\n\n## 1. Project Settings for Resolution\n\nConfigure base resolution and stretch behaviour in `Project > Project Settings > Display > Window`.\n\nKey settings and their keys in the `[display]` section of `project.godot`:\n\n| Setting | project.godot key | Recommended value |\n|---|---|---|\n| Viewport width | `window\u002Fsize\u002Fviewport_width` | `1920` (or your base design width) |\n| Viewport height | `window\u002Fsize\u002Fviewport_height` | `1080` (or your base design height) |\n| Stretch mode | `window\u002Fstretch\u002Fmode` | `canvas_items` (most games) |\n| Stretch aspect | `window\u002Fstretch\u002Faspect` | `expand` (fill screen) or `keep` (letterbox) |\n| Scale factor | `window\u002Fstretch\u002Fscale` | `1` |\n| Scale mode | `window\u002Fstretch\u002Fscale_mode` | `fractional`; `integer` for pixel art |\n\n> **Godot 4.7+:** Projects **newly created** in Godot 4.7 already default `display\u002Fwindow\u002Fstretch\u002Fmode` to `canvas_items` and `display\u002Fwindow\u002Fstretch\u002Faspect` to `expand` (previously `disabled` \u002F `keep`) — the recommendations above are now the out-of-the-box values. Projects created on older versions are unchanged (the property default is still `disabled`), so set both explicitly when upgrading. See the [4.7 migration guide](https:\u002F\u002Fdocs.godotengine.org\u002Fen\u002Flatest\u002Ftutorials\u002Fmigrating\u002Fupgrading_to_godot_4.7.html).\n\nThe engine reads these settings once at startup; changing them with `ProjectSettings.set_setting()` later has no effect. At runtime, set the matching `Window` properties instead:\n\n**GDScript:**\n\n```gdscript\n# Read current viewport size\nvar viewport_size: Vector2 = get_viewport().get_visible_rect().size\n\n# Change stretch mode at runtime (takes effect immediately)\nget_window().content_scale_mode = Window.CONTENT_SCALE_MODE_CANVAS_ITEMS\n```\n\n**C#:**\n\n```csharp\n\u002F\u002F Read current viewport size\nVector2 viewportSize = GetViewport().GetVisibleRect().Size;\n\n\u002F\u002F Change stretch mode at runtime (takes effect immediately)\nGetWindow().ContentScaleMode = Window.ContentScaleModeEnum.CanvasItems;\n```\n\n---\n\n## 2. Stretch Mode Comparison\n\n| Mode | `project.godot` value | Rendering | Best For |\n|---|---|---|---|\n| `canvas_items` | `\"canvas_items\"` | Rendered at the window's resolution; 2D nodes and UI are scaled from the design resolution, so text stays sharp | Most 2D and UI-heavy games |\n| `viewport` | `\"viewport\"` | Entire viewport is rendered at design resolution and stretched; no sub-pixel blending | Pixel art games needing pixel-perfect output |\n| `disabled` | `\"disabled\"` | No automatic scaling; the viewport is the window size, so a bigger window shows more at the same pixel size (anchors and containers still lay out) | Complex custom scaling, 3D games with a Control HUD |\n\n**When to choose each:**\n\n- **`canvas_items`** — Default recommendation. Smooth scaling at any resolution. UI built with `Control` nodes and anchors responds naturally. Text and icons stay crisp at high DPI when combined with `content_scale_factor`.\n- **`viewport`** — Locks rendering to the design resolution. Combined with integer scaling and nearest-neighbour filtering it gives a classic pixel-perfect look. Avoid for high-DPI displays unless you intentionally want chunky pixels.\n- **`disabled`** — Use when you need full manual control, e.g. a 3D game where the UI must adapt to safe areas or unusual aspect ratios without Godot scaling it.\n\n---\n\n## 3. Aspect Ratio Handling\n\nSet via `Project > Project Settings > Display > Window > Stretch > Aspect` or the `window\u002Fstretch\u002Faspect` key.\n\n| Mode | Visual Result | When to Use |\n|---|---|---|\n| `keep` | Letterbox (black bars top\u002Fbottom) or pillarbox (bars left\u002Fright) — design rect is preserved exactly | Games with a fixed layout that must not be cropped (e.g. score-based arcade, puzzle) |\n| `expand` | Screen is fully filled; the visible game area grows on wider or taller displays | Action games, platformers — more visible play area is a bonus, not a problem |\n| `keep_width` | Width is fixed; height expands on taller screens (mobile portrait) | Portrait mobile games where horizontal alignment is strict |\n| `keep_height` | Height is fixed; width expands on wider screens (landscape) | Landscape games where vertical alignment is strict (e.g. side-scroller HUD) |\n\n**`expand` with adaptive UI** is the most versatile choice for games targeting both desktop and mobile. Anchor your HUD elements to screen edges so they follow the expanded visible area.\n\n---\n\n## 4. Pixel Art Setup\n\nFor crisp pixel-art games: `Project Settings → Display → Window → Stretch → Mode = viewport`, base resolution at native pixel size (e.g., 320×180), `Window Width\u002FHeight Override` (e.g. 1280×720) for a larger window when testing. Use integer scaling (`Stretch → Scale Mode = integer`) to avoid uneven pixels.\n\n> See [references\u002Fpixel-art-setup.md](references\u002Fpixel-art-setup.md) for full project settings, integer-scaling script, nearest-neighbour filter overrides.\n\n---\n\n## 5. DPI Scaling\n\nFor retina \u002F high-DPI displays: set `content_scale_factor` to scale the entire UI proportionally. Query `DisplayServer.screen_get_dpi()` at runtime for adaptive scaling per device.\n\n> See [references\u002Fdpi-scaling.md](references\u002Fdpi-scaling.md) for the `content_scale_factor` recipe and DPI-querying patterns.\n\n---\n\n## 6. Mobile Considerations\n\nFour mobile-specific concerns: **touch input** (tap, swipe, multi-touch), **safe-area insets** (notch \u002F dynamic island avoidance), **orientation lock** (portrait\u002Flandscape pinning), **virtual keyboard** (handle show\u002Fhide to avoid covering UI).\n\n> See [references\u002Fmobile.md](references\u002Fmobile.md) for full GDScript on each concern, plus iOS \u002F Android nuances.\n\n---\n\n## 7. Adaptive Layouts\n\nAnchor presets + Container nodes do most of the work. Use `size_flags_horizontal`\u002F`vertical` (`FILL`, `EXPAND`, `SHRINK_CENTER`, `SHRINK_END`) to control how children consume container space. Detect runtime resolution changes via `get_viewport().size_changed`.\n\n> See [references\u002Fadaptive-layouts.md](references\u002Fadaptive-layouts.md) for the anchor + container strategy, resolution-change detection, and the full `size_flags` reference.\n\n---\n\n## 8. Testing Multiple Resolutions\n\n### Editor Preview Sizes\n\nIn the editor viewport, use **Editor > Editor Settings > Run > Window Placement** to start the game at specific sizes, or use the viewport size selector in the 2D editor toolbar.\n\nSet a test window size under **Project > Project Settings > Display > Window > Size > Window Width\u002FHeight Override** — the game window opens at that size while the base viewport size stays the same.\n\n### `--resolution` CLI Flag\n\nLaunch from the command line with an override resolution:\n\n```bash\n# Windows\ngodot.exe --path \"C:\u002Fprojects\u002Fmygame\" --resolution 1280x720\n\n# Linux \u002F macOS\ngodot --path \u002Fprojects\u002Fmygame --resolution 1280x720\n\n# Run an exported binary at a specific size\n.\u002Fmygame.x86_64 --resolution 375x812\n```\n\n### Common Test Resolutions\n\n| Resolution | Aspect | Common Use |\n|---|---|---|\n| `1920×1080` | 16:9 | Standard 1080p desktop \u002F TV |\n| `2560×1440` | 16:9 | 1440p high-DPI desktop |\n| `1280×720` | 16:9 | Low-end desktop \u002F minimum target |\n| `640×360` | 16:9 | Pixel art base resolution (2× of 320×180) |\n| `2732×2048` | 4:3 | iPad Pro — tests non-16:9 aspect ratios |\n| `390×844` | ~19.5:9 | iPhone 14 portrait |\n| `844×390` | ~19.5:9 | iPhone 14 landscape |\n| `1080×2400` | 20:9 | Android tall portrait |\n| `360×800` | ~20:9 | Android low-end portrait |\n\n> **Strategy:** Always test at your base design resolution, one resolution wider than 16:9 (e.g. 21:9 ultrawide), and one taller (e.g. mobile portrait). These three cases catch the most layout bugs.\n\n---\n\n## 9. Checklist\n\n- [ ] Base viewport size (`viewport_width` \u002F `viewport_height`) matches the design canvas in the editor\n- [ ] Stretch mode chosen deliberately: `canvas_items` for most games, `viewport` for pixel art\n- [ ] Aspect ratio mode chosen: `expand` unless fixed-layout content requires `keep`\n- [ ] Pixel art games use `viewport` stretch + `Nearest` texture filter + `integer` stretch scale mode\n- [ ] All HUD `Control` nodes use anchors anchored to the nearest edge, not fixed `position` values\n- [ ] `custom_minimum_size` set on buttons and interactive elements to prevent collapse below tap target size (minimum 44×44 px recommended for mobile)\n- [ ] `size_flags_horizontal` \u002F `size_flags_vertical` set to `SIZE_EXPAND_FILL` on elements that should fill space\n- [ ] `get_viewport().size_changed` signal connected where layout must respond to window resize\n- [ ] Safe area insets read from `DisplayServer.get_display_safe_area()` and applied to a root `MarginContainer`\n- [ ] `content_scale_factor` set at startup based on `DisplayServer.screen_get_dpi()` for high-DPI \u002F Retina displays\n- [ ] Touch input handled via `InputEventScreenTouch` \u002F `InputEventScreenDrag`, not mouse events alone\n- [ ] Orientation locked to the correct mode (`SCREEN_LANDSCAPE` \u002F `SCREEN_PORTRAIT`) or `SCREEN_SENSOR` where rotation is intended\n- [ ] Virtual keyboard height queried after show and used to shift UI content upward on mobile\n- [ ] Tested at minimum: design resolution, one ultra-wide (21:9), and one mobile portrait resolution\n- [ ] `--resolution` flag used in CI or playtest scripts to automate multi-resolution smoke tests\n",{"name":5,"description":7},"master","d7b26cdb5fae14d4ef7b713c5bf259395e75c3c6","skills\u002Fresponsive-ui",63,"https:\u002F\u002Fgithub.com\u002Fjame581\u002FGodotPrompter","https:\u002F\u002Fgithub.com\u002Fjame581","https:\u002F\u002Fjanmesarc.online\u002F","Software engineer. My biggest passion is game development.","2026-11-14 20:45:49",{"source":8,"skillName":5,"commands":54,"prompt":64,"zipAvailable":65},[55,58,61],{"tool":56,"command":57},"npx","npx skills add jame581\u002FGodotPrompter --skill responsive-ui",{"tool":59,"command":60},"bunx","bunx skills add jame581\u002FGodotPrompter --skill responsive-ui",{"tool":62,"command":63},"pnpm","pnpm dlx skills add jame581\u002FGodotPrompter --skill responsive-ui","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fjame581\u002FGodotPrompter\u002Fblob\u002Fmaster\u002Fskills\u002Fresponsive-ui\u002FSKILL.md",true,[67,73,77,81],{"path":68,"resourceType":69,"resourceTypeDesc":70,"sizeBytes":71,"sourceHtmlUrl":72},"references\u002Fadaptive-layouts.md","REFERENCE","参考文档",2888,"https:\u002F\u002Fgithub.com\u002Fjame581\u002FGodotPrompter\u002Fblob\u002Fmaster\u002Fskills\u002Fresponsive-ui\u002Freferences\u002Fadaptive-layouts.md",{"path":74,"resourceType":69,"resourceTypeDesc":70,"sizeBytes":75,"sourceHtmlUrl":76},"references\u002Fdpi-scaling.md",1958,"https:\u002F\u002Fgithub.com\u002Fjame581\u002FGodotPrompter\u002Fblob\u002Fmaster\u002Fskills\u002Fresponsive-ui\u002Freferences\u002Fdpi-scaling.md",{"path":78,"resourceType":69,"resourceTypeDesc":70,"sizeBytes":79,"sourceHtmlUrl":80},"references\u002Fmobile.md",4775,"https:\u002F\u002Fgithub.com\u002Fjame581\u002FGodotPrompter\u002Fblob\u002Fmaster\u002Fskills\u002Fresponsive-ui\u002Freferences\u002Fmobile.md",{"path":82,"resourceType":69,"resourceTypeDesc":70,"sizeBytes":83,"sourceHtmlUrl":84},"references\u002Fpixel-art-setup.md",2422,"https:\u002F\u002Fgithub.com\u002Fjame581\u002FGodotPrompter\u002Fblob\u002Fmaster\u002Fskills\u002Fresponsive-ui\u002Freferences\u002Fpixel-art-setup.md",[86,106,127,155,175,192],{"skillNo":87,"name":88,"nameZh":6,"description":89,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":90,"categories":91,"keywords":92,"publishedAt":39},"01M6KRFE5BR2PSD08ZKDAS66R7","xr-development","Use when building VR\u002FAR\u002FXR applications — OpenXR setup, XROrigin3D, hand tracking, controllers, passthrough, and Meta Quest deployment in Godot 4.3+","https:\u002F\u002Fgithub.com\u002Fjame581\u002FGodotPrompter\u002Fblob\u002Fmaster\u002Fskills\u002Fxr-development\u002FSKILL.md",[],[93,94,38,95,96,97,98,99,100,101,102,33,103,104,105],"xr development","development","deployment","godot","vr","setup","tracking","godot 4","ar","hand","Meta","applications","quest",{"skillNo":107,"name":108,"nameZh":6,"description":109,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":110,"categories":111,"keywords":112,"publishedAt":39},"01M6KRF8GZTG1TAS506MFBSGFC","web-services","Use when a Godot game calls a web server — HTTPRequest, downloads, REST\u002FJSON APIs, auth headers, WebSocketPeer clients, TLS, retries, and keeping secrets out of the build. Not for game networking\u002FRPCs (multiplayer-basics) or browser export (web-export)","https:\u002F\u002Fgithub.com\u002Fjame581\u002FGodotPrompter\u002Fblob\u002Fmaster\u002Fskills\u002Fweb-services\u002FSKILL.md",[],[113,114,115,116,117,118,119,120,33,38,96,121,122,123,124,125,126],"web services","web","services","tls","retries","calling","auth","downloads","clients","headers","secrets","json","build","REST",{"skillNo":128,"name":129,"nameZh":6,"description":130,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":131,"categories":132,"keywords":136,"publishedAt":39},"01M6KRF38Q4WSKAYFS56PG87T0","web-export","Use when shipping a Godot game to the browser — Web export preset options, threads vs no-threads and COOP\u002FCOEP headers, hosting on itch.io or your own server, PWA, JavaScriptBridge, user:\u002F\u002F persistence, audio and input limits, and load size","https:\u002F\u002Fgithub.com\u002Fjame581\u002FGodotPrompter\u002Fblob\u002Fmaster\u002Fskills\u002Fweb-export\u002FSKILL.md",[133],{"categoryNo":134,"categoryName":135,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000016","图像与多媒体",[114,137,138,139,140,141,142,143,122,144,145,38,146,147,148,149,150,151,33,152,153,154],"export","web export","threads","limits","shipping","size","options","hosting","input","Coop","preset","browser","game","io","load","pwa","Audio","server",{"skillNo":156,"name":157,"nameZh":6,"description":158,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":159,"categories":160,"keywords":165,"publishedAt":39},"01M6KREYFETEBH62ZTN6EZH2X3","using-godot-prompter","Bootstrap skill — establishes how to find and use GodotPrompter skills, with platform-specific tool mapping","https:\u002F\u002Fgithub.com\u002Fjame581\u002FGodotPrompter\u002Fblob\u002Fmaster\u002Fskills\u002Fusing-godot-prompter\u002FSKILL.md",[161,164],{"categoryNo":162,"categoryName":163,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发",{"categoryNo":24,"categoryName":25,"taxonomyType":26,"taxonomyTypeDesc":27},[96,166,167,168,169,33,170,171,172,173,174],"using godot prompter","find","with","bootstrap","tool","platform","mapping","how","how to",{"skillNo":176,"name":177,"nameZh":6,"description":178,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":179,"categories":180,"keywords":181,"publishedAt":39},"01M6KRER5G7EQWKGAFN8QJKQ69","tween-animation","Use when implementing tweens — property animation, method tweening, chaining, parallel sequences, easing, and common UI\u002Fgameplay motion recipes","https:\u002F\u002Fgithub.com\u002Fjame581\u002FGodotPrompter\u002Fblob\u002Fmaster\u002Fskills\u002Ftween-animation\u002FSKILL.md",[],[182,183,33,184,185,186,187,29,188,189,190,38,191],"tween animation","Animation","motion","parallel","gameplay","chaining","recipes","common","implementing","sequences",{"skillNo":193,"name":194,"nameZh":6,"description":195,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":196,"categories":197,"keywords":198,"publishedAt":39},"01M6KREKGCQMVDV8WX7HWX8BZG","state-machine","Use when building a state machine or refactoring logic into one — enum, node, and resource-based FSM patterns with trade-offs. Not for adding states to an existing one","https:\u002F\u002Fgithub.com\u002Fjame581\u002FGodotPrompter\u002Fblob\u002Fmaster\u002Fskills\u002Fstate-machine\u002FSKILL.md",[],[199,200,201,96,38,202,203,204,205,206,168,33,190,207],"state","state machine","machine","patterns","node","fsm","state machines","trade","trade-offs"]