[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7CGEHM75PSP9K3AE57518M3":3,"skill-same:01M7CGEHM75PSP9K3AE57518M3":55},{"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":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":24,"commitSha":25,"skillDirectory":26,"forksCount":14,"repositoryHtmlUrl":27,"repositoryHomepageUrl":6,"ownerHtmlUrl":28,"ownerBlogUrl":29,"ownerDescription":6,"updatedAt":30,"install":31,"resources":44},"01M7CGEHM75PSP9K3AE57518M3","window-management",null,"Customize macOS SwiftUI windows and scene behavior. Use when tuning window chrome, drag regions, placement, restoration, launch behavior, or borderless windows.","rossboyd\u002Fquickque","rossboyd","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F3195729?v=4","01M7CG99NTNRFV0TWTZX9JY9CQ","rbyd","01M7CG99PH4WEP5P45VTBNPDB0",0,"MIT","https:\u002F\u002Fgithub.com\u002Frossboyd\u002Fquickque\u002Fblob\u002Fmain\u002F.codex\u002F.tmp\u002Fplugins\u002Fplugins\u002Fbuild-macos-apps\u002Fskills\u002Fwindow-management\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: window-management\ndescription: Customize macOS SwiftUI windows and scene behavior. Use when tuning window chrome, drag regions, placement, restoration, launch behavior, or borderless windows.\n---\n\n# Window Management\n\n## Overview\n\nUse this skill to tailor each SwiftUI window to its job. Start by identifying\nwhich scene owns the window (`Window`, `WindowGroup`, or a dedicated utility\nscene), then customize the toolbar\u002Ftitle area, background material, resize and\nrestoration behavior, and initial or zoomed placement.\n\nPrefer scene and window modifiers over ad hoc AppKit bridges when SwiftUI offers\nthe behavior directly. Keep each window purpose-built: a main browser window, an\nAbout window, and a media player window usually want different chrome,\nresizability, restoration, and placement rules.\n\nThese APIs are macOS 15+ SwiftUI window\u002Fscene customizations. For older\ndeployment targets, expect to use more AppKit bridging or availability guards.\n\n## Workflow\n\n1. Inspect the relevant scene declaration and classify the window role:\n   main app navigation, inspector\u002Fdetail utility, About\u002Fsupport window, media\n   playback window, welcome window, or a borderless custom surface.\n2. Adjust toolbar and title presentation to match the content.\n3. If the toolbar background or entire toolbar is hidden, make sure the window\n   still has a usable drag region.\n4. Refine window behavior for that role: minimize availability, restoration,\n   resize expectations, and whether the window should appear at launch.\n5. Set default placement for newly opened windows and ideal placement for zoom\n   behavior when content and display size matter.\n6. Build and launch the app with `build-run-debug` to verify the result in\n   a real foreground `.app` bundle.\n7. If SwiftUI scene\u002Fwindow modifiers are not enough, switch to `appkit-interop`\n   for a narrow `NSWindow` bridge rather than spreading AppKit through the view\n   tree.\n\n## Toolbar And Title\n\n- Use `.toolbar(removing: .title)` when the window title should stay associated\n  with the window for accessibility and menus, but not be visibly drawn in the\n  title bar.\n- Use `.toolbarBackgroundVisibility(.hidden, for: .windowToolbar)` when large\n  media or hero content should visually extend to the top edge of the window.\n- If the window still needs close\u002Fminimize\u002Ffull-screen controls, remove only the\n  title and toolbar background. If the toolbar should disappear entirely, use\n  `.toolbarVisibility(.hidden, for: .windowToolbar)` instead.\n- Remove custom toolbar backgrounds and manually painted titlebar fills before\n  layering new SwiftUI toolbar APIs on top.\n- Keep the window's logical title meaningful even if hidden; the system can\n  still use it for accessibility and menu items. These are visual changes only.\n\n## Drag Regions\n\n- If a toolbar background is hidden or the toolbar is removed entirely, use\n  `WindowDragGesture()` to extend the draggable area into your content.\n- Attach the gesture to a transparent overlay or non-interactive header region\n  that does not steal gestures from real controls.\n- For a media player with custom playback controls, insert the drag overlay\n  between the video content and the controls so AVKit or transport controls keep\n  receiving input.\n- Pair the drag gesture with `.allowsWindowActivationEvents(true)` so clicking\n  and immediately dragging a background window still activates and moves it.\n\n## Background And Materials\n\n- Use `.containerBackground(.thickMaterial, for: .window)` when a utility window\n  or About window should replace the default window background with a subtle\n  frosted material.\n- Prefer system materials for stylized windows instead of hardcoded translucent\n  colors.\n- Use this especially for fixed-content utility windows where a softer backdrop\n  is part of the design.\n\n## Window Behavior\n\n- Use `.windowMinimizeBehavior(.disabled)` for always-reachable utility windows\n  such as a custom About window where minimizing adds little value.\n- Disable the green zoom control through fixed sizing or window constraints when\n  the window's content has one intended size.\n- Use `.restorationBehavior(.disabled)` for windows that should not reopen on\n  next launch, such as About panels, transient support\u002Finfo windows, or\n  first-run welcome surfaces.\n- Keep state restoration enabled for primary document or navigation windows when\n  reopening prior size and position is desirable.\n- By default, SwiftUI respects the user's system-wide macOS state restoration\n  setting. Use `restorationBehavior(...)` only when a specific window should\n  intentionally opt into or out of that system behavior.\n- Use `.defaultLaunchBehavior(.presented)` for windows that should appear first\n  on launch, such as a welcome window, and choose that behavior intentionally\n  rather than relying on side effects from scene creation order.\n\n## Window Placement\n\n- Use `.defaultWindowPlacement { content, context in ... }` to control the\n  initial size and optional position of newly opened windows.\n- Inside the placement closure, call `content.sizeThatFits(.unspecified)` to get\n  the content's ideal size.\n- Read `context.defaultDisplay.visibleRect` to get the display's usable region\n  after accounting for the menu bar and Dock.\n- Return `WindowPlacement(size: size)` with a size clamped to the visible rect\n  when media or document content may be larger than the display. If no position\n  is provided, the window is centered by default.\n- Use `.windowIdealPlacement { content, context in ... }` to control what\n  happens when the user chooses Zoom from the Window menu or Option-clicks the\n  green toolbar button. For media windows, preserve aspect ratio and grow to the\n  largest size that fits the display.\n- Treat default placement and ideal placement as separate policies:\n  - default placement controls where a new window first appears,\n  - ideal placement controls how large a zoomed window should become.\n- Always consider external displays and rotated\u002Fnarrow screens when sizing\n  player windows or document windows from content dimensions.\n\n## Borderless And Specialized Windows\n\n- Use `.windowStyle(.plain)` for borderless or highly custom chrome windows, but\n  make sure the content still provides a clear drag\u002Fmove affordance and visible\n  context.\n- For a borderless player, HUD, or welcome window, decide upfront whether losing\n  standard titlebar affordances is worth the custom presentation.\n- Keep one clear path back to regular window management if the plain style makes\n  the window feel invisible or hard to move.\n\nFor concrete window modifier examples, read `references\u002Fapi-snippets.md`.\n\n## Review Checklist\n\n- The scene type matches the window's role and lifecycle.\n- Hidden titles still leave a meaningful logical title for accessibility and\n  menus.\n- Toolbar background removal is intentional and does not hurt titlebar legibility\n  or window control placement.\n- Windows with hidden or removed toolbars still have a reliable drag region and\n  support click-then-drag activation from the background.\n- Utility windows have restoration\u002Fminimize behavior that matches their purpose.\n- Restoration overrides are used only when a scene should intentionally differ\n  from the user's system-wide setting.\n- Default and ideal placement use `content.sizeThatFits(.unspecified)` and\n  `context.defaultDisplay.visibleRect` when content\u002Fdisplay size matters.\n- Media windows preserve aspect ratio and fit on small or rotated displays.\n- Borderless windows still have a usable move\u002Fdrag affordance.\n\n## Guardrails\n\n- Do not use `.toolbar(removing: .title)` just to hide a title you forgot to set.\n  Keep the underlying window title meaningful.\n- Do not hide the toolbar background or the whole toolbar without replacing the\n  lost drag affordance.\n- Do not disable restoration on the main document\u002Fnavigation window unless the\n  user explicitly wants a fresh-start app every launch.\n- Do not hardcode one monitor size or assume a single-display setup when sizing\n  player windows.\n- Do not reach for `NSWindow` mutation before checking whether\n  `.windowMinimizeBehavior`, `.restorationBehavior`, `.defaultWindowPlacement`,\n  `.windowIdealPlacement`, `.windowStyle`, or `.defaultLaunchBehavior` already\n  solve the problem.\n- Do not leave a plain borderless window without any obvious drag or close path.\n\n## When To Use Other Skills\n\n- Use `swiftui-patterns` for broader scene, commands, settings, sidebar,\n  and inspector architecture.\n- Use `liquid-glass` when the main question is modern macOS visual treatment,\n  Liquid Glass, or system material adoption.\n- Use `appkit-interop` if a custom window behavior truly requires `NSWindow`,\n  `NSPanel`, or responder-chain control.\n- Use `build-run-debug` to launch and verify the resulting windows.\n","# Window Management\n\n## Overview\n\nUse this skill to tailor each SwiftUI window to its job. Start by identifying\nwhich scene owns the window (`Window`, `WindowGroup`, or a dedicated utility\nscene), then customize the toolbar\u002Ftitle area, background material, resize and\nrestoration behavior, and initial or zoomed placement.\n\nPrefer scene and window modifiers over ad hoc AppKit bridges when SwiftUI offers\nthe behavior directly. Keep each window purpose-built: a main browser window, an\nAbout window, and a media player window usually want different chrome,\nresizability, restoration, and placement rules.\n\nThese APIs are macOS 15+ SwiftUI window\u002Fscene customizations. For older\ndeployment targets, expect to use more AppKit bridging or availability guards.\n\n## Workflow\n\n1. Inspect the relevant scene declaration and classify the window role:\n   main app navigation, inspector\u002Fdetail utility, About\u002Fsupport window, media\n   playback window, welcome window, or a borderless custom surface.\n2. Adjust toolbar and title presentation to match the content.\n3. If the toolbar background or entire toolbar is hidden, make sure the window\n   still has a usable drag region.\n4. Refine window behavior for that role: minimize availability, restoration,\n   resize expectations, and whether the window should appear at launch.\n5. Set default placement for newly opened windows and ideal placement for zoom\n   behavior when content and display size matter.\n6. Build and launch the app with `build-run-debug` to verify the result in\n   a real foreground `.app` bundle.\n7. If SwiftUI scene\u002Fwindow modifiers are not enough, switch to `appkit-interop`\n   for a narrow `NSWindow` bridge rather than spreading AppKit through the view\n   tree.\n\n## Toolbar And Title\n\n- Use `.toolbar(removing: .title)` when the window title should stay associated\n  with the window for accessibility and menus, but not be visibly drawn in the\n  title bar.\n- Use `.toolbarBackgroundVisibility(.hidden, for: .windowToolbar)` when large\n  media or hero content should visually extend to the top edge of the window.\n- If the window still needs close\u002Fminimize\u002Ffull-screen controls, remove only the\n  title and toolbar background. If the toolbar should disappear entirely, use\n  `.toolbarVisibility(.hidden, for: .windowToolbar)` instead.\n- Remove custom toolbar backgrounds and manually painted titlebar fills before\n  layering new SwiftUI toolbar APIs on top.\n- Keep the window's logical title meaningful even if hidden; the system can\n  still use it for accessibility and menu items. These are visual changes only.\n\n## Drag Regions\n\n- If a toolbar background is hidden or the toolbar is removed entirely, use\n  `WindowDragGesture()` to extend the draggable area into your content.\n- Attach the gesture to a transparent overlay or non-interactive header region\n  that does not steal gestures from real controls.\n- For a media player with custom playback controls, insert the drag overlay\n  between the video content and the controls so AVKit or transport controls keep\n  receiving input.\n- Pair the drag gesture with `.allowsWindowActivationEvents(true)` so clicking\n  and immediately dragging a background window still activates and moves it.\n\n## Background And Materials\n\n- Use `.containerBackground(.thickMaterial, for: .window)` when a utility window\n  or About window should replace the default window background with a subtle\n  frosted material.\n- Prefer system materials for stylized windows instead of hardcoded translucent\n  colors.\n- Use this especially for fixed-content utility windows where a softer backdrop\n  is part of the design.\n\n## Window Behavior\n\n- Use `.windowMinimizeBehavior(.disabled)` for always-reachable utility windows\n  such as a custom About window where minimizing adds little value.\n- Disable the green zoom control through fixed sizing or window constraints when\n  the window's content has one intended size.\n- Use `.restorationBehavior(.disabled)` for windows that should not reopen on\n  next launch, such as About panels, transient support\u002Finfo windows, or\n  first-run welcome surfaces.\n- Keep state restoration enabled for primary document or navigation windows when\n  reopening prior size and position is desirable.\n- By default, SwiftUI respects the user's system-wide macOS state restoration\n  setting. Use `restorationBehavior(...)` only when a specific window should\n  intentionally opt into or out of that system behavior.\n- Use `.defaultLaunchBehavior(.presented)` for windows that should appear first\n  on launch, such as a welcome window, and choose that behavior intentionally\n  rather than relying on side effects from scene creation order.\n\n## Window Placement\n\n- Use `.defaultWindowPlacement { content, context in ... }` to control the\n  initial size and optional position of newly opened windows.\n- Inside the placement closure, call `content.sizeThatFits(.unspecified)` to get\n  the content's ideal size.\n- Read `context.defaultDisplay.visibleRect` to get the display's usable region\n  after accounting for the menu bar and Dock.\n- Return `WindowPlacement(size: size)` with a size clamped to the visible rect\n  when media or document content may be larger than the display. If no position\n  is provided, the window is centered by default.\n- Use `.windowIdealPlacement { content, context in ... }` to control what\n  happens when the user chooses Zoom from the Window menu or Option-clicks the\n  green toolbar button. For media windows, preserve aspect ratio and grow to the\n  largest size that fits the display.\n- Treat default placement and ideal placement as separate policies:\n  - default placement controls where a new window first appears,\n  - ideal placement controls how large a zoomed window should become.\n- Always consider external displays and rotated\u002Fnarrow screens when sizing\n  player windows or document windows from content dimensions.\n\n## Borderless And Specialized Windows\n\n- Use `.windowStyle(.plain)` for borderless or highly custom chrome windows, but\n  make sure the content still provides a clear drag\u002Fmove affordance and visible\n  context.\n- For a borderless player, HUD, or welcome window, decide upfront whether losing\n  standard titlebar affordances is worth the custom presentation.\n- Keep one clear path back to regular window management if the plain style makes\n  the window feel invisible or hard to move.\n\nFor concrete window modifier examples, read `references\u002Fapi-snippets.md`.\n\n## Review Checklist\n\n- The scene type matches the window's role and lifecycle.\n- Hidden titles still leave a meaningful logical title for accessibility and\n  menus.\n- Toolbar background removal is intentional and does not hurt titlebar legibility\n  or window control placement.\n- Windows with hidden or removed toolbars still have a reliable drag region and\n  support click-then-drag activation from the background.\n- Utility windows have restoration\u002Fminimize behavior that matches their purpose.\n- Restoration overrides are used only when a scene should intentionally differ\n  from the user's system-wide setting.\n- Default and ideal placement use `content.sizeThatFits(.unspecified)` and\n  `context.defaultDisplay.visibleRect` when content\u002Fdisplay size matters.\n- Media windows preserve aspect ratio and fit on small or rotated displays.\n- Borderless windows still have a usable move\u002Fdrag affordance.\n\n## Guardrails\n\n- Do not use `.toolbar(removing: .title)` just to hide a title you forgot to set.\n  Keep the underlying window title meaningful.\n- Do not hide the toolbar background or the whole toolbar without replacing the\n  lost drag affordance.\n- Do not disable restoration on the main document\u002Fnavigation window unless the\n  user explicitly wants a fresh-start app every launch.\n- Do not hardcode one monitor size or assume a single-display setup when sizing\n  player windows.\n- Do not reach for `NSWindow` mutation before checking whether\n  `.windowMinimizeBehavior`, `.restorationBehavior`, `.defaultWindowPlacement`,\n  `.windowIdealPlacement`, `.windowStyle`, or `.defaultLaunchBehavior` already\n  solve the problem.\n- Do not leave a plain borderless window without any obvious drag or close path.\n\n## When To Use Other Skills\n\n- Use `swiftui-patterns` for broader scene, commands, settings, sidebar,\n  and inspector architecture.\n- Use `liquid-glass` when the main question is modern macOS visual treatment,\n  Liquid Glass, or system material adoption.\n- Use `appkit-interop` if a custom window behavior truly requires `NSWindow`,\n  `NSPanel`, or responder-chain control.\n- Use `build-run-debug` to launch and verify the resulting windows.\n",{"name":5,"description":7},"main","907b1d897cc6743f7f133f8ea2021e1331b0b020",".codex\u002F.tmp\u002Fplugins\u002Fplugins\u002Fbuild-macos-apps\u002Fskills\u002Fwindow-management","https:\u002F\u002Fgithub.com\u002Frossboyd\u002Fquickque","https:\u002F\u002Fgithub.com\u002Frossboyd","www.bigideasgroup.co.uk","2026-09-22 02:03:50",{"source":8,"skillName":5,"commands":32,"prompt":42,"zipAvailable":43},[33,36,39],{"tool":34,"command":35},"npx","npx skills add rossboyd\u002Fquickque --skill window-management",{"tool":37,"command":38},"bunx","bunx skills add rossboyd\u002Fquickque --skill window-management",{"tool":40,"command":41},"pnpm","pnpm dlx skills add rossboyd\u002Fquickque --skill window-management","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Frossboyd\u002Fquickque\u002Fblob\u002Fmain\u002F.codex\u002F.tmp\u002Fplugins\u002Fplugins\u002Fbuild-macos-apps\u002Fskills\u002Fwindow-management\u002FSKILL.md",true,[45,51],{"path":46,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":49,"sourceHtmlUrl":50},"agents\u002Fopenai.yaml","REFERENCE","参考文档",418,"https:\u002F\u002Fgithub.com\u002Frossboyd\u002Fquickque\u002Fblob\u002Fmain\u002F.codex\u002F.tmp\u002Fplugins\u002Fplugins\u002Fbuild-macos-apps\u002Fskills\u002Fwindow-management\u002Fagents\u002Fopenai.yaml",{"path":52,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":53,"sourceHtmlUrl":54},"references\u002Fapi-snippets.md",1601,"https:\u002F\u002Fgithub.com\u002Frossboyd\u002Fquickque\u002Fblob\u002Fmain\u002F.codex\u002F.tmp\u002Fplugins\u002Fplugins\u002Fbuild-macos-apps\u002Fskills\u002Fwindow-management\u002Freferences\u002Fapi-snippets.md",[56,65,73,80,87,95],{"skillNo":57,"name":58,"nameZh":6,"description":59,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":60,"licenseFileUrl":61,"sourceHtmlUrl":62,"categories":63,"keywords":64,"publishedAt":19},"01M7CJSS21K09H3ZQZMPFR4ZAG","skill-installer","Install Codex skills into $CODEX_HOME\u002Fskills from a curated list or a GitHub repo path. Use when a user asks to list installable skills, install a curated skill, or install a skill from another repo (including private repos).","Apache-2.0","https:\u002F\u002Fgithub.com\u002Frossboyd\u002Fquickque\u002Fblob\u002Fmain\u002F.codex\u002Fskills\u002F.system\u002Fskill-installer\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Frossboyd\u002Fquickque\u002Fblob\u002Fmain\u002F.codex\u002Fskills\u002F.system\u002Fskill-installer\u002FSKILL.md",[],[],{"skillNo":66,"name":67,"nameZh":6,"description":68,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":60,"licenseFileUrl":69,"sourceHtmlUrl":70,"categories":71,"keywords":72,"publishedAt":19},"01M7CJSM1F4E7RBXCS3C18EFBY","skill-creator","Create or update a Codex skill with appropriately scoped instructions and any needed supporting resources.","https:\u002F\u002Fgithub.com\u002Frossboyd\u002Fquickque\u002Fblob\u002Fmain\u002F.codex\u002Fskills\u002F.system\u002Fskill-creator\u002Flicense.txt","https:\u002F\u002Fgithub.com\u002Frossboyd\u002Fquickque\u002Fblob\u002Fmain\u002F.codex\u002Fskills\u002F.system\u002Fskill-creator\u002FSKILL.md",[],[],{"skillNo":74,"name":75,"nameZh":6,"description":76,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":77,"categories":78,"keywords":79,"publishedAt":19},"01M7CJSGF2PJM504Q6TZCNT27C","review-agent","Perform a read-only, defect-first review of a specified code change and return every actionable finding. Use when another agent delegates review of uncommitted changes, a base-branch diff, a commit, or custom review instructions.","https:\u002F\u002Fgithub.com\u002Frossboyd\u002Fquickque\u002Fblob\u002Fmain\u002F.codex\u002Fskills\u002F.system\u002Freview-agent\u002FSKILL.md",[],[],{"skillNo":81,"name":82,"nameZh":6,"description":83,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":84,"categories":85,"keywords":86,"publishedAt":19},"01M7CJSBQTPFEQYZF4VWS7QZ3N","plugin-creator","Create and scaffold plugin directories for Codex with a required `.codex-plugin\u002Fplugin.json`, optional plugin folders\u002Ffiles, valid manifest defaults, and personal-marketplace entries by default. Use when Codex needs to create a new personal plugin, add optional plugin structure, generate or update marketplace entries for plugin ordering and availability metadata, or update an existing local plugin during development with the CLI-driven cachebuster and reinstall flow.","https:\u002F\u002Fgithub.com\u002Frossboyd\u002Fquickque\u002Fblob\u002Fmain\u002F.codex\u002Fskills\u002F.system\u002Fplugin-creator\u002FSKILL.md",[],[],{"skillNo":88,"name":89,"nameZh":6,"description":90,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":60,"licenseFileUrl":91,"sourceHtmlUrl":92,"categories":93,"keywords":94,"publishedAt":19},"01M7CJS5BHJZKA16353PVZGC50","openai-docs","Use for Codex models\u002Fpricing, scheduled tasks, skills, settings, setup, troubleshooting, customization, automations, and self-knowledge—including 'you,' 'your,' 'this app,' or 'this coding agent' when they refer to Codex—and for OpenAI APIs\u002Fproducts and ChatGPT Work. Also use for model choice\u002Fmigration, prompting, SDKs, Responses, Realtime, agents, evals, and Chat\u002FWork\u002FCodex comparisons. Do not use for generic app\u002Fsoftware tasks that merely mention Codex.","https:\u002F\u002Fgithub.com\u002Frossboyd\u002Fquickque\u002Fblob\u002Fmain\u002F.codex\u002Fskills\u002F.system\u002Fopenai-docs\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Frossboyd\u002Fquickque\u002Fblob\u002Fmain\u002F.codex\u002Fskills\u002F.system\u002Fopenai-docs\u002FSKILL.md",[],[],{"skillNo":96,"name":97,"nameZh":6,"description":98,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":60,"licenseFileUrl":99,"sourceHtmlUrl":100,"categories":101,"keywords":102,"publishedAt":19},"01M7CJRY1FC048P3RF4YQZ6J8B","imagegen","Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output should be a bitmap asset rather than repo-native code or vector. Do not use when the task is better handled by editing existing SVG\u002Fvector\u002Fcode-native assets, extending an established icon or logo system, or building the visual directly in HTML\u002FCSS\u002Fcanvas.","https:\u002F\u002Fgithub.com\u002Frossboyd\u002Fquickque\u002Fblob\u002Fmain\u002F.codex\u002Fskills\u002F.system\u002Fimagegen\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Frossboyd\u002Fquickque\u002Fblob\u002Fmain\u002F.codex\u002Fskills\u002F.system\u002Fimagegen\u002FSKILL.md",[],[]]