best practise using jotai in big project?

Now I just treat jotai as state management tool, but I think jotai can do more than that. I read the docs, and noticed that maybe I can write my logic in the derived atom and I don’t need to put them in custom hooks anymore.

simply like this:

const countAtom = atom(1)
const asyncIncrementAtom = atom(null, async (get, set) => {
  // await something
  set(countAtom, get(countAtom) + 1)
})

const Component = () => {
  const [, increment] = useAtom(asyncIncrementAtom)
  // it will suspend while `increment` is pending.
}

but then my question is, how should I organize the atom structure? should I put theme together or split them into serval files? when should I use atom, and when shouldn’t I use it?

all the examples in the doc is too simple. Is there any best practices to demonstate the best way of using jotai?

[chj-damon]

@dai-shi maybe it’s better to transform this issue to discuss.

[chj-damon]

I didn’t get a good idea about dealing with other hooks from third-party libraries, such as react-navigation. for example, I need to do some logic and then navigate to other screens. I can use const navigation = useNavigation() which useNavigation is a custom hook from react-navigation library. I can do this in custom hooks, but as we discussed above, If we write all these logic in derived atoms, how can I do that? because Hooks can only be used in hooks.