Apple, Swift, and Xcode workflow skills for Codex and Claude Code.
This repository is active and available for maintainer use.
This repository is the canonical source of truth for Gale's Apple, Swift, and Xcode workflow skills. Treat productivity-skills as the default baseline layer for general repo-doc and maintenance work, and use apple-dev-skills when Apple-specific assumptions should actively shape the workflow.
It exists to keep Apple-platform workflow guidance in one dedicated repository with explicit requirements around Apple documentation, Xcode-safe workflows, and clear source-of-truth boundaries.
This repository is primarily the authored source tree for the shipped Apple workflow skills rather than an end-user app with a separate getting-started path. If you want to understand what the repo currently ships, start with Active Skills and docs/maintainers/workflow-atlas.md. If you want to modify the repository, go to Development and use CONTRIBUTING.md for the maintainer workflow.
Use this repository's skills when the work is about:
- Swift or SwiftUI implementation
- Apple UI accessibility implementation or review
- SwiftUI app structure, focus design, scene ownership, or command architecture
- Xcode build, run, or test workflows
- DocC symbol comments, articles, catalog structure, or DocC-oriented review
- Swift source cleanup, file-header normalization, or source-organization policy
- Swift package bootstrap or validation
- Apple-project guidance sync
- Apple-platform documentation routing
Use CONTRIBUTING.md for maintainer workflow details, and use ROADMAP.md for planned and completed milestone-level work.
Sync the maintainer environment before editing skills, tests, or maintainer docs:
uv sync --devTreat root skills/ as the canonical authored surface. Keep shared reusable assets in shared/, maintainer docs in docs/, and install metadata in .codex-plugin/plugin.json and .claude-plugin/marketplace.json.
Keep the repo honest about its Apple docs-first policy. When a skill changes, update the relevant tests and maintainer guidance in the same pass rather than letting the packaging or guidance drift. Use CONTRIBUTING.md for the normal contributor workflow and review expectations.
Run the repository test suite for skill and metadata changes:
bash .github/scripts/validate_repo_docs.sh
uv run pytest.
├── .codex-plugin/
├── .claude-plugin/
├── AGENTS.md
├── CONTRIBUTING.md
├── README.md
├── ROADMAP.md
├── docs/maintainers/
├── shared/
├── skills/
└── tests/
bootstrap-swift-packagebootstrap-xcode-app-projectauthor-swift-docc-docsexplore-apple-swift-docsapple-ui-accessibility-workflowformat-swift-sourcesstructure-swift-sourcesswiftui-app-architecture-workflowswift-package-build-run-workflowswift-package-testing-workflowswift-package-workflowsync-swift-package-guidancesync-xcode-project-guidancexcode-app-project-workflowxcode-build-run-workflowxcode-testing-workflow
Use Git history and GitHub releases to track shipped changes for this repository.
See LICENSE.