Individual skill

macos-golden-gate-design

Design, implement, review, or refactor native macOS 27 Golden Gate interfaces in SwiftUI or AppKit. Use when a Mac app must match Apple's current macOS 27 UI kit and restrained Liquid Glass language: integrated windows, full-height sidebars, native toolbars, flat lists, tables, and forms, clear pane boundaries, accessible materials, and removal of unnecessary nested cards, framed panels, or glassmorphism. Also use for Figma macOS 27 design-to-code work and audits of interfaces that feel too boxed.

skills/macos-golden-gate-design/SKILL.md

Read pinned source

Source commit edbecfa9099c4addae1f500cca1ac067204b30fd

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
Yes
Repository scan complete
No
Skill scan complete
No
Observed behavior
Network or broad shell
Last checked
Nov 4, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
40,905
Repository last updated
Nov 6, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# macOS 27 Golden Gate Design

## Design contract

Make the app look like a native macOS 27 app, not a web dashboard placed inside a Mac window.

- The window is already the outer container. Do not add a rounded app shell inside it.
- Start with a structural card budget of zero. Add a framed container only when a genuinely self-contained object's boundary communicates meaning.
- Sidebars, content columns, inspectors, tables, lists, and forms are panes or content regions, not cards.
- Let adjacent panes meet at a shared boundary. Use native dividers, separators, alignment, spacing, typography, and selection fills instead of nested rounded rectangles.
- Keep Liquid Glass, but concentrate it in system chrome and compact controls: titlebar and toolbar controls, search, sidebar or inspector material, floating controls, popovers, menus, sheets, and transient surfaces.
- Keep the primary content plane calm and readable. Do not put glass behind every row, section, or data block.
- Prefer standard SwiftUI or AppKit components so macOS supplies current metrics, appearance, interaction, inactive-window behavior, accessibility adaptation, and future refinements.
- Treat a selected row as a state treatment, not as evidence that every neighboring row needs a capsule.