Assets

An app's brand in its asset catalog, drawn on the Mac and shipped as a Granite agent package. A call gives the app's name and, as it likes, a mark, colours and a few lines; the package draws everything an iOS + macOS catalog needs with CoreGraphics and CoreText (the app icon at every size and appearance, the accent and palette colours, vector logos, a launch logo, placeholder avatars, empty-state illustrations, custom symbols) and writes each set with the Contents.json Xcode would write for it. No model is asked.

It is one of the Rao Craft Agents: independent packages that, tagged in prompts along the life of a project, build an app of Loom's quality. assets writes the brand every other layer shows: the icon on the Home Screen and in the Dock, the tint, the logo on an about page, the avatar a feed shows for someone with no picture, the picture an empty list shows.

How an app finds it

AssetsAgent is a GraniteAgentPackage, and it carries a record in its binary:

@used @section("__DATA_CONST,__granite")
let assetsRecord: GraniteRoster.Record = { GraniteRoster.record(AssetsAgent.self) }

In Craft, install it from the Agent Store or with craft agents add https://github.com/Rao-Craft-Agents/AssetsAgent.git, then say $assets in a request:

$assets brand the recipe app Simmer: its S in Didot on a warm orange gradient, a cream paper colour
and a herb green, and a whisk symbol

The model writes the call; it shows on Craft's agent map as assets-1, and the catalog it names is built with the turn.

What a call takes and answers

The answer is an AssetsResult: every file written (path, the largest icon; paths, all of them, absolute), the catalog, the sets by the names code uses, and a sentence for anything the project still needs (an app target that names no icon, a launch screen that does not name the launch logo).

The lines

palette:  paper: #FFF8F0/#1C1714          light, then dark
          ink: #1D1B19                    the same in both
          danger: #D93A2B/#FF6B5E/#A3180D/#FFA39A   light, dark, then each in high contrast
          accent: #E8590C/#FF8A4C         the app's tint: the AccentColor set
          LaunchBackground: #FFF8F0/#1C1714   the launch screen's colour
symbols:  whisk: M30 90 L50 40 L70 90 M50 40 L50 10
          pin.fill: M50 94 C50 94 18 62 18 40 A32 32 0 0 1 82 40 C82 62 50 94 50 94 Z M50 28 A12 12 0 1 0 50.01 28 Z
data:     pantry: Resources/pantry.json

• A symbol is SVG path data in a 0…100 box, y down: every command, absolute and relative, arcs included. The path is the symbol's centre line, stroked at Ultralight, Regular and Black; a name ending .fill (or fill before the colon) fills it, holes and all.
• Two names Xcode's asset symbols would make the same (paper and paperColor, pin.fill and pinFill) are refused, so the app's build never warns; a palette line named accent is the AccentColor itself.
• Every line, value and font that cannot be honoured is refused with its reason, all at once, and nothing is written.

What it makes

Code reads them as Image("Logo"), Image(.logo), Image("Placeholder/Avatar"), Color("paper"), Color.accentColor, Image("whisk"), NSDataAsset(name: "pantry").

How the assets are made

Apple's SF Pro, SF Symbols and New York never appear in an icon or a logo: their licence keeps them out. A letter the chosen face lacks is refused rather than set by macOS in another font.

Testing

swift test                    # the record, the schema, the lines, every Contents.json, the pixels, actool for iOS,
                              # macOS, watchOS and visionOS, what the compiled catalog loads, running again
ASSETS_BUILD=1 swift test     # the catalog in a two-platform app: xcodebuild for macOS and the iOS Simulator with no
                              # asset warning, and the Mac app run to report what it finds in its own bundle

MIT licensed.