# Deliver Swiftui Feature

> Implements a named SwiftUI feature when explicitly requested within approved targets and files; follows actual SDK and state ownership and keeps missing required checks visible.

- Skill: `jovanipink/deliver-swiftui-feature` (Agent Skill, multi-file: 4 files)
- Install (CLI): `npx get-skill add jovanipink/deliver-swiftui-feature`
- Raw SKILL.md: https://api.skillmd.com/api/skills/jovanipink/deliver-swiftui-feature/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- License: MIT
- Author: JovaniPink (https://skillmd.com/u/jovanipink)
- Updated: 2026-11-15
- Page: https://skillmd.com/skills/jovanipink/deliver-swiftui-feature

---


# SwiftUI Feature Delivery

Read [state, availability and acceptance](references/delivery.md) only when its checks apply to the task. Project-local copies include a project contract; compare it with current repository settings before relying on it.

Read [compatibility and evidence preflight](references/currency.md) before selecting targets or reporting acceptance.

## Workflow

1. Establish the requested behavior, acceptance journey, targets, existing edits, and repository instructions before selecting an implementation.
2. Read deployment targets, language mode, default isolation, schemes, and dependency policy. Consult only the relevant reference sections and installed-version authorities.
3. Build a deduplicated repository-relative allowlist from the authorized task and current tracked/untracked changes. Existing changes are evidence, not automatic permission. Exclude dependencies, generated output, build caches, and signing material. If no authorized path remains, return Not Needed.
4. Implement the smallest coherent slice. Keep one state owner, stable identifiers, cancellable effects, explicit error recovery, and supported APIs. Check Dynamic Type, semantic control labels, Reduce Motion, and compact/regular layouts where applicable.
5. Run the narrow behavior check, then applicable existing gates. Inspect the final diff against the allowlist. Report edits, observed checks, missing journey evidence, and remaining risks separately.

## Done when

The slice is complete only when the requested behavior and acceptance criteria are satisfied within the allowlist, required checks pass, and the final allowlisted diff has been inspected. Blocked and partial work remain unfinished. Unavailable required validation must be reported with its limitation and the next authorized check; it cannot establish completion. Not Needed requires evidence that no applicable authorized change exists. Stop and ask only when the slice needs a path outside the allowlist, an action listed under Boundaries, or a product decision the repository cannot answer.

## Boundaries

Never run repository-wide mutating formatters or add dependencies, raise targets, alter signing/entitlements, migrate persistence, or perform external writes without explicit task authority.

## Evidence and output

Lead with the result and anything that needs the user's decision. Then report the authorized scope, applicable settings, observed evidence, missing evidence, and next bounded check. Use Not Needed when no applicable authorized work exists and Blocked when a required precondition is missing. Do not substitute required headings for semantic compliance or invent executed checks.

## Example

Synthetic example; not an observed client result.

Input: Implement an approved form change; the required device check is unavailable.

Output: Implement and run available gates, then report the device check as missing. Required unavailable validation keeps the work incomplete.

