Example decision
Example decision: if a round theme is confusing, open the themes page to understand the prompt, then move to outfit ideas when you need a formula, palette, key pieces, and no-VIP alternative.
Data boundary: Dress to Impress pages can help with creative planning, but they do not predict voting behavior, official scoring, judge preference, or runway results.
When to leave this hub: use your live wardrobe and round timer when the available pieces, theme wording, or server style differs from the example prompts.
- First decide whether the player needs to understand a theme, generate a random prompt, or build a concrete outfit. Theme lookup, prompt generation, and outfit planning should not compete on the same page.
- Then use outfit ideas when the player already knows the theme and needs a silhouette, color plan, key pieces, and common mistake note. Use the generator when the theme itself is still undecided.
- Finally adapt the suggestion to the live wardrobe. No-VIP planning should begin with readable basic pieces before adding premium accents, because a simple clear outfit usually beats a crowded outfit that misses the theme.
- Do not infer guaranteed votes or official scoring from this hub. Treat it as a planning route that helps players choose a prompt, formula, or no-VIP direction faster.
Scenario: a player does not understand the round theme. Start with the theme reference, then choose outfit ideas only after the prompt has a clear visual direction.
Scenario: a player needs a fast prompt. Use the generator for a theme, palette, and accessory direction, then move to outfit ideas if the result needs a complete formula.
Scenario: a player has no VIP access. Use outfit ideas and read the no-VIP alternative before adding premium accents, because readability matters more than expensive-looking clutter.
Scenario: a player wants guaranteed votes. Leave the hub boundary and use the live round context; LootKit can suggest planning structure, but it cannot predict server taste.
Use the themes page when the player needs to decode the prompt. Use outfit ideas when the prompt is understood and the missing piece is a look formula, color plan, silhouette, or no-VIP substitute.
Use the generator when the player needs a new prompt, not when they already have one. A generated prompt should become a planning input, not a promise that the round will reward that direction.
Leave this hub when the question depends on a live server's taste, timer pressure, judge preference, or wardrobe limitations that are not visible in the example. LootKit can structure the plan, but the final outfit has to fit the round.
If the player has thirty seconds left, prioritize one readable silhouette and two theme signals. If the player has time to plan, build the formula first and then add accessories.
When a theme is broad, pick one interpretation and make every piece support it. A clear school uniform, spy outfit, beach look, or vintage silhouette usually reads better than mixing several unrelated ideas.
When a player asks for no-VIP help, route to outfit ideas before theme generation. The useful answer is not more prompts; it is a practical substitute list that works with common wardrobe pieces.
When a player asks why an outfit lost, keep the answer inside planning boundaries. Review theme fit, color contrast, clutter, silhouette, and missing accessories, but do not claim that LootKit can explain vote behavior.