Planners on every platform. System calls behind canImport.

SkillstrandCore

The skill-file parser, dialog values, and the step trace a skill returns. No system framework.

SkillstrandIntents

Intent and parameter builders, the error map, and, when App Intents is present, confirmation and disambiguation.

SkillstrandEntities

Property conventions and EntityQueryScaffold. Display representations are mapped only when App Intents is linked.

SkillstrandSpotlight

IndexSyncSession remembers fingerprints. EntitySpotlightBridge applies the plan to a named index.

SkillstrandShortcuts

Phrase checks require {applicationName}. AppShortcutsSource renders an AppShortcutsProvider.

SkillstrandExamples

The four skills, their Markdown, and the App Intent types the sample registers.

Why the split

A skill file does not execute. The assistant reads it and calls tools. The package still models the questions those tools have to ask — a missing value, a choice, a confirmation — so you can test the path on Linux before a simulator exists. The same inputs drive the sample’s studio.

Indexing follows the same idea. The coordinator is pure. The bridge is the only type that touches CSSearchableIndex. Inserts and updates both go through indexAppEntities, because that call replaces an identifier that is already there. Deletes use deleteAppEntities(identifiedBy:ofType:).