iiYese

That sounds better

I'll give a more detailed review later but just from the examples I think providing the system before the system params the wrong way to do this. The system should...

> I initially implemented it that way but then you don't get the type deduction for the builder closures until you add the system at the end. The alternative would...

> but being able to deduce that the more minimal query .. You don't deduce the more minimal query you always prefer the query in the system signature & it's...

#13120 would help prevent these kinds of bugs & surprises.

I would like replacing `get_(mut)` anyway because it gives it parity with `QueryData` & makes it naturally consistent with the other bevy APIs like `add_systems`, `insert`, `add_plugins` etc. The breaking...

How about: ```rust entity.data::(); enttiy.get_data::(); entity.data_mut::(); enttiy.get_data_mut::(); ``` like Query***Data***.

I'm more a fan of that redundancy than `try_get` which is 2 rust terms for fallible.

> We could also invert things / make mutable access the default. I don't think that's a good idea because: - It would be the only inconsistent exception among every...

These extensions should also be added to `FilteredEntityRef` & `FilteredEntityMut`.