/feedback-form

name: feedback-form
description: Generates an in-app feedback collection form with category selection, text input, optional screenshot attachment, device diagnostics, and support follow-up for low ratings. Never gates the App Store review prompt on in-app sentiment (Guideline 5.6.1). Use when user wants feedback, bug reports, feature requests, or contact support forms.
allowed-tools: [Read, Write, Edit, Glob, Grep, Bash, AskUserQuestion]
last_verified: 2026-11-08
review_by: 2027-06-22
os_version: iOS 27 / macOS 27

Feedback Form Generator

Generate a production in-app feedback form with category selection, sentiment-based rating, optional screenshot attachment, device diagnostics collection, and support follow-up for unhappy users. The feedback form is a support channel open to every user. It never decides who sees the App Store review prompt.

When This Skill Activates

Use this skill when the user:

• Asks to "add a feedback form" or "feedback form"
• Wants "in-app feedback" or "user feedback" collection
• Mentions "bug report form" or "feature request" form
• Asks about "contact support" from within the app
• Wants "feedback collection" with categories or screenshots
• Asks to "route users to App Store review" based on sentiment (generate the form, but explain why the routing is not allowed: see Gotchas)

Pre-Generation Checks

1. Project Context Detection

• [ ] Check Swift version (requires Swift 5.9+)
• [ ] Check deployment target (iOS 16+ / macOS 13+)
• [ ] Check for @Observable support (iOS 17+ / macOS 14+)
• [ ] Identify source file locations

2. Conflict Detection

Search for existing feedback or support code:

Glob: **/*Feedback*.swift, **/*Support*.swift, **/*BugReport*.swift, **/*ContactForm*.swift
Grep: "MFMailComposeViewController" or "FeedbackForm" or "SKStoreReviewController"

If third-party feedback SDK found (Instabug, UserVoice, Zendesk):

• Ask if user wants to replace or keep it
• If keeping, don't generate — advise on best practices instead

3. Framework Detection

Check for MessageUI availability:

Grep: "import MessageUI" or "MFMailCompose"

Note: MessageUI is iOS-only. macOS uses `NSSharingService` or direct webhook delivery.

Configuration Questions

Ask user via AskUserQuestion:

1. **Feedback categories?** (multi-select)

• Bug Report
• Feature Request
• General Feedback
• Praise
• Other
• All of the above — recommended

2. **Delivery method?**

• Email (via MFMailComposeViewController / NSSharingService)
• Webhook (POST to a URL endpoint)
• Both — recommended

3. **Include screenshot capture?**

• Yes — recommended (capture current screen + annotation overlay)
• No

4. **Include device diagnostics?**

• Yes — recommended (device model, OS, app version, disk, memory)
• No

5. **Support follow-up for low ratings?**

• Yes — recommended (rating <= 2 shows a "we'll follow up" confirmation and flags the entry for support)
• No (all feedback gets the same confirmation)

Do **not** offer "rating >= 4 → App Store review" routing, even if asked. Showing the review prompt only to users who rated you highly in-app is review gating. See Gotchas.

Generation Process

Step 1: Read Templates

Read `templates.md` for production Swift code.

Step 2: Create Core Files

Generate these files: 1. `FeedbackCategory.swift` — Enum with SF Symbol icons and display names 2. `FeedbackEntry.swift` — Data model for a feedback submission 3. `DeviceDiagnostics.swift` — Collects device and app info

Step 3: Create UI Files

4. `FeedbackFormView.swift` — SwiftUI form with sentiment, category, message, screenshots

Step 4: Create Delivery Files

5. `FeedbackSubmitter.swift` — Protocol + EmailFeedbackSubmitter + WebhookFeedbackSubmitter

Step 5: Create Optional Files

Based on configuration:

• `ScreenshotCapture.swift` — If screenshot capture selected

Step 6: Determine File Location

Check project structure:

• If `Sources/` exists -> `Sources/Feedback/`
• If `App/` exists -> `App/Feedback/`
• Otherwise -> `Feedback/`

Output Format

After generation, provide:

Files Created

Feedback/
├── FeedbackCategory.swift       # Category enum with icons
├── FeedbackEntry.swift          # Feedback data model
├── DeviceDiagnostics.swift      # Device info collector
├── FeedbackFormView.swift       # SwiftUI form view
├── FeedbackSubmitter.swift      # Email + webhook delivery
└── ScreenshotCapture.swift      # Screen capture (optional)

Integration Steps

**Present the feedback form from any view:**

@State private var showFeedback = false

Button("Send Feedback") {
    showFeedback = true
}
.sheet(isPresented: $showFeedback) {
    FeedbackFormView()
}

**In a settings screen:**

Form {
    Section("Support") {
        Button {
            showFeedback = true
        } label: {
            Label("Send Feedback", systemImage: "bubble.left.and.text.bubble.right")
        }
    }
}
.sheet(isPresented: $showFeedback) {
    FeedbackFormView()
}

**With a pre-selected category (e.g., from a help menu):**

FeedbackFormView(initialCategory: .bugReport)

Testing

@Test
func feedbackEntryEncodesCorrectly() throws {
    let entry = FeedbackEntry(
        category: .bugReport,
        message: "App crashes when tapping save",
        rating: 2,
        screenshots: [],
        deviceInfo: DeviceDiagnostics.collect(),
        appVersion: "1.2.3",
        timestamp: Date()
    )

    let data = try JSONEncoder().encode(entry)
    let decoded = try JSONDecoder().decode(FeedbackEntry.self, from: data)
    #expect(decoded.category == .bugReport)
    #expect(decoded.rating == 2)
}

@Test
func webhookSubmitterSendsCorrectPayload() async throws {
    let mockSession = MockURLSession()
    let submitter = WebhookFeedbackSubmitter(
        url: URL(string: "https://example.com/feedback")!,
        session: mockSession
    )

    let entry = FeedbackEntry(