planning-ios-implementation

Creates architecture plans and phased implementation designs for Bitwarden iOS features.

680|154|Updated Jul 14, 2023
One-click install
npx skills add https://github.com/bitwarden/ios --skill planning-ios-implementation
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: planning-ios-implementation
Source: https://github.com/bitwarden/ios/tree/main/.claude/skills/planning-ios-implementation
Command: npx skills add https://github.com/bitwarden/ios --skill planning-ios-implementation

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Writing iOS code without a clear plan leads to inconsistent architecture, missed dependencies, and rework. This Skill produces a structured implementation plan for Bitwarden iOS features before any code is written, ensuring the design follows the project's established Coordinator-Processor-View patterns.

Core Features & Use Cases

  • Change Classification: Categorizes work as new feature, enhancement, bug fix, refactoring, or infrastructure to scope planning depth.
  • File-Level Planning: Lists exact files to create or modify across Core, UI, and test layers, following BitwardenShared conventions.
  • Dependency-Ordered Phases: Sequences work from data layer through services, DI wiring, Processor/State, View/Coordinator, and tests.
  • Risk Assessment: Flags security, app extension memory limits, multi-account isolation, and BitwardenSdk dependency concerns.
  • Use Case: When asked to add a new vault feature, the Skill explores similar existing implementations, produces a design document saved to .claude/outputs/plans/, and asks for confirmation before implementation begins.

Quick Start

Ask the assistant to plan the implementation of a new Bitwarden iOS feature, such as "plan how I should implement a password history screen".

Frequently Asked Questions about planning-ios-implementation

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

FAQPage Schema
How do I plan an iOS feature implementation before writing code?

Start by classifying the change type, then explore similar existing features to identify reusable patterns. List files to create or modify by layer, order implementation into dependency-based phases, and assess risks before coding.

What architecture pattern does the Bitwarden iOS app use?

The Bitwarden iOS app uses a Coordinator-Processor-View pattern with SwiftUI. Each feature has a Coordinator for navigation, a StateProcessor subclass handling Actions and Effects, a State struct, and a SwiftUI View.

How should I structure a new feature in a SwiftUI iOS codebase?

Create separate files for Coordinator, Processor, State, Action, Effect, and View under the appropriate UI domain. Add services in the Core layer with protocol and default implementation, then wire dependencies through the ServiceContainer.

Does this planning approach work for bug fixes and refactoring?

Yes, the Skill classifies changes into five types including bug fixes and refactoring. Bug fixes get targeted single-phase plans, while refactoring plans emphasize modifications without behavior change and migration awareness.

What risks should I check when planning iOS features that touch vault data?

Features touching vault data, auth tokens, or the Keychain require security review. Also check app extension memory limits for AutoFill, per-account CoreData isolation via userId scoping, and any BitwardenSdk dependency changes.