Hot, not loud
Fire marks action and verification. It stays focused instead of taking over every surface.
A visual system for the tool that turns SwiftUI previews into confidence before release.
Prefire removes the tension between “the interface looks ready” and “we know it did not break”. The fire is the final warm-up before release, not visual noise.
Fire marks action and verification. It stays focused instead of taking over every surface.
Code, grids and status labels create clarity. Paper and light keep it human.
Motion follows the path from preview to test. The language never promises magic.
Calm, concrete and verifiable. Swift terms remain Swift terms. The result comes first, then the mechanism and its limits.
The horizontal lockup is the default. The flame stays inside its rounded square and the proportions never change.

01 / paper + night plate

02 / night

03 / deep plum

Use the standalone mark only when the name is already present in the surrounding context. External communication defaults to the full lockup.
Paper and Night carry the large surfaces. Ember and Gold mark action, progress and success — never long-running copy.
#F5F0E7#17181C#FF6A35#FFB629#31001E#A0075D#343741#665F56The Apple system stack feels native beside Xcode and adds no external dependency. The monospaced layer explains mechanics.
Prefire turns previews into snapshot tests, Playbook and living documentation — without another set of UI states.
DISPLAY / 64One decisive ideaBODY / 17Explanation and documentationLABEL / 12STATUS / PLATFORM / VERSION#Preview("Checkout / loading") { CheckoutView() .previewState(.loading) } // snapshot passed
Use the warm field for atmosphere and the state path to explain the product. Pick one leading device per surface.
A cover, conference backdrop or restrained promo layer — never a replacement for product proof.
Connects preview, generator, snapshot and confidence as one visible flow.
A field of UI variants. Keep generous empty space around it.
One light source marks the active check or primary action.
README, release notes, social posts and talks use the same ingredients: a direct headline, a small piece of real code or UI and one hot accent.
The PDF contains the full reference. CSS and JSON files expose the same tokens for product and site work.