How do I install the Design Macos Interfaces skill?

Run npx skillmds@latest add 0xkoru/design-macos-interfaces in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Design Macos Interfaces safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Design Macos Interfaces?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Design Macos Interfaces free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Design Macos Interfaces?

0xKoru (@0xkoru) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Design Macos Interfaces by 0xkoru — Agent Skill

Name: Design Macos Interfaces
Rating: 4.2 (5 reviews)
Author: 0xKoru

Design Macos Interfaces

Design native-feeling macOS interfaces using Apple Human Interface Guidelines and common macOS app conventions. Use when Codex needs to create, redesign, implement, or review Mac app windows, sidebars, toolbars, settings windows, menu behavior, command palettes, document workflows, Flutter macos_ui layouts, desktop web apps with macOS feel, or cross-platform Apple-style desktop experiences.

0xKoru Updated Sep 22, 2026

File contents

Design macOS Interfaces

Use this skill when the target experience is a desktop Apple interface or a Mac-like web/Flutter app.

Workflow

Determine whether the app is document-based, utility, content browser, creator tool, settings utility, or dashboard.
Choose the window model: single-window app, document windows, utility panels, settings window, sheets, popovers, or inspectors.
Place persistent navigation in sidebars or segmented toolbar controls. Keep important commands in the menu bar and toolbar.
Design with pointer, keyboard, menus, resizable windows, and multi-window behavior in mind.
Specify default, compact, and expanded window sizes. Avoid bottom-only critical controls because windows can be partly off screen.
Include accessibility, keyboard shortcuts, menu availability, empty states, and window restoration notes.

macOS Design Rules

Keep standard menu items unless there is a strong platform reason to remove them.
Settings windows should be ordinary windows, not translucent panels. Use grouped forms and expected tabs or sections.
Toolbars should contain frequent commands; menu bar should still expose commands and keyboard shortcuts.
Sidebars are for navigation and source lists. Inspectors are for details or properties of the current selection.
Use sheets for document-modal decisions and popovers for lightweight contextual controls.
Do not rely on touch-sized spacing; macOS can be denser, but targets and focus states still need to be clear.
For Flutter, use macos_ui components when the project already uses Flutter and wants native macOS conventions.

References

Read references/macos-patterns.md for component mapping and source links.

---name: design-macos-interfacesdescription: Design native-feeling macOS interfaces using Apple Human Interface Guidelines and common macOS app conventions. Use when Codex needs to create, redesign, implement, or review Mac app windows, sidebars, toolbars, settings windows, menu behavior, command palettes, document workflows, Flutter macos_ui layouts, desktop web apps with macOS feel, or cross-platform Apple-style desktop experiences.---# Design macOS InterfacesUse this skill when the target experience is a desktop Apple interface or a Mac-like web/Flutter app.## Workflow1. Determine whether the app is document-based, utility, content browser, creator tool, settings utility, or dashboard.2. Choose the window model: single-window app, document windows, utility panels, settings window, sheets, popovers, or inspectors.3. Place persistent navigation in sidebars or segmented toolbar controls. Keep important commands in the menu bar and toolbar.4. Design with pointer, keyboard, menus, resizable windows, and multi-window behavior in mind.5. Specify default, compact, and expanded window sizes. Avoid bottom-only critical controls because windows can be partly off screen.6. Include accessibility, keyboard shortcuts, menu availability, empty states, and window restoration notes.## macOS Design Rules- Keep standard menu items unless there is a strong platform reason to remove them.- Settings windows should be ordinary windows, not translucent panels. Use grouped forms and expected tabs or sections.- Toolbars should contain frequent commands; menu bar should still expose commands and keyboard shortcuts.- Sidebars are for navigation and source lists. Inspectors are for details or properties of the current selection.- Use sheets for document-modal decisions and popovers for lightweight contextual controls.- Do not rely on touch-sized spacing; macOS can be denser, but targets and focus states still need to be clear.- For Flutter, use `macos_ui` components when the project already uses Flutter and wants native macOS conventions.## ReferencesRead `references/macos-patterns.md` for component mapping and source links.

Frequently asked questions