Patterns
Composer
The inline creation form: one mandatory title, a description line, and every property as a quiet pill menu rather than a labelled field. Create stays disabled until the title has content and nothing else gates it, so an object can exist a second after the thought does. Suggestions sit one click away for the case where the reader knows they want something but not what to call it.
npx shadcn@latest add @minflow/composerWhere to use it
- Issue, task, and document creation, in place of a New button that navigates away.
- Any object whose properties can honestly be filled in after it exists.
- Never for a form with real validation across several required fields; that needs a page and proper error handling.
Variations
Standard
The default. One team, one suggestion, and every property optional behind a pill.
With suggestions
When the surface can propose plausible titles from context. Keep the list to three, because a wall of suggestions is a decision rather than a shortcut.
Opened in place
Inside a list the reader is adding to. The composer replaces the add control at the exact spot the new object will appear, and cancelling puts the control back.