Create Vibe Feature
mistralai/mistral-vibe
Guides feature work in the Mistral Vibe Python CLI so each change lands in the right module and matches the project's architecture decision records.
Plan implementation, design an approach, or create an architecture plan for a Bitwarden iOS feature.
Install Planning iOS Implementation
$ npx skills add bitwarden/ios --skill planning-ios-implementation -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install bitwarden/ios planning-ios-implementation --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/bitwarden/ios.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/planning-ios-implementation .claude/skills/planning-ios-implementation && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "planning-ios-implementation" agent skill from https://github.com/bitwarden/ios/tree/main/.claude/skills/planning-ios-implementation into .claude/skills/planning-ios-implementation/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "planning-ios-implementation", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/bitwarden/ios/tree/main/.claude/skills/planning-ios-implementationType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add bitwarden/ios --skill planning-ios-implementation -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install bitwarden/ios planning-ios-implementation --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/bitwarden/ios.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.claude/skills/planning-ios-implementation .agents/skills/planning-ios-implementation && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "planning-ios-implementation" agent skill from https://github.com/bitwarden/ios/tree/main/.claude/skills/planning-ios-implementation into .agents/skills/planning-ios-implementation/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "planning-ios-implementation", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add bitwarden/ios --skill planning-ios-implementation -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install bitwarden/ios planning-ios-implementation --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/bitwarden/ios.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.claude/skills/planning-ios-implementation .cursor/skills/planning-ios-implementation && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "planning-ios-implementation" agent skill from https://github.com/bitwarden/ios/tree/main/.claude/skills/planning-ios-implementation into .cursor/skills/planning-ios-implementation/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "planning-ios-implementation", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/bitwarden/ios.git --path .claude/skills/planning-ios-implementation--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add bitwarden/ios --skill planning-ios-implementation -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install bitwarden/ios planning-ios-implementation --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/bitwarden/ios.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.claude/skills/planning-ios-implementation .gemini/skills/planning-ios-implementation && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "planning-ios-implementation" agent skill from https://github.com/bitwarden/ios/tree/main/.claude/skills/planning-ios-implementation into .gemini/skills/planning-ios-implementation/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "planning-ios-implementation", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install bitwarden/ios planning-ios-implementationInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add bitwarden/ios --skill planning-ios-implementation -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/bitwarden/ios.git skills-src && mkdir -p .github/skills && cp -r skills-src/.claude/skills/planning-ios-implementation .github/skills/planning-ios-implementation && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "planning-ios-implementation" agent skill from https://github.com/bitwarden/ios/tree/main/.claude/skills/planning-ios-implementation into .github/skills/planning-ios-implementation/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "planning-ios-implementation", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add bitwarden/ios --skill planning-ios-implementation -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install bitwarden/ios planning-ios-implementation --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/bitwarden/ios.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.claude/skills/planning-ios-implementation .opencode/skills/planning-ios-implementation && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "planning-ios-implementation" agent skill from https://github.com/bitwarden/ios/tree/main/.claude/skills/planning-ios-implementation into .opencode/skills/planning-ios-implementation/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "planning-ios-implementation", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
planning-ios-implementation- GitHub stars
- 694
- Token cost
- ~1.1k tokens
- SKILL.md length
- 284 words
- Files
- 1
- Skills in repo
- 11
- Repo updated
- First seen
- Licence
- GPL-3.0
At a glance
Plan implementation, design an approach, or create an architecture plan for a Bitwarden iOS feature.
- Works in 6 steps: Classify the Change → Explore Existing Patterns → List Files to Create/Modify → …
- Asked to plan implementation
- SKILL.md covers Prerequisites, Step 1: Classify the Change, Step 2: Explore Existing… and Step 3: List Files to…, plus 4 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Planning iOS Implementation is an agent skill from bitwarden/ios, published by the product's own GitHub organization. Plan implementation, design an approach, or create an architecture plan for a Bitwarden iOS feature. Use when asked to "plan implementation", "design approach", "architecture plan", "how should I implement", "what files do I need", or to create a design doc before writing code.
Its SKILL.md is about 1.1k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Development, covering Architecture decision records. It works with iOS. The repository describes itself as: Bitwarden mobile apps (Password Manager and Authenticator) for iOS. The licence is GPL-3.0.
When your agent uses it
- Asked to plan implementation
- Design approach
- Architecture plan
- How should I implement
Example prompts
- “plan implementation”
- “design approach”
- “architecture plan”
- “/planning-ios-implementation”
Workflow steps
6 steps, taken from the step headings in SKILL.md.
What it can do on your machine
Read from SKILL.md and the folder at commit 59bbfb3. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Planning iOS Implementation loads about 1.1k tokens when it runs. Until then it costs about 77 tokens; SKILL.md has 284 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from bitwarden/ios at commit 59bbfb3, republished under its GPL-3.0 licence (© bitwarden). 284 words, ~1,058 tokens.
Download SKILL.mdSave it as
.claude/skills/planning-ios-implementation/SKILL.md (or your agent's skills folder).- name
- planning-ios-implementation
- description
- Plan implementation, design an approach, or create an architecture plan for a Bitwarden iOS feature. Use when asked to "plan implementation", "design approach", "architecture plan", "how should I implement", "what files do I need", or to create a design doc before writing code.
Planning iOS Implementation
Use this skill to design a complete implementation plan before writing code. Output is saved as a design document.
Prerequisites
- Requirements must be clear. If not, invoke
refining-ios-requirementsfirst. - Read
Docs/Architecture.mdbefore proceeding — it is the authoritative source for all patterns.
Step 1: Classify the Change
Determine the change type to guide scope and planning depth:
| Type | Description | Typical Scope |
|---|---|---|
| New Feature | Entirely new functionality, screens, or flows | New files + modifications, multi-phase |
| Enhancement | Extending existing feature with new capabilities | Mostly modifications, 1-2 phases |
| Bug Fix | Correcting incorrect behavior | Targeted modifications, single phase |
| Refactoring | Restructuring without behavior change | Modifications only, migration-aware |
| Infrastructure | Build, CI, tooling, or dependency changes | Config files, minimal code changes |
State the classification and rationale before proceeding.
Step 2: Explore Existing Patterns
Search the codebase for similar existing implementations to follow:
- Find a similar existing feature in the same domain
- Identify which services/repositories it uses
- Note how its Coordinator, Processor, and View are structured
- Check if
BitwardenKit/UI/has reusable components for the new UI
Step 3: List Files to Create/Modify
For each file, specify path, action (create/modify), domain placement, and purpose. Group by layer:
### New Files (Create)
#### Core Layer
- `BitwardenShared/Core/<Domain>/<Feature>/Services/<Feature>Service.swift`
- Protocol + Default<Feature>Service + Has<Feature>Service
#### UI Layer
- `BitwardenShared/UI/<Domain>/<Feature>/<Feature>Coordinator.swift`
- `BitwardenShared/UI/<Domain>/<Feature>/<Feature>Processor.swift`
- `BitwardenShared/UI/<Domain>/<Feature>/<Feature>State.swift`
- `BitwardenShared/UI/<Domain>/<Feature>/<Feature>Action.swift`
- `BitwardenShared/UI/<Domain>/<Feature>/<Feature>Effect.swift`
- `BitwardenShared/UI/<Domain>/<Feature>/<Feature>View.swift`
#### Tests (co-located with implementation)
- `BitwardenShared/UI/<Domain>/<Feature>/<Feature>ProcessorTests.swift`
- `BitwardenShared/Core/<Domain>/<Feature>/Services/<Feature>ServiceTests.swift`
### Modified Files
- `BitwardenShared/Core/Platform/Services/ServiceContainer.swift` — Add new service
- `<Existing>Coordinator.swift` — Add new routeStep 4: Dependency-Ordered Implementation Phases
Order phases so each builds on the previous:
### Phase 1: Data / Core Layer
Models, CoreData entities (if needed), service protocols, repository protocols
### Phase 2: Service/Repository Implementations
Default<Name>Service/Repository — business logic, SDK calls, network
### Phase 3: DI Wiring
ServiceContainer extensions, Has* protocol additions
### Phase 4: Processor + State
StateProcessor subclass, State struct, Action enum, Effect enum
### Phase 5: View + Coordinator
SwiftUI View with store.binding, Coordinator with routes, navigation wiring
### Phase 6: Tests
ProcessorTests (action/effect paths), ServiceTests (business logic), ViewTests (snapshots if UI)Step 5: Risk Assessment
Identify risks and mitigations:
- Security: Does this touch vault data, auth tokens, or Keychain? → Security review required
- Extensions: Does this affect AutoFill/Action/Share extensions? → Memory limit check needed
- Multi-account: Does this need per-account isolation? → CoreData userId scoping
- SDK dependency: Does this require BitwardenSdk changes? → Coordinate with SDK team
Step 6: Save Design Document
Save the plan to .claude/outputs/plans/<ticket-id>.md.
Confirm Before Proceeding
Present the plan to the user and ask: "Here is the implementation plan. Should I proceed with implementation?"
© bitwarden, GPL-3.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in .claude/skills/planning-ios-implementation of bitwarden/ios.
Open the folder on GitHubat commit 59bbfb3
Compare with similar skills
Planning iOS Implementation next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Planning iOS Implementation this skillbitwarden/ios | 694 | — | ~1.1k | Automated safety check: Pass | GPL-3.0 | |
| Create Vibe Featuremistralai/mistral-vibe | 5.1k | — | ~1.2k | Automated safety check: Pass | Apache-2.0 | |
| Git Worktree Setupk8zdev/k8z | 155 | — | ~930 | Automated safety check: Pass | None | |
| Grill With Docsmeain/dotfiles | 285 | 21 repos | ~875 | Automated safety check: Pass | MIT | |
| Rememberantonio-orionus/Arroxy | 389 | — | ~571 | Automated safety check: Pass | MIT | |
| Grounding A Designandrew-blake/melcloudhome | 142 | — | ~1.1k | Automated safety check: Pass | MIT |
Similar skills
- Official
Git Worktree Setup
k8zdev/k8z
Automate git worktree creation and copy private files (not tracked in git) to new workdirs.
Grill With Docs
meain/dotfiles
Grilling session that challenges your plan against the existing domain model, sharpens terminology, and updates documentation (CONTEXT.md, ADRs) inline as decisions crystallise.
Remember
antonio-orionus/Arroxy
Persists a durable Arroxy lesson — a gotcha, user preference, workflow rule, or design decision — to the right tracked file (project memory, AGENTS.md, CONTEXT.md, dev-docs, or an ADR) so any coding…
Grounding A Design
andrew-blake/melcloudhome
A skill your agent uses when about to propose, brainstorm, review or revise a design, fix approach or plan for a feature or behaviour change in this repo, including "brief" or "quick" design…
Plan Tree
SeemSeam/claude_codex_bridge
Maintain a structured planning document tree made of roadmap/status files, implementation status or handoff TODO files, topic notes, decision records, open questions, ideas/inspiration pools, and…
More from bitwarden/ios
All 11 skills in this repo- Official
Testing iOS Code
bitwarden/ios
Write tests, add test coverage, unit test, or add missing tests for Bitwarden iOS.
- Official
Audit Build Warnings
bitwarden/ios
Build the Bitwarden iOS app, capture all compiler and lint warnings, categorize them into Swift 6 concurrency vs actionable, and interactively fix the actionable ones.
- Official
Build Test Verify
bitwarden/ios
Build the project, run tests, lint, format, spell check, generate mocks, or verify the build passes for Bitwarden iOS.
- Official
Converting Mocks To Automockable
bitwarden/ios
Convert a hand-written bespoke mock to a Sourcery AutoMockable-generated mock.
- Official
Evaluating SDK Internal Updates
bitwarden/ios
Evaluates a bitwarden/ios "Update SDK to" PR against the sdk-swift commit range for compile-time, runtime and serialization breaking changes, maps affected symbols to iOS call sites, and applies…
- Official
Fixing Flaky Tests
bitwarden/ios
Diagnose and fix flaky (intermittently failing) tests in Bitwarden iOS.
Related
Works with
Categories
Questions about Planning iOS Implementation
What does Planning iOS Implementation do?
Plan implementation, design an approach, or create an architecture plan for a Bitwarden iOS feature. Planning iOS Implementation is an agent skill from bitwarden/ios, published by the product's own GitHub organization. Plan implementation, design an approach, or create an architecture plan for a Bitwarden iOS feature.
When should I use Planning iOS Implementation?
Planning iOS Implementation fits situations like: asked to plan implementation; design approach; architecture plan; how should I implement.
How do I install Planning iOS Implementation in Claude Code?
Run `npx skills add bitwarden/ios --skill planning-ios-implementation -a claude-code`. Or copy the skill folder (.claude/skills/planning-ios-implementation in bitwarden/ios) into .claude/skills/planning-ios-implementation in your project. Claude Code loads it when a task matches its description.
How do I install Planning iOS Implementation in Codex?
Run `npx skills add bitwarden/ios --skill planning-ios-implementation -a codex`. Or copy the skill folder (.claude/skills/planning-ios-implementation in bitwarden/ios) into .agents/skills/planning-ios-implementation in your project. Codex loads it when a task matches its description.
Can I use Planning iOS Implementation in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add bitwarden/ios --skill planning-ios-implementation -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/planning-ios-implementation, .gemini/skills/planning-ios-implementation, .github/skills/planning-ios-implementation and .opencode/skills/planning-ios-implementation in your project.
What does Planning iOS Implementation need to run?
SKILL.md names no scripts, command-line tools or credentials: Planning iOS Implementation is instructions for the agent only.
Does Planning iOS Implementation access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Planning iOS Implementation safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Planning iOS Implementation use?
Planning iOS Implementation is published under the GPL-3.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Planning iOS Implementation use?
About 1.1k tokens (SKILL.md is roughly 4.2k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Planning iOS Implementation?
Skills that share tags, products or a category with Planning iOS Implementation: Create Vibe Feature (mistralai/mistral-vibe, 5.1k stars), Git Worktree Setup (k8zdev/k8z, 155 stars), Grill With Docs (meain/dotfiles, 285 stars) and Remember (antonio-orionus/Arroxy, 389 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Planning iOS Implementation?
bitwarden (a GitHub organization, an official publisher) maintains it in bitwarden/ios, which has 694 GitHub stars. The repository holds 11 skills in this directory. The repository was last updated on October 6, 2026.
Source: bitwarden/ios on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.