Wear counts per item
The hanger-reversal test, automated: every outfit log credits the items in it, so "worn in 12 months" is a number, not a guess.
Interactive · 6 questions
Should I keep it?
Hold the piece in your hands and answer honestly. The tree applies the two frameworks professional organizers use — the hanger-reversal test and cost per wear — and hands you a verdict with the reasoning spelled out, not a vibe.
Question 1
Does it fit the body you have today?
Not the body from two years ago, and not "with a belt". Today.
Verdict
KEEP
The verdict never deletes anything — in the app, the same logic feeds the retire flow, where "sell" drafts a listing and "donate" logs the exit.
How the app does it
Retire with receipts.
Armoiria already knows your wear counts, so the tree runs itself.
Cost per wear on tap
Price ÷ wears per item, updating with every wear. The tree's CPW branch reads straight off your closet ledger.
A real retire flow
Sell drafts the resale listing, donate logs the exit, and memories get archived — the rail gets shorter either way.
Duplicate detection
The "three or more of the same job" question is answered before you ask it — the app flags duplicate stacks for you.
Frequently asked questions
What is the hanger-reversal trick?
Turn every hanger in your closet to face backwards today. When you wear something, rehang it the normal way. In twelve months, the still-backwards hangers are your retire list — no memory or guilt required, just evidence.
Why does cost per wear matter when deciding?
The question is never "how much did it cost?" but "how much does it cost per wear, going forward?" An unworn $40 shirt costs $40 per year to store. A worn-in $220 coat is already down to pocket change per wear.
Shouldn't I keep everything that still fits?
Fit is necessary, not sufficient. The tree also checks whether the piece is being worn, whether you own three duplicates, and whether it is in wearable condition — a rail full of "fits but never worn" is the most common closet failure.