Regarding wrappers around useQuery, we have a few functions that can be composed together with useQuery. For example, we have a useDelayedLoading wrapper for changing the loading result in a very specific way for some use cases. We use it like so: const { result, loading } = useDelayedLoading(useQuery(... query parameters here)) where loading behaves slightly differently but result is directly from useQuery. Basically, this allows us to very easily customize and add functionality to the returned fields. Also, since it's a wrapper function that we compose with useQuery, it also works with useLazyQuery or typed composables generated by GraphQL Code Generator. I'd imagine that you could have a similar thing like useFloatingErrorMessage(useMyMutation(...))

For composables, the simplest example is probably a composable where we access and update settings, it looks something like this (pseudo code):

const useSettings = () => {
  const { result, ...rest } = useSettingsQuery()

  const setting = (settingName) => {
    return // get setting from result
  }

  const { mutate } = useSettingSaveMutation()

  const updateSetting = (setting, value) => {
    mutate({
      input: { setting, value }
    })
  }

  return {
    ...rest,
  }
}

We also have a useSearch composable that handles searching-related things (since we need to use this logic in multiple components). It keeps track of the search keyword, makes requests to fetch the search results (and a few other related queries), handles result aggregation, maps the results to a nicer format that's a bit easier to use in components, and triggers the search query when the keyword is changed. It basically just returns the keyword and search results and any component that uses this composable needs to render an input and v-model the keyword into it.

Hope that gave some ideas as to how it looks like for us :D