macOS design review
Read docs/DESIGN.md and the references needed for the task:
references/layout-and-composition.mdreferences/visual-system.mdreferences/interaction-patterns.mdreferences/platform-matrix.md
Run the accessibility gate in ../apple-accessibility/SKILL.md. Load ../swiftui-navigation/SKILL.md for navigation or presentation changes.
Workflow
- Name the primary user task and content hierarchy.
- Choose system windows, scenes, navigation, toolbars, lists, tables, grids, forms, and presentation containers.
- Cover loading, populated, empty, search-empty, failure, permission-denied, offline, and absent-selection states.
- Define pointer, keyboard, VoiceOver, Voice Control, menu/command, drag-and-drop, and multi-window behaviour where applicable.
- Start with semantic system typography, colour, materials, symbols, spacing, and controls.
- Review narrow, standard, wide, full-screen, active, and inactive window states.
- Check light and dark appearance, localisation expansion, text scaling, contrast, Reduce Transparency, and Reduce Motion.
- Use previews for representative states, then run the assembled app on the lowest supported macOS version and representative hardware/input devices.
Native composition
This repository uses native SwiftUI for macOS. Use system title-bar, toolbar, window, material, colour, and control APIs. Do not draw traffic lights, fake title bars, copy browser or Electron chrome, or convert CSS measurements into fixed SwiftUI metrics.
Output
Group findings into blockers, important improvements, and polish. Name the macOS version, window size/state, input method, and affected application state. Give the consequence and smallest correction for each finding.
1---2name: apple-design-review3description: Design or review native macOS SwiftUI interfaces, including layout, visual hierarchy, interaction, keyboard and pointer input, windowing, and system integration.4license: MIT5---67# macOS design review89Read `docs/DESIGN.md` and the references needed for the task:1011- `references/layout-and-composition.md`12- `references/visual-system.md`13- `references/interaction-patterns.md`14- `references/platform-matrix.md`1516Run the accessibility gate in `../apple-accessibility/SKILL.md`. Load `../swiftui-navigation/SKILL.md` for navigation or presentation changes.1718## Workflow19201. Name the primary user task and content hierarchy.212. Choose system windows, scenes, navigation, toolbars, lists, tables, grids, forms, and presentation containers.223. Cover loading, populated, empty, search-empty, failure, permission-denied, offline, and absent-selection states.234. Define pointer, keyboard, VoiceOver, Voice Control, menu/command, drag-and-drop, and multi-window behaviour where applicable.245. Start with semantic system typography, colour, materials, symbols, spacing, and controls.256. Review narrow, standard, wide, full-screen, active, and inactive window states.267. Check light and dark appearance, localisation expansion, text scaling, contrast, Reduce Transparency, and Reduce Motion.278. Use previews for representative states, then run the assembled app on the lowest supported macOS version and representative hardware/input devices.2829## Native composition3031This repository uses native SwiftUI for macOS. Use system title-bar, toolbar, window, material, colour, and control APIs. Do not draw traffic lights, fake title bars, copy browser or Electron chrome, or convert CSS measurements into fixed SwiftUI metrics.3233## Output3435Group findings into blockers, important improvements, and polish. Name the macOS version, window size/state, input method, and affected application state. Give the consequence and smallest correction for each finding.
rcarmo