SFT (Screens, Flows, Transitions) — manage UI behavioral specs as structured data.
Use when the user wants to define, query, modify, or validate a UI specification
covering screens, regions, events, state machines, tags, and flows. The spec lives
in a local .sft/db SQLite database in the working directory.
<example>
user: "show me the current spec"
assistant: runs sft show to render the full spec
</example>
<example>
user: "add a Settings screen"
assistant: runs sft add screen Settings "description"
</example>
<example>
user: "what would break if I remove the Inbox screen?"
assistant: runs sft impact screen Inbox
</example>
<example>
user: "validate the spec"
assistant: runs sft validate
</example>
<example>
user: "model the checkout flow for this app"
assistant: uses sft add to build screens, regions, events, transitions, and flows
</example>
<example>
user: "query all events"
assistant: runs sft query events
</example>
<example>
user: "attach the component schema to the NavBar"
assistant: runs sft at
2026-03-17