About Prefire
Prefire turns SwiftUI previews into snapshot tests, a component catalog, and images for iOS, tvOS, and macOS developers. Its MCP server also lets AI agents render previews for selected devices and appearance settings.
Key features
- 01Parse #Preview and PreviewProvider
- 02Generate snapshot tests automatically
- 03Build an interactive Playbook catalog
- 04Render previews as PNG images
- 05Support SwiftUI, UIKit, and AppKit
Use cases
- 01Check interface changes for visual regressions
- 02Organize component and user-story catalogs
- 03Let AI agents inspect views on selected devices
MCP support
Prefire provides an MCP server for listing previews, rendering them, and building a board. Clients can use it to give agents preview images rendered with selected devices and color schemes.
Configuration
Local server config is the same for every client. Copy it into your client’s MCP config file.
We haven’t collected a package or remote endpoint for this server. Follow the instructions in the project README.
Tools
Local servers expose tools only once running on your machine, and the maintainer has not provided a tool list.
Details
From the project README
Quick Start · Installation · Usage · AI agents · Configuration · Docs
🔥 What is Prefire?
Prefire turns the #Preview blocks you already write into tests, a catalog and images, with no extra code.
📸 Snapshot testsEvery preview becomes a snapshot test, on the devices you pick. Catch visual regressions before users do.How it works → |
📚 PlaybookAn interactive catalog of your components and user stories, with states and render times. Living documentation.See Playbook → |
🤖 AI-ready rendersClaude Code, Cursor and Codex render your previews through an MCP server, on any iPhone or iPad, light or dark.Set up → |
🤖 Using an AI agent?
brew install barredewe/prefire/prefire, thenclaude mcp add prefire -- prefire mcpin your project. The agent renders SwiftUI previews on any iPhone or iPad, light or dark, without Xcode Previews. Setup →
🚀 Key Features
- 🧠 Smart Preview Parsing — including
#Preview,@Previewable - 📸 Snapshot Testing — automatic test generation from previews (iOS, tvOS, macOS)
- 📚 Playbook View — auto-generated interactive component catalog (iOS)
- 🏃 Flow-aware — build user stories from multiple preview steps
- 🤖 AI-ready — render previews to PNG for agents with
prefire renderand an MCP server - 🧩 UIKit + AppKit Support — support for
UIView/UIViewControllerandNSView/NSViewController - ⚙️ SPM + Xcode Plugins — works in CLI, Xcode build phases, or CI
- 🧠 Fast Caching — fingerprint-based AST and body caching avoids redundant work
- ✍️ Stencil Templates — customize output with your own templates
Why Prefire?
- 🔥 Save Time - Generate tests and documentation automatically
- 🔥 Stay Consistent - Keep previews and tests always in sync
- 🔥 Improve Quality - Catch visual regressions before users do
- 🔥 Boost Collaboration - Share living documentation with your team
⚡ Quick Start
📦 Example project available at: Prefire Example
1. Add Prefire to Your Project
// Package.swift
dependencies: [
.package(url: "https://github.com/BarredEwe/Prefire.git", from: "6.3.0"),
.package(url: "https://github.com/pointfreeco/swift-snapshot-testing", from: "1.18.0"),
],
.testTarget(
dependencies: [
.product(name: "Prefire", package: "Prefire"),
.product(name: "SnapshotTesting", package: "swift-snapshot-testing"),
],
plugins: [
.plugin(name: "PrefireTestsPlugin", package: "Prefire")
]
)
2. Write #Preview
#Preview {
Button("Submit")
}
3. Run tests
Just run the test target 🚀 — Prefire will auto-generate snapshots based on your previews.
💡 If your test target is empty, Prefire will still generate files and snapshot code during build.
📦 Installation
| Method | How |
|---|---|
| SPM Plugin | PrefireTestsPlugin / PrefirePlaybookPlugin in Package.swift |
| Xcode Build Tool Plugin | Add PrefireTestsPlugin to the test target's build phases |
| CLI | brew install barredewe/prefire/prefire |
| Mint (Beta) | mint install BarredEwe/Prefire |
| GitHub Actions / CI | Any of the above, see Troubleshooting |
Step-by-step setup is in the Installation guide.
Requirements
- Swift 6.0 or higher
- Xcode 16.0 or higher
- iOS 14 or higher; macOS 13 or higher (macOS: snapshot tests only, see Configuration)
🛠 Usage
Choose previews
Prefire finds every #Preview automatically. For PreviewProvider, add the PrefireProvider protocol:
struct Text_Previews: PreviewProvider, PrefireProvider {
static var previews: some View { ... }
}
Exclude a preview with .prefireIgnored():
#Preview {
Text("")
.prefireIgnored()
}
To opt in instead of opting out, set preview_default_enabled: false in .prefire.yml and mark the previews you want with .prefireEnabled():
#Preview {
Text("")
.prefireEnabled()
}
Snapshot tests
PrefireTestsPlugin generates the tests into the DerivedData folder when the test target builds. Run the test target as usual.
Tune the timing and precision of a single snapshot:
#Preview {
TestView()
.snapshot(delay: 0.3, precision: 0.95, perceptualPrecision: 0.98)
}
For previews that load or animate, wait instead of guessing a delay:
.snapshot(waitForIdle: true) // until nothing changes on screen
.snapshot(waitUntil: { viewModel.isLoaded }) // until a condition is true
How waiting works, its limits and how the modifiers combine: Snapshot timing and precision.
Snapshots are compared with swift-snapshot-testing.
Playbook (Demo) View
Show all previews as an interactive catalog with PlaybookView:
isComponent: truelists all the ViewsisComponent: falsegroups them by UserStory
import Prefire
struct ContentView: View {
var body: some View {
PlaybookView(isComponent: true, previewModels: PreviewModels.models)
}
}
To keep previews and PreviewModels out of release builds, see Excluding previews from release builds.
Flows
Connect previews into one Flow with .previewUserStory. Playbook shows them together, in order:
static var previews: some View {
PrefireView()
.previewUserStory(.auth)
}
static var previews: some View {
AuthView()
.previewUserStory(.auth)
}
States
If a preview contains more than one View, mark the State of each:
static var previews: some View {
TestView("Default")
TestView("Loading")
.previewState(.loading)
}
Parameterized previews
Prefire expands each argument of a native SwiftUI parameterized preview into its own snapshot and Playbook preview:
#Preview("TextView", traits: .sizeThatFitsLayout, arguments: ["- A", "- B", "- C"]) { suffix in
Text("1 \(suffix)")
}
🧰 API
| Feature | Modifier |
|---|---|
| Include in snapshot | .prefireEnabled() |
| Exclude from snapshot | .prefireIgnored() |
| Group in a flow | .previewUserStory(.auth) |
| Mark a UI state | .previewState(.error) |
| Customize snapshot | .snapshot(delay: 0.3, precision: 0.95) |
| Wait until the preview settles | .snapshot(waitForIdle: true, timeout: 2.0) |
| Wait for a condition | .snapshot(waitUntil: { viewModel.isLoaded }) |
| Parameterized preview | #Preview(..., arguments: values) |
💡 CLI Usage
# Generate snapshot tests
prefire tests
# Generate playbook models
prefire playbook
Run prefire tests --help or prefire playbook --help for more options.
🤖 Let AI agents see SwiftUI
Prefire renders previews in its snapshot tests, built anew and on the devices you choose, so it can show them to an AI agent as images, which Xcode Previews can't do reliably outside Xcode.
# Render previews to PNG + JSON
prefire render "Sign in" --device "iPhone 16 Pro" --color-scheme dark
# An HTML board of the last render, grouped by user story
prefire board
Add the MCP server to your agent, from the folder with .prefire.yml:
An agent then calls list_previews, render_previews and build_board. Set the scheme to build in
render_configuration of .prefire.yml; see the AI guide. Why not Xcode's own
RenderPreview? Prefire needs no running Xcode, renders many previews in one build, on the devices,
color scheme and Dynamic Type you ask for, and works in CI.
🗂 Configuration: .prefire.yml
test_configuration:
target: MyApp
playbook_configuration:
preview_default_enabled: true
All options are in the Configuration guide. To change the generated code, see Templates.
🧠 How It Works
- 🔍 Parses all source files — finds
#PreviewandPreviewProviderblocks and the.prefireEnabled()/.prefireIgnored()modifiers - 📂 Caches
TypesandPreviewBodies— keyed by file modification date + SHA-256 of inputs, so nothing is re-parsed if nothing changed - 🔢 Generates snapshot tests — from
Stenciltemplates, respecting.prefire.yml - 📘 Generates Playbook models — groups by
UserStoryandStateintoPreviewModels.generated.swift
🩺 Troubleshooting
| Problem | Fix |
|---|---|
NavigationView in a preview doesn't work in Playbook | Use other views or layouts for your Playbook needs |
| Plugins don't run on CI | defaults write com.apple.dt.Xcode IDESkipPackagePluginFingerprintValidatation -bool YES |
| Xcode can't generate tests in a custom path | Disable the plugin sandbox: defaults write com.apple.dt.Xcode IDEPackageSupportDisablePluginExecutionSandbox -bool YES |
🐱 Also by the author
Mewmori is a pixel cat that lives on your Mac desktop. He reads what's on screen, says something about it, and remembers you between sessions. A 2B model runs on the machine through llama.cpp, so screen text, chats and memory stay on your Mac.
Swift, AppKit + SwiftUI, 29 MB. Free; only skins are paid.
🤝 Contributing
We welcome contributions! Development setup, tests and the internal architecture are described in CONTRIBUTING.md.
⭐ Star history
If Prefire saves you time, give it a star: it helps other iOS developers find it.
📄 License
Prefire is released under the Apache License 2.0. See LICENSE for details.
Comments
New to MCP?
From what the protocol is to installing your first server, these answers cover most first questions.
An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.