cross-platform

Align APIs, paths, and behavior across macOS Swift and Windows C# apps.

1|Updated Feb 9, 2026
One-click install
npx skills add https://github.com/Pepsi1978/proggs --skill cross-platform-pepsi1978
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cross-platform
Source: https://github.com/Pepsi1978/proggs/tree/main/claude-code-setup/commands/cross-platform
Command: npx skills add https://github.com/Pepsi1978/proggs --skill cross-platform-pepsi1978

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps developers ensure that features implemented for macOS (Swift/AppKit) and Windows (C#/WPF) behave consistently, avoiding platform drift and duplicate effort.

Core Features & Use Cases

  • Cross-platform parity checks for APIs, UI behavior, and project structure between macOS and Windows
  • Shared guidance for mapping functionalities, build/run scripts, and conventions across both platforms
  • Use Case: when adding a feature on macOS, mirror and verify equivalent behavior on Windows to maintain a consistent user experience

Quick Start

Review existing macOS and Windows projects and implement a parity plan for any new feature before coding begins

Frequently Asked Questions about cross-platform

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I maintain cross-platform parity between macOS Swift and Windows C# apps?

Cross-platform parity is maintained by mapping project structures, aligning platform-specific APIs, and verifying consistent UI behavior between macOS Swift and Windows C# apps before coding begins.

What is the best way to map macOS AppKit features to Windows WPF equivalents?

The best way to map macOS AppKit features to Windows WPF equivalents is to use structured project structure mapping and platform-specific API usage guidelines to ensure features align across both platforms.

How do I implement a parity plan for new features in macOS and Windows projects?

To implement a parity plan, review your existing macOS and Windows projects, map the shared functionalities, and define API, path, and behavior alignment practices before starting development.

Does this approach support build and run automation practices for macOS and Windows?

Yes, it supports build and run automation practices by providing shared guidance for mapping build and run scripts, ensuring consistent execution conventions across macOS and Windows environments.

When do I need to check cross-platform API alignment during development?

You need to check cross-platform API alignment whenever modifying or adding features in macOS Swift apps and Windows C# apps to prevent platform drift and avoid duplicate development effort.