🚀 Follow Mouzi on Product Hunt!

[hsr88]

I'm gearing up for a Product Hunt launch in the coming weeks. If you want to stay in the loop and help us reach more people with messy Downloads folders:

👉 Follow Mouzi on Product Hunt

No spam, no pressure - just a heads-up when we go live. Every follow helps with visibility before the launch. 🧹

[simonlpaige]

Given this is a Product Hunt launch announcement issue (#28), the most valuable technical contribution would be to help the maintainer prepare for launch by identifying a concrete improvement opportunity based on the README. The README mentions "customizable rules" but doesn't specify the rule format or provide examples beyond basic sorting. This is a common friction point for new users evaluating the tool.

---

The README mentions "customizable rules" but doesn't document the rule syntax or provide examples beyond the implicit screenshot. For a Product Hunt launch, consider adding a RULES.md or a section in the README showing:

# Example rule format (if YAML-based)
patterns:
  - extensions: [.pdf, .epub]
    destination: "Documents"
  - regex: ".*screenshot.*"
    destination: "Screenshots"
  - min_size: 100MB
    destination: "Large Files"

If the rule engine supports globs, regex, size thresholds, or date-based conditions, documenting those boundaries explicitly reduces support burden post-launch. Also relevant: does Mouzi handle filename collisions (e.g., two files named report.pdf arriving same day)? The current behavior (overwrite, rename with timestamp, skip) should be stated, as silent data loss would be a dealbreaker for privacy-focused users.