{
  "markdown": "# Swift Architecture Skill\n\n[![Validate Skill](https://github.com/efremidze/swift-architecture-skill/actions/workflows/validate-skill.yml/badge.svg)](https://github.com/efremidze/swift-architecture-skill/actions/workflows/validate-skill.yml)\n[![Agent Skills](https://img.shields.io/badge/Agent%20Skills-Compatible-purple.svg)](https://agentskills.io/home)\n![Release](https://img.shields.io/github/v/release/efremidze/swift-architecture-skill)\n\nArchitecture guidance for AI coding tools — because LLMs default to MVVM for everything. This skill routes to the right pattern for your feature, keeps guidance scoped to your task, and gives you concrete code, anti-pattern fixes, and a PR checklist.\n\nSupports the [Agent Skills open format](https://agentskills.io/home).\n\n## Features\n\n- **Routes to the right architecture**: Describe your feature and the skill selects the best fit based on UI stack, state complexity, and existing conventions. Name a pattern yourself and it validates the fit before you commit.\n- **Scoped playbooks**: Each architecture has its own reference — code patterns, anti-pattern fixes, testing strategy, and a PR checklist. Guidance never bleeds across patterns.\n- **Reference index**: A dedicated `_index.md` gives agents a fast navigation hub and problem router before diving into a playbook.\n- **SwiftUI and UIKit**: Every playbook covers both stacks with modern async/await and actor-based concurrency patterns throughout.\n- **Snippet validation**: CI parses Swift fences across the playbooks so examples stay syntactically healthy as guidance evolves.\n\n## Supported Architectures\n\nMVP · MVVM · MVI · TCA · Clean Architecture · VIPER · Coordinator · Reactive\n\nEach has a dedicated [playbook](swift-architecture-skill/references/) with overview, patterns, anti-pattern fixes, testing strategy, and PR checklist.\nStart with the [reference index](swift-architecture-skill/references/_index.md) for quick routing, or use the [selection guide](swift-architecture-skill/references/selection-guide.md) when the architecture is still undecided.\n\n## Installation\n\n### skills.sh (recommended)\n\nWorks with any tool that supports the [Agent Skills](https://agentskills.io) format:\n\n```bash\nnpx skills add https://github.com/efremidze/swift-architecture-skill --skill swift-architecture-skill\n```\n\n### Claude Code plugin\n\nInstall from the marketplace for personal use:\n\n```text\n/plugin marketplace add efremidze/swift-architecture-skill\n/plugin install swift-architecture-skill@swift-architecture-skill\n```\n\nOr enable it for an entire project by committing this to `.claude/settings.json`:\n\n```json\n{\n  \"extraKnownMarketplaces\": {\n    \"swift-architecture-skill\": {\n      \"source\": {\n        \"source\": \"github\",\n        \"repo\": \"efremidze/swift-architecture-skill\"\n      }\n    }\n  },\n  \"enabledPlugins\": {\n    \"swift-architecture-skill@swift-architecture-skill\": true\n  }\n}\n```\n\n### Manual install\n\nClone the repo and copy the skill into your skills directory — `~/.claude/skills/` for personal use, or a project's `.claude/skills/`:\n\n```bash\ngit clone https://github.com/efremidze/swift-architecture-skill.git\nmkdir -p ~/.claude/skills  # or .claude/skills for a project\ncp -r swift-architecture-skill/swift-architecture-skill ~/.claude/skills/swift-architecture-skill\n```\n\n## Usage\n\nOnce installed, ask your agent:\n\n> Use `swift-architecture-skill` to recommend and scaffold architecture for this feature.\n\n## Example Prompts\n\n```text\nI'm building a SwiftUI feed with pagination, pull-to-refresh, and live updates.\nWhich architecture should I use and why?\n```\n\n```text\nWe're planning to use TCA for a simple settings screen with two toggles.\nIs that the right call, or is it overkill for this feature?\n```\n\n```text\nThis module started as MVVM but the ViewModel is doing too much — routing,\nformatting, and business logic. Use swift-architecture-skill to refactor it\ntoward Clean Architecture and show me the layer boundaries.\n```\n\n```text\nWe have a UIKit + MVP module we're migrating to SwiftUI. Should we keep MVP\nor switch patterns during the migration, and how do we handle the transition\nperiod where both coexist?\n```\n\n## Skill Structure\n\n```text\nswift-architecture-skill/\n  SKILL.md                       # Routing logic and output requirements\n  references/\n    _index.md                    # Navigation hub and problem router\n    selection-guide.md           # Decision framework across architectures\n    mvp.md                       # MVP playbook\n    mvvm.md                      # MVVM playbook\n    mvi.md                       # MVI playbook\n    tca.md                       # TCA playbook\n    clean-architecture.md        # Clean Architecture playbook\n    viper.md                     # VIPER playbook\n    coordinator.md               # Coordinator playbook\n    reactive.md                  # Reactive (Combine/RxSwift) playbook\n```\n\n## Contributing\n\nContributions are welcome. A few things to keep in mind:\n\n- **Respect the token budget.** SKILL.md is loaded on every invocation — keep additions concise.\n- **Don't repeat what LLMs already know.** Focus on edge cases, common mistakes, and pattern-specific traps that models get wrong.\n- **One playbook per pattern.** Keep guidance scoped; don't let patterns bleed into each other.\n\nSee [CONTRIBUTING.md](CONTRIBUTING.md) for full structure and quality requirements.\n\n## Related\n\n- [swift-patterns-skill](https://github.com/efremidze/swift-patterns-skill)\n\n## License\n\nMIT. See [LICENSE](LICENSE) for details.\n",
  "bytes": 5489,
  "sha": "96bf27b643f810fc5e7b037298ac842afb4cb34539d28015dafb63b7a0210350",
  "repo_slug": "efremidze/swift-architecture-skill",
  "fonte": "repo",
  "truncated": false,
  "api": "https://agentalog.com/api/listings/skl_efremidze_swift_architecture_skill_swift_a5cdf115/readme"
}