apple-desktop-ui
/apple-desktop-ui
Projektuje i sprawdza interfejsy macOS w SwiftUI i AppKit: materiały, panele ustawień, okna dialogowe, paski narzędzi i fokus klawiatury.
- Autor
- xiaolongnk ↗
- Repozytorium
- apple-desktop-ui ↗
- Licencja
- MIT
- Ostatnia zmiana repozytorium
- 25.10.2026
Ocena i bezpieczeństwo
- Pliki w paczce
- 4
- Skrypty
- 0
- Komentarze HTML
- 0
- Adresy URL w SKILL.md
- 5
Brak sygnałów. Repozytorium zmienione 25.10.2026, bez odwołań do wycofanych modeli i API.
MIT, otwarta: można używać i zmieniać, z zachowaniem informacji o autorze.
Co robi i kiedy
Projektuje i sprawdza interfejsy macOS w SwiftUI i AppKit: materiały, panele ustawień, okna dialogowe, paski narzędzi i fokus klawiatury.
Oryginalny opis (EN)
Design, implement and review macOS SwiftUI or AppKit interfaces, including glass materials, attached settings panels, resizable layouts, dialogs, toolbars, icons and keyboard focus. Use for Mac desktop UI work; use platform-specific guidance for iPhone and iPad interfaces.
Jak działa
- Settings presentation
- Layout, materials and actions
- Technical review
- Verify the changed surface
- Leave one usable installation
Podgląd SKILL.md
--- name: apple-desktop-ui description: Design, implement and review macOS SwiftUI or AppKit interfaces, including glass materials, attached settings panels, resizable layouts, dialogs, toolbars, icons and keyboard focus. Use for Mac desktop UI work; use platform-specific guidance for iPhone and iPad interfaces. license: MIT --- # Apple Desktop UI An opinionated workflow for readable, compact Mac interfaces with coherent glass materials and predictable keyboard behavior. Read the project's instructions and existing design system first. Explicit user and project requirements take precedence; apply changes to the requested surface without unrelated migrations. This skill is self-contained and requires no other skill or application repository. ## Settings presentation For a glass-style app, prefer a **custom settings panel attached to its main window**, using native sheet presentation with custom content. This is a design convention, not an Apple requirement. Retain a different established presentation when the project or user explicitly requires it. - Keep a compact header, clear pane selection, aligned rows and a stable size appropriate to the content. Let longer content scroll instead of clipping controls or reserving large empty regions. Do not copy another app's dimensions or tabs without checking the content. - Reuse the app's material surface and semantic foregrounds. Avoid a separate opaque toolbar, hardcoded black settings background or second visual theme. Respect Reduce Transparency with a solid fallback. - Route the settings button, app-menu Settings item and **Command-Comma** through one presentation authority. Repeated requests reuse the panel and retain its selected pane. Restore or focus the appropriate owning window when necessary; avoid duplicate windows and competing sheets. Required state belongs above views that can disappear or be replaced. - Provide Done/close, Escape dismissal and a sensible initial focus in the pane or content. A nondestructive Done action may be the Return default. Closing clears presentation state and restores useful focus. - Give the close control a practical pointer target, such as a 26 pt circle, with neutral hover and pressed feedback. Avoid an accent-filled square around the close glyph on initial presentation. Keep keyboard access and a visible, coherent focus indicator when Tab reaches the control. Any custom focus treatment must replace the native indicator locally, not globally hide it. - Preserve preference bindings and persistence. Indicate autosave for live changes. Do not add a Cancel action that falsely implies rollback; retain existing Apply/Cancel semantics unless their change is requested. - Keep OS-owned open/save panels and permission prompts native. Custom settings are not permission to imitate, bypass or restyle system authorization. ## Layout, materials and actions - Establish a small shared set of insets, spacing, radii and typography. Related metric cards share widths, heights and value baselines within a row. At compact widths, reflow deliberately and reduce wasted vertical space; keep actions reachable. - Separate the background treatment from readable content. Text, icons, images and data remain legible while the background changes. Use semantic primary/secondary foregrounds and state-aware native controls. Reuse the established material composition rather than stacking new blur and tint layers. - Treat glass as hierarchy, not decoration applied to every element. A denser material can support settings or inspection content; appropriate grouping and spacing should still explain the structure. Under accessibility contrast/transparency settings, prioritize legibility over the effect. - Use familiar semantic symbols with consistent visual weight. Icon-only actions need clear help and accessibility labels. Preserve established custom vector assets and avoid unexplained replacement icons. Reserve prominent accent styling for a genuine primary action. - Keep charts interpretable: prioritize names, provide readable list/legend mapping for cells too small for text, and expose complete labels or paths through help and accessibility. Preserve true proportions and stable item identities. Ensure even cells without text still render their intended background and selection state; show connecting leaders selectively rather than cluttering the chart. - Confirmation sheets identify the target, consequence and action. Use Cancel/Escape and semantic destructive roles. Scope destructive color to that action; check that an inherited accent does not make it look recommended. A destructive action must not silently become the Return default. Preserve existing confirmation and safety checks. ## Technical review Check the actual SDK, deployment target and language settings before adopting API examples. Keep those settings unless migration is requested. Gate newer APIs and preserve older-system fallbacks. Native presentation and controls can support custom glass content without replacing their interaction semantics. For changed SwiftUI, review the concerns that apply: - **State:** keep one authority per setting or presentation, clear ownership versus bindings, and preserve selections across layout changes. Avoid unnecessary observable dependencies in frequently updating views. - **Identity and composition:** use stable item IDs, keep semantic Button roles through visual wrappers, and split views at meaningful data/invalidation boundaries. Do not force a new architecture for a visual change. - **Layout:** handle real window resizing, long or localized labels, display scaling and safe areas. Do not transplant iOS sizing/navigation conventions onto Mac controls. - **Work:** keep synchronous I/O, full-dataset sorting and unbounded view construction out of UI paths. Use bounded presentation data and keep expensive preparation off the main thread. - **Interaction:** preserve accessible labels, useful focus order, visible focus, menu shortcuts, disabled states, and hover/pressed feedback. Do not make a control mouse-only to hide a visual defect. Use current primary documentation for uncertain API behavior. [Apple's HIG](https://developer.apple.com/design/human-interface-guidelines), [Materials](https://developer.apple.com/design/human-interface-guidelines/materials), [Layout](https://developer.apple.com/design/human-interface-guidelines/layout), [Buttons](https://developer.apple.com/design/human-interface-guidelines/buttons) and [SwiftUI documentation](https://developer.apple.com/documentation/swiftui) are reference sources. Apply guidance in context rather than adding unrelated features from a checklist. ## Verify the changed surface Build the actual Mac app and run relevant existing checks. Test meaningful new behavior or nontrivial geometry; avoid assertions that only mirror spacing constants. A visual review does not itself authorize installation, process termination or changes to user data. Inspect native output at minimum, default and wider supported sizes; light/dark appearance with active and inactive windows; long labels and relevant empty/error/busy states. Check Tab/Shift-Tab, Return/Space where applicable, Escape and actual pointer activation. For settings, exercise every entry point, repeated opening, pane retention, owning-window restoration and interaction with other sheets. Check transparency extremes and custom-image backgrounds when relevant. Distinguish source review from actual OS accessibility-toggle or assistive-technology testing. Use disposable owned fixtures for destructive-action previews. Preserve user data, unrelated processes and preferences; restore temporary test choices. Record source/build attribution, unedited screenshots, observed outcomes and remaining gaps. Do not claim untested states passed. ## Leave one usable installation When local installation is part of the authorized delivery, reuse the established app name, bundle identity and install location. Quit the target before replacing its executable. Use separate preview builds only when comparison or isolation requires them, and record which temporary artifacts belong to the task. After verification, retire redundant task-owned previews and confirm the intended installation is the only one left running. Check the delivered signature and executable hash. Keep evidence as logs/screenshots rather than retaining many running test apps. Preserve user data and unrelated applications. Clean only confirmed obsolete task-owned outputs, prefer recoverable removal, and respect any required approval for quitting, installation or deletion. Do not interpret this cleanup convention as authorization for broad build-cache or filesystem deletion. Follow the project's own version-control and delivery policy.
Pliki w paczce (4)
- .gitignore 1 KB
- LICENSE 1 KB
- README.md 2 KB
- SKILL.md 9 KB
Wersje
W bazie nie ma innych skilli o nazwie apple-desktop-ui.
Migawka bazy z 13.11.2026 · wersja paczki ea854363930e (skrót SHA-256 całej paczki)
Pobrania w ostatnich 30 dniach: 0 · ranking
Zgłoś problem z tym skillem: szkodliwa treść, błędny opis albo prośba autora o usunięcie.
Podobne skille
- 91macos-design
Stosuje wytyczne Apple Human Interface Guidelines dla Maca przy budowie aplikacji w SwiftUI i AppKit: paski menu, paski narzędzi, okna i skróty klawiszowe. - 86macos-design-guidelines
Stosuje wytyczne Apple HIG dla Maca przy budowie aplikacji SwiftUI i AppKit: paski menu, paski narzędzi, okna i skróty klawiszowe. - 100macos-golden-gate-design
Projektuje, implementuje i przegląda natywne interfejsy macOS 27 Golden Gate w SwiftUI lub AppKit zgodnie ze stonowanym językiem Liquid Glass: zintegrowane okna, paski boczne, paski narzędzi i formularze. - 91macos-design-guidelines
Opiera projektowanie aplikacji macOS w SwiftUI lub AppKit na wytycznych Apple Human Interface Guidelines, w tym menu, toolbary, zarządzanie oknami i skróty. - 100apple-ui-macos
Podpowiada, jak projektować okna, paski narzędzi i menu aplikacji na Maca w zestawie macOS 26, mapując komponenty na AppKit i SwiftUI. - 95macos-hig-designer
Projektuje natywne aplikacje macOS zgodnie z Apple Human Interface Guidelines i systemem Liquid Glass, przydaje się przy SwiftUI, AppKit i sprawdzaniu zgodności projektu.