Style
Style helps your assistant give advice based on what you actually own.
What Style Remembers
- saved closet items
- item details, fit notes, and where those details came from
- patterns your assistant has noticed, clearly separated from preferences you confirmed
- photos of saved items
- an optional clothing budget
Your assistant makes the final style recommendation. Fluent supplies the closet information behind it.
Closet Questions
Start with:
fluent_get_context(domain="style", intent="closet")Your assistant can look up a specific item or photo when it needs more detail.
Purchase Questions
For a grounded candidate, use:
fluent_get_context(domain="style", intent="purchase", candidate=..., amount=...)Your assistant should inspect the available images, compare the candidate with items you own, and be honest when your closet information is incomplete.
Your assistant considers the budget alongside fit, usefulness, and what you already own.
Saving Changes
After you explicitly approve a change, Fluent can:
- create a new Style item from a user-confirmed draft
- patch details on an existing item
- update an item from details or an image your assistant inspected
- save or replace an item photo
- archive an item that is no longer owned
- set a clothing budget or record spending against it
Your assistant should check the saved item before saying the change worked.
Closet Manager
Compatible AI apps can show a visual Closet Manager for your saved items. Purchase advice comes from the conversation with your assistant.
What To Keep In Mind
- Treat patterns in the closet as useful signals and label them as inference until confirmed.
- Ground product details, prices, and closet comparisons in available evidence.
- Keep internal identifiers and storage details out of ordinary answers.
- Leave the final purchase action with the user.