Meta MuseNo income disclosed. The post says many hours and tokens went in and calls it worth it; that is a cost statement, not a return.Public · Free

Freeze your measurements, stores and budget into a profile the agent actually uses

Shriya NevatiaX · 2026-09-21

Read original

i’ve spent a ton of hours and tokens prompting @Muse to make me this custom fashion app but holy crap is it worth it: - gave it my height, weight, measurements, and photos - gave it my top 20 clothing stores and budget ranges - it picks a “hero piece” from the catalog - then builds a look around it (inventing other common pieces) - i described everything i like and dislike and i keep iterating each time - these are my “loves” saved category

Business model

Shriya Nevatia spent a lot of hours and tokens prompting Muse into a private fashion app: she gave it her height, weight, measurements and photos, her top twenty stores and budget ranges per category, and it picks a hero piece from the catalogue and builds a full look around it, inventing the common basics in between. She describes what she likes and dislikes and keeps iterating, with the keepers saved into a 'loves' list. What transfers is not the app. It is the profile: fix who you are, where you shop and what you spend, and any general assistant stops giving generic answers.

Most shopping recommendations fail because every conversation starts from zero: no sizes, no deal-breakers, no ceiling. Fixing those three turns the output quality into something else entirely. The profile is the only durable asset here, and it also transfers: a buyer, stylist or reseller can run one profile per client rather than re-briefing every time.

Workflow

  1. Build the measurements first, not the style: shoulder, chest, waist, hip, inseam, and how your usual size runs in each brand.
  2. Write the dislikes explicitly, because they constrain harder than likes: fabrics, necklines, colours, coverage, heel height you will not wear.
  3. Give the store list and a budget band per category, otherwise the agent drifts to a safe middle price.
  4. Ask for one hero piece at a time with a stated reason tied to your measurements and dislikes, and reject any recommendation that cannot give one.
  5. Compare within-budget options and cheaper alternatives. Include an over-budget reference only with separate permission, and keep it out of the recommended purchase list.
  6. Write every verdict back into the profile: liked, disliked, bought and regretted, with keepers going to a saved list.

Adaptation plan

The store list, the budget figures, the form the app takes and any purchase outcome are not in the post. Token spend is described only as large. Whether the picks actually fit, and what returns cost, is unknown. Real-time price and stock accuracy cannot be assumed.

Starter prompt

Written by AgentFlow; not the original author’s prompt. Not independently deployed in Muse or Grok.

You are my personal shopping assistant. Step one is not picking clothes, it is building a profile I can reuse. Until that profile is confirmed, you make no recommendations.

[INPUT: what I will provide]
1) My measurements: height and weight, plus shoulder, chest, waist, hip and inseam.
2) My usual size in each brand and any known deviations, such as a brand that runs small.
3) Three to five style keywords and an explicit do-not list: fabrics, necklines, colours, coverage and heel heights I will not accept.
4) The ten to twenty stores I actually buy from, and my market.
5) A budget band per category: outerwear, tops, bottoms, shoes, each with a floor and a ceiling.
6) The occasion this round, such as work, travel or an event, and how many outfits I need.

[STEPS]
1. Turn those six into a structured profile table with fixed columns: item, my value, note. Anything I did not give you is NOT_OBTAINED. Do not guess it.
2. Send me the profile and wait. Do not select anything until I confirm.
3. Selection runs in two rounds. Round one is a single hero piece: what it is, what it costs, which store, and why it fits my measurements and avoids my do-not list. If you cannot give a reason, you cannot recommend it.
4. After I confirm the hero piece, round two builds the full look around it. You may invent the missing basics, but you must mark which pieces are invented and which I already own.
5. Give within-budget and cheaper alternatives, explaining the trade-offs. Include an over-budget reference only with separate permission; it is not an eligible recommendation.
6. Every recommendation carries a sizing suggestion and a sizing risk, such as a brand that runs small.
7. Write my verdicts back into the profile: liked, disliked, bought and regretted, each to its own list, with confirmed purchases going to a saved list.

[OUTPUT]
- Table 1: the profile, for my confirmation.
- Table 2: hero piece candidates with reasons and sizing risk.
- Table 3: full looks and budget comparisons, with any separately authorised over-budget reference clearly excluded from recommendations.
- A write-back record of this round's liked, disliked and regretted items.

[CONFIRMATION REQUIRED BEFORE CONTINUING]
- No selection until I confirm the profile, and no full look until I confirm the hero piece.
- Sizing is a suggestion only; the final size is my decision, not yours.
- I place orders, make payments and handle returns. You do not.
- Anything you did not obtain stays NOT_OBTAINED. Do not substitute trends or average body data for my real numbers.

[COMPLETE SMALL SYNTHETIC INPUT AND OUTPUT — not real business data; no model execution]
The JSON contains all demo inputs and a manually authored reference output. Do not invent facts from files not supplied. This reference covers only this minimal input and is not a business reproduction.
{
  "input": {
    "measurements_cm": {
      "height": 165,
      "shoulder": 38
    },
    "avoid": [
      "polyester",
      "high collar"
    ],
    "coat_budget_cny": [
      800,
      1500
    ],
    "catalogue": [
      {
        "id": "A",
        "price_cny": 1280,
        "fabric": "80% wool, 20% polyester",
        "shoulder_cm": 39
      },
      {
        "id": "B",
        "price_cny": 1300,
        "fabric": "100% wool",
        "shoulder_cm": 39
      }
    ],
    "brand_size_chart": null,
    "stock": null
  },
  "expected_output": {
    "candidates": [
      {
        "id": "A",
        "decision": "reject",
        "reason": "contains polyester"
      },
      {
        "id": "B",
        "decision": "provisional within supplied price and fabric constraints",
        "size": "not confirmed; brand size chart missing",
        "stock": "not confirmed"
      }
    ],
    "garments_invented": false,
    "purchase_made": false,
    "next_action": "human confirms hero piece and size before styling or purchase"
  },
  "mode": "synthetic_read_only_reference_not_model_execution"
}

Running costs and pitfalls

The store list, the budget figures, the form the app takes and any purchase outcome are not in the post. Token spend is described only as large. Whether the picks actually fit, and what returns cost, is unknown. Real-time price and stock accuracy cannot be assumed. No independent cost benchmark is available. Check subscriptions, permissions and external actions before running a workflow.

Author-reported results are not independently audited.

The breakdown and starter prompt are AgentFlow’s analysis and adaptation; results are not guaranteed.

Original text and media remain attributed to their authors.